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

[LoRd_MuldeR]

This is not the latest version. As I said before, please update to the latest version.

[szabi]

Ok, I installed this one x264_x64.2013-11-06.exe.
But now this problem occured: PROCESS EXITED WITH ERROR CODE: -1073741819 for my script.
Script is attached.

[LoRd_MuldeR]

Lookls like Avisynth/Avs2YUV has crashed, so this is not related to Simple x264 Launcher at all.

So first make sure that your script is working correctly. But by having a look at your script, it seems you are using Avisynth-MT, which is known to be an unstable mess. You might want to start by throwing out the MT-related stuff installing a stable Avisysnth 2.5...

In any case, you can use the following to check if your script working correctly:

avs2yuv.exe "c:\path to script\foobar.avs" -raw -o NUL

[szabi]

Ok, thanks.
You are right avisynth MT is used.
What can be tested with this code?

[AGKnotUser]

Originally Posted by LoRd_MuldeR

The warning can be ignored safely, so it's just a "cosmetic" problem

I could either filter out that message so user never gets it to see or I could convert the "shot" name to lower case before passing it to Avs2YUV.

Or I could simply fix the check inside Avs2YUV...

I vote for the Avs2YUV check.

[LoRd_MuldeR]

FWIW, I have implemented a workaround for the Avs2YUV warning message:
http://www.mediafire.com/download/4n...2013-11-08.exe

[AGKnotUser]

Originally Posted by LoRd_MuldeR

FWIW, I have implemented a workaround for the Avs2YUV warning message:
http://www.mediafire.com/download/4n...2013-11-08.exe

Ah, you pass AVS in lowercase. Works for me!

[lansing]

I had installed both 32bit and 64bit vapoursynth, and simple x264 launcher is giving me the message "vapoursynth missing" on start up.

[LoRd_MuldeR]

Originally Posted by lansing

I had installed both 32bit and 64bit vapoursynth, and simple x264 launcher is giving me the message "vapoursynth missing" on start up.

Currently only 32-Bit version is required/used.

Anyway, do you have the latest Simple x264 Launcher installed? And with what version of VapourSynth?

Furthermore: What does the log say? (try to run the app with "--console" if you haven't yet)

[lansing]

I'm using both the last vapoursynth R22 test3 and simple x264 laucher 2.27.638.

And how can I run it with --console?

[LoRd_MuldeR]

Originally Posted by lansing

I'm using both the last vapoursynth R22 test3 and simple x264 laucher 2.27.638.

AFAIK, VapourSynth R22 has not even been released yet, so I don't know if anything relevant for Simple x264 Launcher is going to change. Haven't tried those test builds

Please try with current R21 release. I will have a look at R22 as soon as it's done.

Originally Posted by lansing

And how can I run it with --console?

Type this:

x264_launcher.exe --console

...then hit Enter.

[lansing]

I ran the console the saw the problem.

The newer Vapoursynth version changed the structure of the installation folder. Now they have four folders for filters: core32, core64, plugins32, plugins64

[LoRd_MuldeR]

Originally Posted by lansing

I ran the console the saw the problem.

The newer Vapoursynth version changed the structure of the installation folder. Now they have four folders for filters: core32, core64, plugins32, plugins64

Okay, I will adjust the detection code and release a new version, as soon as R22 is officially out.

(Can send you test version via PM)

[LoRd_MuldeR]

Originally Posted by LoRd_MuldeR

Okay, I will adjust the detection code and release a new version, as soon as R22 is officially out.

(Can send you test version via PM)

The new version is out now!

[Sm3n]

Hi,
Any chance to see soon a Simple x265 Launcher beta?

[LoRd_MuldeR]

Originally Posted by Sm3n

Hi,
Any chance to see soon a Simple x265 Launcher beta?

I did not yet have a chance to play around with x265. But if their interface isn't too different, support can be added in a future version, hopefully.

[Sm3n]

That would be great.
Thx Lord

[szabi]

I receive an alert notification for the exe file:

Do yu have any idea for reason?

bye
szabi

[szabi]

I ignore the alert, and launch the program, what drives new questions.

This is the log file:
Resolution: 704x528
Frame Rate: 25
No. Frames: 333381

--- PASS 1 ---

Creating Avisynth process:
"C:/Program Files (x86)/MuldeR/Simple x264 Launcher v2/toolset/x86/avs2yuv_x86.exe" D:\movie\movie.avs -

Creating x264 process:
"C:/Program Files (x86)/MuldeR/Simple x264 Launcher v2/toolset/x64/x264_8bit_x64.exe" --bitrate 2540 --pass 1 --stats C:\Users\szabi\Videos\movie.stats --preset veryslow --tune film --profile high --level 3.1 --bframes 6 --ref 9 --no-fast-pskip --output C:\Users\szabi\Videos\movie.mkv --frames 333381 --demuxer y4m --stdin y4m -

y4m [info]: 704x528p 0:0 @ 25/1 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x264 [info]: profile Main, level 3.1

Why not save the output to the same directory?
My "C" drive is ssd, which has not enough space for huge files.
Saving to same directory more logical.

Why the given profile is not used?
It is set to High but using Main.

Bye
szabi

[r0lZ]

The warning is due to the fact that the program is not digitally signed. (That cost money, and you cannot hope that a free program will be signed.)

Originally Posted by szabi

Why not save the output to the same directory?
My "C" drive is ssd, which has not enough space for huge files.
Saving to same directory more logical.

There is an option in the Preferences to save by default to the source directory.

I prefer to leave more knowledgeable persons reply to the question about the main profile. I guess it's because you have used an option incompatible with the high profile.