14.04.2018, 22:40
First, I just replaced Hybrid and the result is attached output2.txt
Then, I removed avisynth Extension from the .hybrid folder and copied it all complete including the sub-avisynthPlugins folder to /root/.wine/drive_c/Program Files
I also copied avisynth.dll and DevlL.dll to /root/.wine/drive_c/windows/syswow64
I had these previously in system32
I also edited misc.ini to reflect the change and attached output3.txt is the result.
Looking at lines 67 & 68 of this, it is not clear to me if Hybrid has found avisynth because the avisynth filter section is greyed out. An attempt to load a .avs file resulted in error " AVSAnalyser: Absolute path for 'avsinfo' not set "
Am also puzzled about the references to aften and x265 near the end because both are on the system and whilst I do not use x265 for encoding, I know that aften works because I specified it in the earlier Hybrid trial.
Thanks for your help so far.
Regards
Zig
I noticed that Hybrid expects to find certain tools in /usr/bin so I copied the following four files over from
Avisynth Extension and reloaded Hybrid.
avs2yuv.exe
avsInfo.exe
AVSMeter.exe
avsViewer.exe
Whoopee !!! avisynth is no longer greyed out. See output4.txt attached
My next step is to try and locate the missing minor tools and work out how I load an avs script and what the format should be because I want to be able to use TFM and QTGMC. Is there any link guide that you can point me to because there is a distinct lack of documentation. All of this should really be documented somewhere
Thanks again
Then, I removed avisynth Extension from the .hybrid folder and copied it all complete including the sub-avisynthPlugins folder to /root/.wine/drive_c/Program Files
I also copied avisynth.dll and DevlL.dll to /root/.wine/drive_c/windows/syswow64
I had these previously in system32
I also edited misc.ini to reflect the change and attached output3.txt is the result.
Looking at lines 67 & 68 of this, it is not clear to me if Hybrid has found avisynth because the avisynth filter section is greyed out. An attempt to load a .avs file resulted in error " AVSAnalyser: Absolute path for 'avsinfo' not set "
Am also puzzled about the references to aften and x265 near the end because both are on the system and whilst I do not use x265 for encoding, I know that aften works because I specified it in the earlier Hybrid trial.
Thanks for your help so far.
Regards
Zig
I noticed that Hybrid expects to find certain tools in /usr/bin so I copied the following four files over from
Avisynth Extension and reloaded Hybrid.
avs2yuv.exe
avsInfo.exe
AVSMeter.exe
avsViewer.exe
Whoopee !!! avisynth is no longer greyed out. See output4.txt attached
My next step is to try and locate the missing minor tools and work out how I load an avs script and what the format should be because I want to be able to use TFM and QTGMC. Is there any link guide that you can point me to because there is a distinct lack of documentation. All of this should really be documented somewhere
Thanks again