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

[ACrowley]

Not exactly. It only shows the last eight parameters used and it only adds a new item to the list, if the current parameters are different from the previous ones!
This way you don't end up with a bunch of identical items in your history list, if you run several encodes with the very same parameters...

Anyway, you can simply delete all the "history_n" entries in your "%APPDATA%\x264_x64.ini" file or rename/move/delete the entire file, if that makes you feel better :p
THX :rolleyes:

[LoRd_MuldeR]

Updated x264 to r1292 (Komisar's builds). Download link in first post updated!

[ACrowley]

again a request

Cab you add a minimize Button please ?

[LoRd_MuldeR]

again a request

Cab you add a minimize Button please ?

Will look for a solution. The "tool window" doesn't have a minimize button. You can use "Minimze" from the taskbar icon for the moment...

[ACrowley]

Will look for a solution. The "tool window" doesn't have a minimize button. You can use "Minimze" from the taskbar icon for the moment...

Taskbar icon ..ok

Another Thing :)
A Time Overview/Hint would be nice.
Maybe the Time where you start the encoding and the elapsed Time in the Final Stats

Ofcourse i know its a "simple x264 launcher only" and there are enough frontends out there....

[LoRd_MuldeR]

Updated x264 to r1301 (Komisar's builds). Download link in first post updated!

[kypec]

LM: Maybe you could add and then regularly update info about which version of x264 is included with your launcher at the first post of this thread also?

[LoRd_MuldeR]

LM: Maybe you could add and then regularly update info about which version of x264 is included with your launcher at the first post of this thread also?

The info is here ;)

Last edited by LoRd_MuldeR; Today at 11:54. Reason: Update x264 binaries to r1301

Also you can update x264 yourself. I just update the package now and then, so less experienced users don't get/keep an outdated x264 binary...

[kypec]

Sorry, didn't notice that tiny edit notes below. Yeah, I know I can use whatever x264 build instead of packaged one. Just wanted to make it more clear for not so experienced users/visitors of this thread. ;)

[Yoshiyuki Blade]

Droppin by to say thanks for pointing me to this program. :)
I might switch over to 64-bit encoding finally!

[dstln]

And if anyone still cares about the benchmarks, I was burning in/testing a new cpu last night.

Source: C:\temp\test.avs
Preset: Medium
Tuning: None
Profile: High
Params: --level 4.1 --thread-input --deblock -2:-2 --bframes 7 --b-adapt 2 --direct auto --ref 10 --merange 24 --me umh --subme 10 --partitions all --trellis 2 --psy-rd 1.0:0.0 --no-dct-decimate --no-fast-pskip --psnr --ssim --sar 33:27

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 9750 frames, 7.53 fps, 2582.80 kb/s
encoded 9750 frames, 7.58 fps, 2582.80 kb/s
encoded 9750 frames, 7.50 fps, 2582.80 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 9750 frames, 8.68 fps, 2582.80 kb/s
encoded 9750 frames, 8.59 fps, 2582.80 kb/s
encoded 9750 frames, 8.68 fps, 2582.80 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 9750 frames, 8.76 fps, 2582.80 kb/s
encoded 9750 frames, 8.74 fps, 2582.80 kb/s
encoded 9750 frames, 8.53 fps, 2582.80 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 9750 frames, 8.80 fps, 2582.80 kb/s
encoded 9750 frames, 8.76 fps, 2582.80 kb/s
encoded 9750 frames, 8.72 fps, 2582.80 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 9750 frames, 8.64 fps, 2582.80 kb/s
encoded 9750 frames, 8.59 fps, 2582.80 kb/s
encoded 9750 frames, 8.66 fps, 2582.80 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 9750 frames, 8.63 fps, 2582.80 kb/s
encoded 9750 frames, 8.60 fps, 2582.80 kb/s
encoded 9750 frames, 8.69 fps, 2582.80 kb/s


further proof that 2m buffer seems to perform best, and with a nice ~1.16x speedboost over 32-bit x264

