Simple x264/x265 Launcher v3.02 (2022-06-16)

[LoRd_MuldeR]

As the error message says:

The Vapoursynth process terminated abnormally. This means Vapoursynth or one of your Vapoursynth-Plugin's just crashed.

-1073741819 = 0xC0000005 = STATUS_ACCESS_VIOLATION

So this is a problem with Vapoursynth or, more likely, one of the Vapoursynth plug-in's involved. Might as well be a hardware issue though...

[2-perf]

Originally Posted by LoRd_MuldeR

As the error message says:


It's a problem with Vapoursynth or, more likely, one of the Vapoursynth plug-in's involved. Might also be a hardware issue though...

Thanks LoRd_MuldeR. I'll post in the VapourSynth forum.

[djesteban]

Originally Posted by LoRd_MuldeR

As the error message says:


-1073741819 = 0xC0000005 = STATUS_ACCESS_VIOLATION

So this is a problem with Vapoursynth or, more likely, one of the Vapoursynth plug-in's involved. Might as well be a hardware issue though...

I tested this on my side out of curiosity. Tested with two .mov file, one encoded in DNxHD and the other one in ProRes.

I have the same issue than 2-perf where it will crash sometimes on 1-pass startup but mostly on 2nd pass, I would say and easy 8-9 times out of 10.

Seems definitively related to vapoursynth mishandling either .mov containers or the two codecs above... or both. Anyways, there's also ffms2 in the equation here so it could also be part of the issue, but I doubt it.
Encoding a h264 file causes no issue/crash at all.

[SuLyMaN]

Thank you Lord Mulder for this software

[LoRd_MuldeR]

Simple x264 Launcher v2.67
https://github.com/lordmulder/Simple...ases/tag/v2.67

Version 2.67 [2016-03-17]
* Updated x265 to version 1.9+96
* Fixed detection of 64-Bit VapourSynth in certain cases

[LoRd_MuldeR]

Simple x264 Launcher v2.68
https://github.com/lordmulder/Simple...ases/tag/v2.68

Version 2.68 [2016-04-09]
* Updated build environment to Visual Studio 2015 with Update-2
* Updated x265 to version 1.9+106

[RTW47]

vapoursynth input - still gives me troubles with x64 Python 3.5.1 and x64 vapoursynth R31 installed, on Windows 7 SP1;
v2.68.1018 --console as expected shows that 64-bit vapoursynth was successfully detected, unfortunately after selecting add job: I still get "VapourSynth is not/available!" message.
- additionally prefering 64-Bit source in the preferences - not helping;
edit:. trying update to 1024 build via web updater returns SendRequest Error;
edit1:. now noticed that if I just "Ignore&Continue", - everything works without actual problem;

[LoRd_MuldeR]

Originally Posted by RTW47

vapoursynth input - still gives me troubles with x64 Python 3.5.1 and x64 vapoursynth R31 installed, on Windows 7 SP1;
v2.68.1018 --console as expected shows that 64-bit vapoursynth was successfully detected, unfortunately after selecting add job: I still get "VapourSynth is not/available!" message.

Argh, there was a stupid mistake in one of the checks, so it was testing for Avisynth flag where it actually should be testing for VapourSynth flag

Should be fixed by now:
https://github.com/lordmulder/Simple...c98e1f76e206ff

Please try new TEST version:
https://sourceforge.net/projects/mul...8.exe/download

Originally Posted by RTW47

edit:. trying update to 1024 build via web updater returns SendRequest Error;
edit1:. now noticed that if I just "Ignore&Continue", - everything works without actual problem;

Works for me

(Probably a short server outage on SF.net)

[RTW47]

Originally Posted by LoRd_MuldeR

Should be fixed by now:
https://github.com/lordmulder/Simple...c98e1f76e206ff

Please try new TEST version:
https://sourceforge.net/projects/mul...8.exe/download

I can confirm that test build works properly.

[szabi]

Hi

Since update to version 2.69 this error occurs:

error: LoadPlugin: unable to load "C:\My Program Files\MeGUI\tools\lsmash\LSMASHSource.dll", Module not found. Install missing library?

I tried it and this avs script works correctly with megui and virtualdub.
What reason makes launcher to fail pluginload?

bye

[LoRd_MuldeR]

Originally Posted by szabi

Hi

Since update to version 2.69 this error occurs:

 error: LoadPlugin: unable to load "C:\My Program Files\MeGUI\tools\lsmash\LSMASHSource.dll", Module not found. Install missing library?

This is an Avisynth error, not Simple x264 Launcher error

Note that Simple x264 Launcher is pretty much just a GUI that launches x264/x265 + Avs2YUV/VSPipe for you. So probably just coincidence that the issue happened to start after the v2.69 update. The real problem must be in Avisynth!


Anyway, one possible reason that comes to my mind:

Maybe your plug-in (LSMASHSource.dll) is 32-Bit and with VirualDub you are using 32-Bit Avisynth, so all is fine, but with Simple x264 Launcher you are trying to use 64-Bit Avisynth? Or the other way around.


[EDIT]

Another possible reason:

Maybe LSMASHSource.dll has a dependency on another DLL. And, when working with VirualDub, that DLL is picked up from VirualDub directory, or from whatever happens to be the "current" directory when you launch VirualDub. But when working with Simple x264 Launcher that other DLL can no longer be loaded, because it's neither in the avs2yuv.exe directory nor in whatever happens to be the "current" directory when you launch Simple x264 Launcher.

