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

[LoRd_MuldeR]

Updated x264 binaries to r1096 (Komisar build).

[LoRd_MuldeR]

Updated x264 binaries to r1101 (Skystrife builds).

[Rodger]

Hallo Mulder, hier ein paar brand neue Resultate von mir:
Vista Home Premium 64bit, 4GB Ram, E8400@3537Mhz, P45 Mainboard.

Source: D:\Temp\MTV - h264_576p.avs
Params: --crf 22

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 7475 frames, 66.70 fps, 1604.27 kb/s
encoded 7475 frames, 66.78 fps, 1604.27 kb/s
encoded 7475 frames, 67.04 fps, 1604.27 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 7475 frames, 69.44 fps, 1604.29 kb/s
encoded 7475 frames, 69.53 fps, 1604.29 kb/s
encoded 7475 frames, 69.31 fps, 1604.29 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 7475 frames, 69.75 fps, 1604.29 kb/s
encoded 7475 frames, 69.65 fps, 1604.29 kb/s
encoded 7475 frames, 69.69 fps, 1604.29 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 7475 frames, 69.09 fps, 1604.29 kb/s
encoded 7475 frames, 69.47 fps, 1604.29 kb/s
encoded 7475 frames, 68.96 fps, 1604.29 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 7475 frames, 68.97 fps, 1604.29 kb/s
encoded 7475 frames, 69.13 fps, 1604.29 kb/s
encoded 7475 frames, 69.62 fps, 1604.29 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 7475 frames, 67.28 fps, 1604.29 kb/s
encoded 7475 frames, 67.37 fps, 1604.29 kb/s
encoded 7475 frames, 67.60 fps, 1604.29 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 7475 frames, 65.11 fps, 1604.29 kb/s
encoded 7475 frames, 65.07 fps, 1604.29 kb/s
encoded 7475 frames, 65.20 fps, 1604.29 kb/s

[LoRd_MuldeR]

Updated x264 binaries to r1107 (Komisar builds).

[LoRd_MuldeR]

Updated x264 binaries to r1109 (Skystrife builds).

My recent test shows significant speed-up between 32-Bit and 64-Bit:

Source: C:\TEMP\x264\sample.avs
Params: --crf 22 --subme 9 --me umh --analyse all --8x8dct --bframe 4 --b-adapt 2 --ref 6 --b-pyramid --trellis 2 --weightb --mixed-refs --direct auto

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 2262 frames, 55.68 fps, 457.49 kb/s
encoded 2262 frames, 57.09 fps, 457.49 kb/s
encoded 2262 frames, 57.88 fps, 457.49 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 2262 frames, 67.55 fps, 457.49 kb/s
encoded 2262 frames, 67.08 fps, 457.49 kb/s
encoded 2262 frames, 67.18 fps, 457.49 kb/s

That's a nice 20% speed-up for high (but not overkill) settings, even though the pipe is involved

[Atak_Snajpera]

Could you test with faster settings --subme 7 --bframe 3 --b-adapt 1 --ref 3 --trellis 1

[LoRd_MuldeR]

Yup: That's still a speed-up of ~1% to ~3%. Bigger fluctuations this time.

Source: C:\TEMP\x264\sample.avs
Params: --crf 22 --subme 7 --bframe 3 --b-adapt 1 --ref 3 --trellis 1

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 2262 frames, 201.07 fps, 441.97 kb/s
encoded 2262 frames, 202.20 fps, 441.97 kb/s
encoded 2262 frames, 202.18 fps, 441.97 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 2262 frames, 209.21 fps, 441.97 kb/s
encoded 2262 frames, 204.48 fps, 441.97 kb/s
encoded 2262 frames, 192.51 fps, 441.97 kb/s

[Atak_Snajpera]

Could you try with 1080p source?

[LoRd_MuldeR]

This time 64-Bit was slightly slower:

Source: C:\Crowdrun1080p.avs
Params: --crf 22 --subme 7 --bframe 3 --b-adapt 1 --ref 3 --trellis 1

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 500 frames, 3.46 fps, 20170.88 kb/s
encoded 500 frames, 3.54 fps, 20170.88 kb/s
encoded 500 frames, 3.53 fps, 20170.88 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 500 frames, 3.37 fps, 20170.88 kb/s
encoded 500 frames, 3.37 fps, 20170.88 kb/s
encoded 500 frames, 3.36 fps, 20170.88 kb/s

[Atak_Snajpera]

Could you try again with the same source but with your insane settings?

[LoRd_MuldeR]

Originally Posted by Atak_Snajpera

Could you try again with the same source but with your insane settings?

No, takes too long. Maybe tomorrow

[LoRd_MuldeR]

Updated x264 binaries to r1113 (Skystrife builds).

[hd1080]

Can i do with your programm 2pass encodes?

[LoRd_MuldeR]

Originally Posted by hd1080

Can i do with your programm 2pass encodes?

Sure. But you need to run both passes manually, each with the required parameters. There's no automated 2-Pass implemented, if you mean that...

[LoRd_MuldeR]

Updated x264 binaries to r1114 (builds taken from x264.nl).

[henryho_hk]

May I know what is the difference between pipebuf.exe and normal "|" piping?

I tried "|"'ing 32-bit mencoder's output to 64-bit x264.exe but it failed.

[LoRd_MuldeR]

Originally Posted by henryho_hk

May I know what is the difference between pipebuf.exe and normal "|" piping?

I tried "|"'ing 32-bit mencoder's output to 64-bit x264.exe but it failed.

The "|" operator will only work in the Windows Commandline Interpreter (aka "cmd.exe"), but it will not work in CreateProcess() or WinExec() natively.

So if you don't use my 'pipebuf.exe' tool, then you will need to use 'cmd.exe' instead and pass the commandline via "/c" option.

The advantage of 'pipebuf.exe' is that it has a nicer syntax (cmd.exe has a pretty bizarre way of handling quotes) and that you are able to specify the pipe buffer size.

Internally 'cmd.exe' will create the pipe in the very same way that 'pipebuf.exe' usese, I guess...

[LoRd_MuldeR]

Updated x264 binaries to r1120 (Skystrife builds).

[LoRd_MuldeR]

Updated x264 binaries to r1125 (builds taken from x264.nl).

[puffpio]

when doing the benchmark, i notice that the first benchmark (the 32 bit one) only uses 1 of my cpu's
while just hitting start calls the 64 bit version and it uses both cpu's...

thoughts? running windows 7 and your latest version w/ x264 1125