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

[LoRd_MuldeR]

The most straightforward approach for me would be lowering the clock so that you CPU runs within the standard clock speed. Then you should check both the encoding speed you get and the temperature you have. Also you could monitor your CPU clock if it changes when you overclock and the CPU gets warmer. I do not know how to do it in Windows but under Linux I usually can monitor my CPU clock via "cat /proc/cpuinfo"

AFAIK, Windows doesn't reveal this info with "standard" tools, but you can use CPU-Z:
http://www.cpuid.com/softwares/cpu-z.html

Or, if you need it even more detailed, you might want to have a look a TMonitor:
http://www.cpuid.com/softwares/tmonitor.html

Finally, Intel offers a (rather clunky) tool here:
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3052&DwnldID=19105&lang=eng

[VideoFanatic]

Thanks guys. I already using CPUs-Z and CoreTemp. Darksoul - I'm using scripts to do restoration on my videos. The scripts are slow so I can only encode six 1 hour 30 minute videos per day. Using a faster preset makes no difference to the encoding speed in this situation. The problem is that for some reason each video is taking 45 minutes longer to encode than normal and I don't know why. I'm using the same scripts as always.

I'm looking forward to the 8 core (16 thread) Intel CPUs coming out next year then the encodings will be so fast that losing a couple of FPS won't make a difference. Anybody know when they're coming out?

[Darksoul71]

Ah...there we come closer....honestly with a complex filter chain in AVISynth I guess that x264 is most likely not the bottleneck :)

Is your CPU maxed out ? If not you could consider using AVISynth-MT for your scripts. Hopefully you do not do dual-pass with your videos and the complex filter chain ?

@LoRd_MuldeR: Thanks...I was not aware of this. My main OS of choice is Linux and I rarely touch my Windows 7 box beside some gaming or BD ripping.

[Leinad4Mind]

The minimum supported revision is r2350 at this time. Why would you want to use a version that is older than the current "stable" branch of x264?

(If there's some regression in the new version, like the recent deadlock issue, it should be reported and fixed)

I use JEEB r2334 build, and I dunno how to patch, but I like to use some features as fgo and fade-compensate.

And I don't see why just to support the lattest version...

It would be better to let the user choose the x264 version he wants.

Best regards

[LoRd_MuldeR]

I use JEEB r2334 build, and I dunno how to patch, but I like to use some features as fgo and fade-compensate.

If those patches are still relevant (AFAIK, FGO was superseded by Psy-RDO/Psy-Trellis, and the "fade compensation" patch is just a hack that moves more bits into "fades" ... no matter what ... causing problems of its own), somebody should make an up-to-date build of x264 with those. You don't want to stick with an outdated x264, just because somebody once made a build with some obscure patch, do you? Again, if the patch is still relevant, somebody ought to actively maintain it.

And if you prefer using patches nobody else seems to care about anymore, you better familiarize yourself with building x264 from the sources...

And I don't see why just to support the lattest version...

Well, I think I have made that clear above (http://forum.doom9.org/showthread.php?p=1642055#post1642055).

It would be better to let the user choose the x264 version he wants.

I don't think so. I think a "user friendly" software is supposed to guide the average user into the "right" direction ;)

At the same time, the advanced user can always adapt the program to his/her needs. Those are the blessings of OpenSource software...

[Leinad4Mind]

Thanks, I will test out psy-RDO, with komisar builds (with fade compensation). ;)

And try to learn how to use vapoursynth, to check the possible speed compensation.

Best regards!

[sneaker_ger]

Taro (http://astrataro.wordpress.com/category/encode/x264/x264-bin/) builds recent versions with a lot of patches, including fgo and fade compensation.

[Leinad4Mind]

It's the first time I tried to encode using this GUI, and I've tried with a simple .avs:

DGSource("D:\Blu-Rays\GLOBAL_EDITION\5stars.dgi")

But the GUI takes too long to starting up. More than 2h...

MeGUI can use dgi file and encode right away, so why it takes so much time? Is Simplex264 creating a new index file?


EDIT: Maybe is he already encoding, but the info keep saying "starting up" lol (I think that it could tell the remaining time)


PS: Thanks sneaker_ger about that info. Glad to know too.

[LoRd_MuldeR]

Startup times are not related to the GUI. But you can try opening your AVS file in VirtualDub, just to be sure it opens correctly.

Anyway, if the progress indicator in the x264 GUI doesn't seem to update, then please try to run the exactly same AVS file with an unmodified x264 binary.

Quite possible the "Taro" build (or whatever you are using now) breaks compatibility, so the GUI cannot parse the progress message...

[Leinad4Mind]

In virtualDub, it opens correctly. AVSPMod too.

I've just change the 10bit version to an modified one. So I change the preference to 8bit (x264 is the original one), and tried, but the message still doesnt update.

Kinda strange...

[LoRd_MuldeR]

Please make a clean re-install of Simple x264 Launcher and try again. I cannot help you with modified versions.

If you still encounter problems, then please:
:logfile:

[Leinad4Mind]

You are right, with a unmodified version, it update.;)

With an modified one, the message appears too, but on the log. And we can see the same information too.

Thanks to explain. :)

[LoRd_MuldeR]

Please post a link to the exact modified x264 binary you are using and I might be able to implement a workaround...

[LoRd_MuldeR]

Well, here is a test version that adds support for the heavily modified progress output in Komisar's "kMod" build:
http://www.mediafire.com/download/n8tk1kmb0fbj6b8/x264_x64.2013-10-13.exe

