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

[LoRd_MuldeR]

what buffersize is it using, when you dont run the benchmark?

4 Megabyte

[Rodger]

I remember it was 1MB

[LoRd_MuldeR]

I remember it was 1MB

Then you remember wrong. Look at the source code! If my eyes don't fool me, then it's 4 MB ;)

[MajorX]

@LoRd_MuldeR
can u add a custom setting option so that we can change x264 parameters like ref, me_range, rc_lookahead, bframes etc.

[LoRd_MuldeR]

@LoRd_MuldeR
can u add a custom setting option so that we can change x264 parameters like ref, me_range, rc_lookahead, bframes etc.

No I can't. Because it is already there :p

http://img696.imageshack.us/img696/8918/customoptions.png

[MajorX]

No I can't. Because it is already there :p

http://img696.imageshack.us/img696/8918/customoptions.png
Oh yeah, now i can use custom parameters, thanks. :)

Edit:when i use --subme 10 it always encode with --subme 9 not 10 why?
(i use 10-bit x264)

[LoRd_MuldeR]

Oh yeah, now i can use custom parameters, thanks. :)

Edit:when i use --subme 10 it always encode with --subme 9 not 10 why?
(i use 10-bit x264)

SubME > 9 requires (Trellis == 2) && (AQ != 0). I guess that at least one of these conditions doesn't hold true for your settings.

I would recommend to NOT tweak such options manually (unless you have a very good reason to do so), but use the preset system instead!

SubME 10 is enabled in "veryslow" preset. Of course that presets contains all options required for SubME 10 to work...

[MajorX]

can it possible to use subme 10 with trellis= 2 & aq=2:0.60? i use slow preset.

[LoRd_MuldeR]

can it possible to use subme 10 with trellis=2 & aq=2:0.60?

Sure.

i use slow preset.

Time to upgrade to "veryslow", if you want SubME 10. If "veryslow" is too slow for you, then go with the SubME mode that "slow" uses.

[egrimisu]

hi lord,
can i use a 10bit x264 with the laucher as i use the 8bit one? does the 10bit preset profiles have the same config as the 8bit one? thanks.

[LoRd_MuldeR]

hi lord,
can i use a 10bit x264 with the laucher as i use the 8bit one? does the 10bit preset profiles have the same config as the 8bit one? thanks.

10-Bit is a compile-time option. So you will have to replace the x264 binary(ies) with 10-Bit build(s). That's all.

AFAIK there are no bitness-specific CLI options in x264...

[naoan]

any plan to have simple preset option? and uh, batch...

[LoRd_MuldeR]

any plan to have simple preset option?

Support for Presets (and Tunings) has already been implemented long ago :confused:

and uh, batch...

Not planned, sorry.

[MajorX]

Any Update?

[LoRd_MuldeR]

There's nothing that would require an update at the moment, I think. You can update your x264 independent from the GUI...

[the_weirdo]

There's nothing that would require an update at the moment, I think. You can update your x264 independent from the GUI...