It's a very common pitfall with Avisynth plug-in's that have dependencies on other DLL's. Putting those other DLL's into the Avisynth plug-in directory, alongside the plug-in DLL, is not going to work! They must be in one of the directories where the host application (e.g. VirualDub or avs2yuv.exe) will be able to pick them up! One solution is to put the required DLL into "System32" directory. Then it can always be found. But, when doing so, be aware of DLL Hell problem...

[LoRd_MuldeR]

Simple x264 Launcher v2.70
https://github.com/lordmulder/Simple...ases/tag/v2.70

Version 2.70 [2016-04-29]
* Fixed potential VapourSynth error, when Avisynth is not installed
* Some installer improvements

Originally Posted by RTW47

I can confirm that test build works properly.

Thanks for confirming.

[szabi]

Originally Posted by LoRd_MuldeR

This is an Avisynth error, not Simple x264 Launcher error

Note that Simple x264 Launcher is pretty much just a GUI that launches x264/x265 + Avs2YUV/VSPipe for you. So probably just coincidence that the issue happened to start after the v2.69 update. The real problem must be in Avisynth!


Anyway, one possible reason that comes to my mind:

Maybe your plug-in (LSMASHSource.dll) is 32-Bit and with VirualDub you are using 32-Bit Avisynth, so all is fine, but with Simple x264 Launcher you are trying to use 64-Bit Avisynth? Or the other way around.


[EDIT]

Another possible reason:

Maybe LSMASHSource.dll has a dependency on another DLL. And, when working with VirualDub, that DLL is picked up from VirualDub directory, or from whatever happens to be the "current" directory when you launch VirualDub. But when working with Simple x264 Launcher that other DLL can no longer be loaded, because it's neither in the avs2yuv.exe directory nor in whatever happens to be the "current" directory when you launch Simple x264 Launcher.

It's a very common pitfall with Avisynth plug-in's that have dependencies on other DLL's. Putting those other DLL's into the Avisynth plug-in directory, alongside the plug-in DLL, is not going to work! They must be in one of the directories where the host application (e.g. VirualDub or avs2yuv.exe) will be able to pick them up! One solution is to put the required DLL into "System32" directory. Then it can always be found. But, when doing so, be aware of DLL Hell problem...

Hi

I try to figure out what cause it, until that megui going to be used instead of your program which i prefer more.
However before update this issue did not exist.
Thanks.

bye

[LoRd_MuldeR]

Originally Posted by szabi

However before update this issue did not exist.

Please confirm again that the issue still exists with latest version. If so, downgrade to the "old" version (v2.68), but do not touch anything else. Does that resolve the issue?

[szabi]

Hi

You were right the problem comes not from simple launcher.
It comes from megui. It was used to create script.
Megui does something what I do not see.
I reinstall it. Since that script works only with megui nothing else.
Until that I use ffms for indexing which works with simple.
Sorry for that I made a false conclusion.

bye

[LoRd_MuldeR]

Originally Posted by szabi

It comes from megui. It was used to create script.
Megui does something what I do not see.
I reinstall it. Since that script works only with megui nothing else.
Until that I use ffms for indexing which works with simple.
Sorry for that I made a false conclusion.

Again, I suggest you do this:

1. Figure out if the plugin DLL that won't load is 32-Bit or 64-Bit. You can use this tool, to check the "bitness" (see example here). If it is 32-Bit, can only work with 32-Bit Avisynth and thus only with 32-Bit programs; if it's 64-Bit, can only work with 64-Bit Avisynth and thus only with 64-Bit programs. The Simple x264 Launcher supports both "variants" of Avisynth – provided they are installed on your system – by using either 32-Bit or 64-Bit version of Avs2YUV. If both "variants" of Avisynth are installed, you can choose the preferred one in the preferences (this clearly has no effect, of only one "variant" is installed). Make sure it uses the version that matches the "bitness" of your plugin-in DLL!
2. Use this tool to figure out if your plug-in DLL has some additional dependencies. You need the 32-Bit version of the tool for 32-Bit plug-in DLL, and the 64-Bit version for 64-Bit DLL. If it shows any dependencies other than standard Windows DLL's, then these additional DLL's will need to be in a path where they can be found when the plug-in DLL's get loaded into the Avs2YUV process – otherwise loading of the plug-in DLL is going to fail due to missing dependency!

[szabi]

Hi

Many thanks for your help and I apologize for my awkward situation.
Something happened with Microsoft Visual C++ 2015 Redistributable x86 which needed by L-SMASH.
It had to be reinstalled.
Somehow megui worked without it but simple did not.
I must say again thanks and sorry for it.

bye

[LoRd_MuldeR]

Here is a new TEST version with experimental NVEncC (NVidia GPU encoding) support:
https://sourceforge.net/projects/mul...8.exe/download

This requires a NVIDIA Kepler/Maxwell based GPU with driver 358.xx or higher!

[Zetti]

Why is there no option to select x86 or x64 when i choose to use NVEncC??

[LoRd_MuldeR]

Originally Posted by Zetti

Why is there no option to select x86 or x64 when i choose to use NVEncC??

There is. Isn't it?