[LoRd_MuldeR]

Cab you add a minimize Button please ?

Done.

[Keiyakusha]

I just downloaded and re-downloaded latest ver but don't see minimize button... :confused:

[LoRd_MuldeR]

I just downloaded and re-downloaded latest ver but don't see minimize button... :confused:

http://img188.imageshack.us/img188/9380/minimize.png

:confused: :confused: :confused:

[Keiyakusha]

http://img188.imageshack.us/img188/9380/minimize.png

:confused: :confused: :confused:

Ahaa! I didn't think I need to start the encode, I expected to see it near the "close" button! :p
Thanks for this useful feature!

[LoRd_MuldeR]

Ahaa! I didn't think I need to start the encode, I expected to see it near the "close" button! :p

I think minimizing the window is only of interest for the user while encoding ;)

(BTW: Tool windows cannot have a "normal" minimize buttons)

[prOnorama]

Thanks for this LordMulder, I was looking for a MeGUI replacement just to do the encoding part, I just want to encode using the latest x264 32 bit (MeGUI is contantly out of date and sometimes buggy)

Did a test and it worked with the latest x264 32 bit (1310) using my own custom command line :)

I know this is not meant as a full GUI but it would be nice if you can store custom command lines under (a few) profiles and give them your own name (like "DXVA 720p HQ" or "DXVA 1080p SHQ").

An option to auto-save the log file would be nice too (especially for lazy people like me :p )

Cheers

PS: there's a small typo in the log-> "Analayzing Source File" ->
"Analyzing Source File"

[prOnorama]

Bummer, it doesn't let you set an exact bitrate (like 7238), just rounded to the nearest 100, if I enter it manually on the command line I get a "Please don't specify the "--bitrate parameter", I will do this for you, if required" warning.

[Darth Viorel]

You can set an exact bitrate, but the automatic correction will change wron values. So as 7 kbit/sec isn't allowed, it will make 100 out of it. If you just paste your desired bitrate into the box even 7238 is possible.

[egrimisu]

great too, a queue would be excelent. Thanks

[LoRd_MuldeR]

Bummer, it doesn't let you set an exact bitrate (like 7238), just rounded to the nearest 100, if I enter it manually on the command line I get a "Please don't specify the "--bitrate parameter", I will do this for you, if required" warning.

The behavior of the SpinEdit control to enforce the Min value isn't very convenient, I know.

However you can enter the desired bitrate manually using number-keys. But the intermediate value must not be too small.

So don't erase the complete number. Better change one digit at a time...

[Zarxrax]

Could I get a sample command line for how to use avs2yuv and pipebuf with x264? Thanks.

[LoRd_MuldeR]

I'd say look at my GUI. It prints out the full command-line to the log/progress window ;)

[Zarxrax]

Oh, ok :)

[Blue_MiSfit]

This is a great tool, Lord_Mulder!!!

I will be using this for all my x264 encoding needs for the time being!

~MiSfit

[LoRd_MuldeR]

