View Single Post
Old 24th June 2018, 19:03   #6284  |  Link
Zathor
Registered User
 
Join Date: Nov 2009
Posts: 2,405
The process during startup is:
- delete avisynth.dll if found in the MeGUI folder
- run a avs script to check if a system installed avisynth is found (+ log output)
- if no, no suitable version or if "always use portable" is checked, the avisynth.dll will be copied to the MeGUI root folder (from tools\avs)
- run a avs script to check if this portable avisynth can be used (+ log output)
- if the portable version cannot be used, delete the avisynth.dll from MeGUI root

So if you do not find it there, it has already been deleted.

Did the "force" version work or not? It does not do the steps with the system avisynth. Could you post a log of that?

What happens if you copy the tools\avs avisynth.dll and devil.dll to e.g. x264 folder and start the encode? Is it then using it?
EDIT: the avisynth.dll in an encoder folder cannot be influenced at all by MeGUI. So either it does work or not. During program start I can do a few changes for the detection and usage e.g. in AVS Creator, but not for the encoders. There the encoder has to call the proper dllbased on the search rules. Therefore it would be good to know e.g. when you run the x264.exe (without MeGUI) on a command line if the avisynth.dll in that folder will be used or not.

Last edited by Zathor; 24th June 2018 at 19:08.
Zathor is offline   Reply With Quote