Actually, I think you should update avs2yuv to this version (http://forum.doom9.org/showthread.php?p=1527698#post1527698). But users can also update it themself, of course.

[LoRd_MuldeR]

Actually, I think you should update avs2yuv to this version (http://forum.doom9.org/showthread.php?p=1527698#post1527698). But users can also update it themself, of course.

Will have a look at that one...

:thanks:

[LoRd_MuldeR]

I have uploaded a new package:

x264 has been updated to r2106 and avs2yuv has been updated v0.24bm2.

[kypec]

When I updated my x264 binaries to komisar's build revision 2120 Launcher refuses to show help screen dialog after Show Help Screen click. Only error message pops up "Sorry, failed to generate the help screen!"
I can't understand what could go wrong as I've been updating x264 binaries myself many times before without problems so I know what to do and how to do it (rename executable to x264.exe and x264_x64.exe respectively)...
Has anything changed in console output of x264 since r2106 recently? :confused:

[Nevilne]

I'm not sure, but even
"apps\x264komisar.exe" --fullhelp > x264.txt

crashes on 21kb :o

Haven't used his builds for long time tho so not sure if it's recent stuff.

[komisar]

first build is buggy... sorry. i'm update it with patch http://privatepaste.com/c943123095 ... this is ffmpeg fault

[kypec]

:thanks: a lot! You're the man, komisar :)

[LoRd_MuldeR]

komisar, any chance you update the "x264 libpack" on your site? Latest x264 doesn't like the FFMS2 included in your current pack.

:thanks:

[stinman]

What now? Last post is Dec 7th- are things fixed now? Can we add new x264 builds to the simple x264 launcher
May I ask what are the difference from komisar x264 and darkshikari x264 or jeeb... and why you choose komisar builds? Just wondering and learning. Thanks.

[LoRd_MuldeR]

You can always update x264.exe and x264_x64.exe with the build of your choice, as long as the CLI syntax hasn't changed - which did not happen recently.

Builds by different people mostly differ which GCC version was used to build and by the versions of the "third-party" libs (libavcodec, libavformat, FFMS2, etc) included.

Some builds may also include new/experimental patches. Usually this will be noted...

[aufkrawall]

Is there a way to manually define FPS?
When I try --fps command it tells me that *it* would define it if needed but it's doing something wrong. ;)
According to MediaInfo the output has 1.500 fps, but input file has 30.
I'd like to define an output file with 30 fps.

[LoRd_MuldeR]

This GUI was mainly written to allow encoding with 64-Bit x264 from a 32-Bit Avisynth.

For this reason we use a 32-Bit 'avs2yuv' instance to read the AVS script and then pipe over the "raw" data to the 64-Bit 'x264' process.

Of course x264 can't know the frame rate of the original source in this case. So the GUI will set the appropriate "--fps" for you.

(Now it should be obvious why we can't allow the user to specify "--fps" itself)

[aufkrawall]

(Now it should be obvious why we can't allow the user to specify "--fps" itself)
It is now, thank you. :)
But it's odd: The result is played with 30 fps but MediaInfo says 1.5.
I can remuxe it and define 30 fps, but I'd like to save this stepp.

The input is Fraps RGB, btw.

Is there really no way to force x264 via GUI to write 30 fps into the file info?
It's just a bureaucratic issue, not a technical one.

[LoRd_MuldeR]

If your input is from an Avisynth script, I would recommend to use AssumeFPS() or ChangeFPS(), whatever is the suitable one.

(The former just "overwrites" the FPS value, but does not add or remove any frames. The latter actually converts the FPS, by duplicating/skipping frames as needed)

If you don't use Avisynth input yet, make a simple text file (input.avs) and put the following content in:

FFVideoSource("C:\Path to your input\source.avi")
AssumeFPS(25.0) #could also put ChangeFPS(25.0) at this place

(Make sure you have Avisynth (http://sourceforge.net/projects/avisynth2/files/AviSynth%202.5/) and the FFMS2 (http://code.google.com/p/ffmpegsource/downloads/list) plug-in installed for this to work)

[aufkrawall]

Somehow it fails with "Analyzing the source video".
I just copied the ffms plug-in into the the plugins folder, is this correct?

But it's really not urgent. I have to use some merging tool anyway to merge the splitted Fraps avi files and while this I can specify FPS afterwards.

Btw: Your Simple x264 Launcher seems to be the only x264 converter with GUI that correctly encodes Fraps RGB videos to x264 I444/RGB. :thanks:
All other tools fail, colors aren't right etc.

Edit: One more question: Why is --tune forbidden?

[LoRd_MuldeR]

Somehow it fails with "Analyzing the source video".

Try to open your AVS script in VirtualDub and see what happens...

I just copied the ffms plug-in into the the plugins folder, is this correct?

If you mean the Avisynth plug-in folder, then you did right.[/QUOTE]

But it's really not urgent. I have to use some merging tool anyway to merge the splitted Fraps avi files and while this I can specify FPS afterwards.

Btw: Your Simple x264 Launcher seems to be the only x264 converter with GUI that correctly encodes Fraps RGB videos to x264 I444/RGB. :thanks:
All other tools fail, colors aren't right etc.

That's not a feature of the GUI. In fact it should work with any x264 GUI, given it is used with an up-to-date x264 binary that has FFMS2 enabled.

Edit: One more question: Why is --tune forbidden?

...because there is a combo box for this option in the GUI. Setting "--tune" twice would be pointless ;)

[aufkrawall]

Try to open your AVS script in VirtualDub and see what happens...

It gives unknown import filter error with code 80040154.


That's not a feature of the GUI. In fact it should work with any x264 GUI, given it is used with an up-to-date x264 binary that has FFMS2 enabled.

They always mess around with color spaces.
Either they allow only YUV12/I420, they change it without saying, they use only I420 or they mess it up in some other way.
Either I use a GUI because it makes things easier or I don't use it at all and learn x264 CLI or AviSynth.
Your program simply works, it decodes flawlessly in RGB mode and converts it to the chosen CS without mess.
I just wished there would be a GUI option for the 10bit x264 version. Would be very easy to implement. :)
Btw: The x264 version which is delivered by the current version of your program doesn't accept --range pc.


...because there is a combo box for this option in the GUI. Setting "--tune" twice would be pointless ;)
Oops.
Hm, when using --tune fastdecode it simply seems to be --no cabac, at least when using crf 0.
The problem with x264 RGB is its high CPU usage. Best compromise of decoding speed and compression seems to be placebo preset and no cabac.

[LoRd_MuldeR]

According to the x264 manpage, the "fastdecode" tuning does exactly the following:

--no-cabac --no-deblock --no-weightb --weightp 0

Though, AFAIK, the lossless mode doesn't use B-Frames anyway and Deblocking also is irrelevant in that case.

[aufkrawall]

Though, AFAIK, the lossless mode doesn't use B-Frames anyway and Deblocking also is irrelevant in that case.
That it must be, the file size doesn't even differ by one KB between festdecode and no cabac.

Uhm, the following may be a bit OT ;) , I hope it's ok though:
Do you know if/when compatibility for 10bit RGB of x264 could be realized?
It could dramatically help to reduce bitrate and so decoding power.

[LoRd_MuldeR]

Do you know if/when compatibility for 10bit RGB of x264 could be realized?

I don't understand this question. x264 does support RGB encoding as well as 10-Bit encoding.

It could dramatically help to reduce bitrate and so decoding power.

If you refer to 10-Bit encoding here, then 10-bit encoding indeed does improve the compression efficiency (i.e. the "quality per bit" ratio), compared to 8-Bit.

However 10-Bit is significant slower at both, encoding and decoding. After all using "only" 8-Bit is nothing but a speed-up trick ;)