Updated x264 to r1310 (Komisar's builds). Also made the "Bitrate" SpinEdit box easier to edit. Download link in first post updated!

[McArty]

Thank you LoRd_MuldeR for your continuous work.

P.S.That minimize button was very useful for me.

[turbojet]

Is there any chance of being able to type in the path\file boxes?

Also since I notice x86 x264 is faster then x64 on first pass or really fast settings is there any chance of adding an option to use x86 on first pass, x64 on second pass?

Also an option to use x86 x264 would be very useful for everyone that are still on x86 OS's and want to use a simple GUI.

[LoRd_MuldeR]

Is there any chance of being able to type in the path\file boxes?

Nope :p

Also since I notice x86 x264 is faster then x64 on first pass or really fast settings is there any chance of adding an option to use x86 on first pass, x64 on second pass?

Also an option to use x86 x264 would be very useful for everyone that are still on x86 OS's and want to use a simple GUI.

Runtime x86 -vs- x64 is already implemented :D

[sjakke]

Image in first post is broken.

[LoRd_MuldeR]

Blame ImagesHack. Will re-upload if it remains broken...

[turbojet]

Nope :p

Bummer, just a usual routine for me.

Runtime x86 -vs- x64 is already implemented :D

Ah wasn't aware of that never tried on an x86 OS. How an option in x64 mode an option to use x86 x264 for first pass and an option to use x86 for all encodes?

Also any chance of a process priority option and/or a pause/resume option through something like PsSuspend (http://technet.microsoft.com/en-us/sysinternals/bb897540.aspx)?

[Buggle]

Mulder, I'm having some issues here. First, launcher reports me it is using MMX and SSE2slow. As I'm on a X2 Brisbane 5000+, that doesn't make sense (it supports MMX, Extended 3DNow!, SSE, SSE2, SSE3).
Then, I was wondering if there is an option to select/set the buffer size to use for the encode, since there's no one-size-fits all. I've scrolled through this threat and looked for an ini/inf file in the package, but can't find one. Maybe I'm just blind, that could be the case.

[Buggle]

Some benchmarks from me. The clip is a trim() of Lord of War, with double DeGrainMedian, Spline36 resize (hardly, but it's in the filterlist) and some Undots. The x264 used is release 1318 from x264.nl
Source: D:\LORD_OF_WAR\VTS_01_1.avs
Preset: Slower
Tuning: Film
Profile: High
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 5001 frames, 5.50 fps, 1106.06 kb/s
encoded 5001 frames, 5.39 fps, 1106.06 kb/s
encoded 5001 frames, 5.39 fps, 1106.06 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 5001 frames, 5.91 fps, 1106.06 kb/s
encoded 5001 frames, 5.91 fps, 1106.06 kb/s
encoded 5001 frames, 5.38 fps, 1106.06 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 5001 frames, 4.98 fps, 1106.06 kb/s
encoded 5001 frames, 6.01 fps, 1106.06 kb/s
encoded 5001 frames, 5.96 fps, 1106.06 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 5001 frames, 5.97 fps, 1106.06 kb/s
encoded 5001 frames, 6.01 fps, 1106.06 kb/s
encoded 5001 frames, 6.18 fps, 1106.06 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 5001 frames, 6.18 fps, 1106.06 kb/s
encoded 5001 frames, 6.03 fps, 1106.06 kb/s
encoded 5001 frames, 6.06 fps, 1106.06 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 5001 frames, 6.15 fps, 1106.06 kb/s
encoded 5001 frames, 6.11 fps, 1106.06 kb/s
encoded 5001 frames, 6.08 fps, 1106.06 kb/s

[Dark Shikari]

Mulder, I'm having some issues here. First, launcher reports me it is using MMX and SSE2slow. As I'm on a X2 Brisbane 5000+, that doesn't make sense (it supports MMX, Extended 3DNow!, SSE, SSE2, SSE3).No, that's perfectly normal for an Athlon 64.

[Buggle]

No, that's perfectly normal for an Athlon 64.
How come? I thought x264 is using/can use SSE3 as well.

[Dark Shikari]

How come? I thought x264 is using/can use SSE3 as well.Only as a workaround for a weakness of the Pentium 4E.

[LoRd_MuldeR]

Ah wasn't aware of that never tried on an x86 OS. How an option in x64 mode an option to use x86 x264 for first pass and an option to use x86 for all encodes?

I don't see how this would be useful...

Also any chance of a process priority option and/or a pause/resume option through something like PsSuspend (http://technet.microsoft.com/en-us/sysinternals/bb897540.aspx)?

No need to use an external tool. As I have created the process(es), I already have the handles to suspend/resume them directly.

And if you click the "X" button, the encoding will be paused. Click "No" to resume...

[Fr4nz]

Hi Lord, it seems that no one asked you this question in this thread: is it possible to implement a "shutdown" function (like the one present in MeGUI) in your launcher? :)

[LoRd_MuldeR]

Hi Lord, it seems that no one asked you this question in this thread: is it possible to implement a "shutdown" function (like the one present in MeGUI) in your launcher? :)

Possible indeed. But not currently planned...

[turbojet]

I don't see how this would be useful...

Fast x264 settings run faster with x86 x264. Including fast first passes which I see are ~5-10% faster. For example:

1280x720, preset medium, 2000 kbps, windows 7 x64, athlon ii 620

x86 from command line
pass 1: encoded 1277 frames, 48.40 fps, 1970.02 kb/s
pass 2: encoded 1277 frames, 28.44 fps, 2000.92 kb/s

x64 launcher
[First Pass]
encoded 1277 frames, 45.61 fps, 1969.83 kb/s
[Second Pass]
encoded 1277 frames, 29.02 fps, 2000.89 kb/s

Also I did a benchmark with the same CPU/source.

Preset: Ultrafast
Tuning: None
Profile: High
Params:

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 1277 frames, 51.93 fps, 1083.92 kb/s
encoded 1277 frames, 52.19 fps, 1083.92 kb/s
encoded 1277 frames, 51.82 fps, 1083.92 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 45.61 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 45.61 fps, 1083.92 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 1277 frames, 45.61 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s
encoded 1277 frames, 47.30 fps, 1083.92 kb/s


No need to use an external tool. As I have created the process(es), I already have the handles to suspend/resume them directly.

And if you click the "X" button, the encoding will be paused. Click "No" to resume...

Thanks that works.

[McArty]

And if you click the "X" button, the encoding will be paused. Click "No" to resume...
That is good to know, i thought wasn't implemented. Very useful for my slow cpu ;.)

p.d. Only that doing so is impossible minimize...

[psycoxl]

MeGUI does show you the complete commandline for each profile. So you can simply copy&paste ;)

Anyway, if you want to use MeGUI profiles, why not simply use MeGUI?



Not planned. But I have included the sources, so feel free to hack that in :D

you can't use it with the x264 x64 (or am i wrong)

[ACrowley]

That is good to know, i thought wasn't implemented. Very useful for my slow cpu ;.)

p.d. Only that doing so is impossible minimize...

mhh doesnt work here in 2nd Pass.

It was working before but only after 10-10sec until it suspends and cpu load goes down.

But in this Moment it doesnt work anymore in 2nd Pass here ?

[Buggle]

Seeing the attention went to the second part of my question about the SSIMs, I would like to ask the first part again to LordMulder: is it, or will it be, possible to select a custom buffer size? I've searched, but didn't find information about this.

[Darth Viorel]

I really like this small GUI but sometimes it crashes right after it finishes encoding. I can see the log in the background but I get a windows error message saying that the launcher.exe stopped working. It happens randomly and I can't figure out why. What I can exclude is my hardware, it is stable and not the issue.

[LoRd_MuldeR]

You mean VBV Buffer or Pipe Buffer? The former can be adjusted with "--vbv-bufsize". The latter is hardcoded to 4 MB in "encode" (non-benchmark) mode.

[LoRd_MuldeR]

I really like this small GUI but sometimes it crashes right after it finishes encoding. I can see the log in the background but I get a windows error message saying that the launcher.exe stopped working. It happens randomly and I can't figure out why. What I can exclude is my hardware, it is stable and not the issue.

Never seen anything like that :confused:

[Buggle]

You mean VBV Buffer or Pipe Buffer? The former can be adjusted with "--vbv-bufsize". The latter is hardcoded to 4 MB in "encode" (non-benchmark) mode.
I meant the pipe buffer. Would it be possible to implement a custom (drop down or so) option to select your own? Depending on the different uses (fast/slow settings and low/heavy filtering for instance) this could provide for some extra benefit speedwise.

[Buggle]

Never seen anything like that :confused:
I've experienced this as well, one time.