Please note that this will probably remain an exception, as I certainly won't try to support any modified build out there ;)

(It's generally a very bad idea to modify the progress output, as this is likely to break x264 GUI's)

[Leinad4Mind]

Thanks, I'll try out later. :)

[kypec]

:thanks: a million for "Apply to all selected files" option when adding new jobs. Until now I had to click dozens of times on "Add job" with chosen template which was not that bad either when encoding series with more than 20 episodes at once but this option is simply amazing!
Thumbs up once again, Lord M! :D

[AGKnotUser]

Just tried to use version 2.24 with Windows 8.1 64 bit. When started a (paraphrasing) "...Launcher.exe cannot run in Windows Compatibility mode" message appears and asks to quit. If I go back to 2013-8-28 or 2013-10-13 it runs without incident. I'm not running in compatibility mode. Could you please have a look?

[LoRd_MuldeR]

Just tried to use version 2.24 with Windows 8.1 64 bit. When started a (paraphrasing) "...Launcher.exe cannot run in Windows Compatibility mode" message appears and asks to quit. If I go back to 2013-8-28 or 2013-10-13 it runs without incident. I'm not running in compatibility mode. Could you please have a look?

I think I have an idea. Will upload a fixed version when I'm back from work this evening...

[AGKnotUser]

I think I have an idea. Will upload a fixed version when I'm back from work this evening...

Thanks for the quick response.

[LoRd_MuldeR]

I think I have an idea. Will upload a fixed version when I'm back from work this evening...

New version is now available.

[AGKnotUser]

Thanks, that fixed the problem.

[AGKnotUser]

I see it does an avs script check now. It tells me my script doesn't look like an avs script when it is and the path and script name are displayed in 8.3 format not long file names. I have uploaded the script used.

[LoRd_MuldeR]

First of all, Simple x264 Launcher is passing short (8+3) file names to Avs2YUV because Avisynth (latest stable release) does not support Unicode file names :rolleyes:

Using short (8+3) file names is an unreliable hack, I know, but it's all we can do until they add proper Unicode support. x264 does support Unicode file names now, but until recently it had the same issue.

Secondly, the error message you are getting is not generated by Simple x264 Launcher, but by Avs2YUV. It probably means that your script has some kind of error and did not actually return a clip :eek:

When I try to run your script I get this:
infile 'C:\Temp\AVS_72~1.AVS' doesn't look like an avisynth script
error: Script error: there is no function named "SetMTmode"
(C:\Temp\AVS_72~1.AVS, line 2)

It's obviously because I don't use the "MT" branch of Avisynth and thus SetMTmode() doesn't exist. You will need Avisynth-MT to run this kind of script. Do you use Avisynth-MT ???

(There also are a bunch of plug-in's used in that script. Do you have all of the required plug-ins in your Avisynth "plugins" folder too?)

[AGKnotUser]

Thank you for the explanation. I'll check my script but it did run properly with a cmd file using avs2yuv. And yes, I am using the MT version AVISynth 2.6.

Edit: Ok, I guess I was just not used to seeing those messages as they did not appear in earlier versions of the launcher. The script seems to run though so no problem.

[LoRd_MuldeR]

Thank you for the explanation. I'll check my script but it did run properly with a cmd file using avs2yuv. And yes, I am using the MT version AVISynth 2.6.

Edit: Ok, I guess I was just not used to seeing those messages as they did not appear in earlier versions of the launcher. The script seems to run though so no problem.

After some more investigation, it seems the "doesn't look like an avisynth script" warning is not related to the error message I got at all.

Avs2YUV simply checks the input file name for an ".avs" extension and it will show a warning if no such extension is present. However that check is case-sensitive!

And since we are passing a "short" (8+3) file name - which happens to be all upper-case - Avs2YUV doesn't recognize the ".avs" extension ;)

[AGKnotUser]

And since we are passing a "short" (8+3) file name - which happens to be all upper-case - Avs2YUV doesn't recognize the ".avs" extension ;)

So now you have a choice to make. Unicode compatibility or a permanent avs script warning.

[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...

[szabi]

Hi

This error message pop up when I want to start the application:
http://abload.de/img/s264l_errutqvm.png

Of course aplication does not start.
What can be the solution?

bye
szabi

[LoRd_MuldeR]

What version are you using? If you are not using v2.25 (Build #610) yet, please install the latest update.

[szabi]

This one: x264_x64.2013-11-03.exe

bye
szabi

[LoRd_MuldeR]

This is not the latest (http://forum.doom9.org/showthread.php?p=1234822#post1234822) version. As I said before, please update to the latest version.

[szabi]

Ok, I installed this one x264_x64.2013-11-06.exe (http://code.google.com/p/mulder/downloads/detail?name=x264_x64.2013-11-06.exe&can=2&q=&sort=-uploaded).
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]

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/4ndl2hd1au4j706/x264_x64.2013-11-08.exe

[AGKnotUser]

FWIW, I have implemented a workaround for the Avs2YUV warning message:
http://www.mediafire.com/download/4ndl2hd1au4j706/x264_x64.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]

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? :confused:

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]

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 :confused:

Please try with current R21 (http://www.vapoursynth.com/downloads/vapoursynth-r21.exe) release. I will have a look at R22 as soon as it's done.


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]

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]

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]

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:
http://abload.de/img/simp_x264_lau05sw0.gif
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.)
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.