(Also hardware support for 10-Bit H.264 is pretty much none-existing. Well, the same applies to H.264 RGB mode, i.e. "High 4:4:4" Profile)

[aufkrawall]

I don't understand this question. x264 does support RGB encoding as well as 10-Bit encoding.

But not both at a time, 10bit version supports only I444 colorspace (and lower).


If you refer to 10-Bit encoding here, then 10-bit encoding indeed does improve the compression efficiency (i.e. the "quality per bit" ratio), compared to 8-Bit.

However 10-Bit is significant slower at both, encoding and decoding. After all using "only" 8-Bit is nothing but a speed-up trick ;)

With some earlier tests I couldn't play I444 8bit crf 0 smoothly, but now it does (I must have made some mistakes in the past).
But CPU usage is not lower than with 10bit, must be because bitrate is 80mbit/s lower with 10bit.


(Also hardware support for 10-Bit H.264 is pretty much none-existing. Well, the same applies to H.264 RGB mode, i.e. "High 4:4:4" Profile)
Yey, it's only usable with PCs, and only with correctly configured ones.
And of course only with enough powerful ones. ;)
I wonder if x264 RGB crf 0 with preset placebo can be played smoothly on a 4.5Ghz Sandy Bridgy i7. :D

[honza567]

Hi,

