https://github.com/lordmulder/Simple-x2 ... /tag/v2.64
Version 2.64 [2015-12-20]
* Fixed a dependency issue with Visual Studio runtime libraries
Version 2.64 [2015-12-20]
* Fixed a dependency issue with Visual Studio runtime libraries
Version 2.68 [2016-04-09]
* Updated build environment to Visual Studio 2015 with Update-2
* Updated x265 to version 1.9+106
Version 2.67 [2016-03-17]
* Updated x265 to version 1.9+96
* Fixed detection of 64-Bit VapourSynth in certain cases
Version 2.66 [2016-02-06]
* Updated x265 to version 1.9+3
Version 2.65 [2016-01-24]
* Improved 32-Bit vs. 64-Bit selection for Avisynth/VapourSynth
* Added menu entry to remove all completed or enqueued jobs at once
* Updated x264 to revision 2665
* Updated x265 to version 1.8+212
C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\extra\VapourSynth\core64>VSPipe.exe --version
Failed to initialize VapourSynth environment
Update:deathcubek wrote:Try with this TEST version:
https://sourceforge.net/projects/mulder ... p/download
This version should detect and use the "portable" version of VapourSynth. Just extract the 32-Bit version to the extra\VapourSynth\core32 sub-directory and the 64-Bit version to the extra\VapourSynth\core64 sub-directory.
Note, however, that I did not manage to get the "portable" version of VapourSynth to work on my system. It just says:C:\Program Files (x86)\MuldeR\Simple x264 Launcher v2\extra\VapourSynth\core64>VSPipe.exe --version
Failed to initialize VapourSynth environment
The Avisynth installer already does have a "protable" mode in which it will simply dump the Avisynth DLL's into the specified target directory, without "installing" them into the System directory.Midas wrote:Can a similar solution be applied to AviSynth and its ilk?
deathcubek wrote:Here is a new TEST version that tries to workaround this problem by adding the Avisynth.DLL location to the PATH environment variable for all sub-processes that may need it:
https://sourceforge.net/projects/mulder ... p/download
False PositiveMidas wrote:deathcubek wrote:Here is a new TEST version that tries to workaround this problem by adding the Avisynth.DLL location to the PATH environment variable for all sub-processes that may need it:
https://sourceforge.net/projects/mulder ... p/download
- Thanks. Will look into it soon...
EDIT: Oops! (I downloaded it anyway...)
Version 2.83 [2017-06-11]
* Updated x264 to revision 2833
* Updated x265 to version 2.4+36
Version 2.84 [2017-07-12]
* Updated x264 to revision 2851
* Updated x265 to version 2.5+2