error: "viddll engine not installed" when exporting executable
Hello Max people!
I just updated to Max 8.1.6 and tried to do an executable of my patch. Everything went smooth apart from a new (yellow) error announcing that “viddll engine not installed: video playback capabilities will be limited, please install VIDDLL package from Package Manager (File->Show Package Manager)”, even if VIDDLL package was already installed (I think now by default). I tried to include the whole folder in the executable through the include folder option, I got a new error. I don’t think I even use the external, so I do not understand why the warning. Also, I don’t want just to ignore it, as it look troublesome to people that just need to use the executable. Any suggestions?
Thanx!
solution is found already. fyr, Paul Fennell in the FB Max/MSP forum suggested the following:
"I just copy the VIDDLL folder (and any other required packages) into resources/packages/ - it has always worked for me. My standalone is Jitter based, so it's actually needed in my case.
Viddll is the default engine used for video playback (jit.movie etc). Changing the engine to qt in max’s preferences prior to exporting or using the Max message "max videoengine qt;" on load may also suppress the error message, although I’m not certain. I think that you can also create a jitter-config.txt file in the init/ folder where you could execute the same message - again, I haven't tested this.
Also, you can hide the Max console in standalones if you don’t need it and are sure that there are no critical errors (of course, it’s always better to rectify them). If you're not dealing with video the message is irrelevant."
although the 'warning' has disappeared, it seems weird it appeared in the first place.
I have been doing executables from different versions of this patch for some time, and this is the first time I have this 'warning'.
Not sure why it checks for it when not used. Also, not sure why if it is automatically checked, why it is not automatically included.
it does look like 8.1.6 introduced some behavior changes in this area, thanks for the report.
I don't think we'll be able to get a fix in for 8.1.7, but I will ticket this for investigation and we'll sort it out. for now you can either: use 8.1.5, ignore the warning, or copy the viddll package into your standalone's resources folder (as suggested). apologies for the inconvenience!
looks like this change goes all the way back to Max 8.1.4
Thanx rob for your investigation! For now we have to remember to include the viddll, to avoid unnecessary warning, until it gets fixed in a couple of versions of Max. Cheers!