firstly I want to say, that the Simple x264 luncher is the best x264 encoder tool I ever met, becouse of his easy update for a new x264 version and low requirments to RAM and last but not least open all x264 settings.


I know that my question is silly, but I spent too much to done it just by myself and without success.

I can´t change resolution of output file.

Even I tried to use "Show help screen."

resize:[width,height][,sar][,fittobox][,csp][,method] - This fine, but I still must put some mistakes into, when it didn´t work. Even when I thought that units are filled rigthly. ... Or can I miss any of those inner parameters?

Should be "--" before this.. or should I prezerve "[]" or commas?

Let´s say for example. We need to get:
width 320,
height 320
sar is: 1 here (I suppose)
fittobox... I don´t know. Let´s use some recommended
csp: again I don´t know which one. Let´s use some recommended
method: spline

Could you write me what exactly to write into CLI (Custom parameters x264) for change resolution?

Thanks a lot

[aufkrawall]

Could you write me what exactly to write into CLI (Custom parameters x264) for change resolution?

Try something like this:
"--video-filter resize:width=1920,height=1080"
Some more info:
http://mewiki.project357.com/wiki/X264_Settings#resize

[Temuthril]

--video-filter resize:320,320,1:1,method=spline

[honza567]

Ouch. It works even with modifications

Thanks a lot guys

... Another my IQ test fail. :D :p

[komisar]

komisar, any chance you update the "x264 libpack" on your site? Latest x264 doesn't like the FFMS2 included in your current pack.
Sorry for the delay... Libpacks updated 2012-01-19

[LoRd_MuldeR]

Sorry for the delay... Libpacks updated 2012-01-19

Great :thanks:

[donfrenchiano]

Has anyone been able to get the 64bit to work under wine in linux? If i do everything from the command line it seems to work fine but the gui gives me an error, something like it can't get normal handles. The gui works fine if i run it in a 32bit environment.

[LoRd_MuldeR]

Has anyone been able to get the 64bit to work under wine in linux? If i do everything from the command line it seems to work fine but the gui gives me an error, something like it can't get normal handles. The gui works fine if i run it in a 32bit environment.

This software was never written to run under Wine. It may work or not, I have no idea.

Anyway, running under Wine only makes sense, if you need Avisynth, because there is no native Avisynth port for Linux.

But then you should run only Avisynth/AVS2YUV under Wine. Pipe the output to a native Linux x264 from there!

(The simple x264 launcher cannot do this)

[darknoob]

First off thanks for the GUI lord it works great. My question is regarding the first pass log info. I use the two pass method with placebo preset, the first pass log does appear briefly before the second pass starts, but its for like 2 seconds, and I don't see it saved anywhere. I would like to see that final rate factor number to verify my compressibility on the first pass. Lord is there a cmd I can use to get this?

thanks

[LoRd_MuldeR]

My simple x264 launcher currently does not retain detailed information of the first of a 2-Pass encode. Sorry.

(The "2-Pass report" only includes a quick "one line" summary of the first pass)

[LoRd_MuldeR]

Here is an all new but experimental(!) version of the "Simple x264 Launcher" application:

http://img17.imageshack.us/img17/6384/simplex264launcher64bit.th.png (http://img17.imageshack.us/img17/6384/simplex264launcher64bit.png)

Be aware that this really is an early version! But I hope that this will develop into something useful ;)

[MajorX]

Thanks LoRd_MuldeR. :)
I will try this new version of x264 Launcher.

Edit: Please help i got this error when i try to open x264 Launcher.

http://img831.imageshack.us/img831/3561/errorwr.jpg

[LoRd_MuldeR]

Hmm, Google says the code 0xC0000409 refers to a STATUS_STACK_BUFFER_OVERRUN.

Smells like we have an infinite recursion somewhere :eek:

I need some more details. Does that crash happen before the main window becomes visible ???

Cannot reproduce on my Windows XP machine

[LoRd_MuldeR]

Here is a slightly updated version: 2-Pass encoding should now be working.