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

[puffpio]

update : nevermind
even though the process was listed using 50%, the total cpu usage was 100%..i think the task manager was not reporting it correctly

[puffpio]

Source: D:\temp\090306212759.avs
Params: --crf 22 --ref 5 --mixed-refs --bframes 3 --b-adapt 2 --b-pyramid --weightb --deblock -1:-1 --subme 8 --trellis 2 --partitions all --8x8dct --me umh --thread-input --no-psnr --no-ssim

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 1784 frames, 1.95 fps, 4160.33 kb/s
encoded 1784 frames, 2.18 fps, 4160.11 kb/s
encoded 1784 frames, 1.98 fps, 4160.33 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 1784 frames, 2.37 fps, 4160.11 kb/s
encoded 1784 frames, 2.32 fps, 4160.11 kb/s
encoded 1784 frames, 2.18 fps, 4160.11 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 1784 frames, 2.43 fps, 4160.11 kb/s
encoded 1784 frames, 2.35 fps, 4160.11 kb/s
encoded 1784 frames, 2.16 fps, 4160.11 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 1784 frames, 2.41 fps, 4160.11 kb/s
encoded 1784 frames, 2.42 fps, 4160.11 kb/s
encoded 1784 frames, 2.17 fps, 4160.11 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 1784 frames, 2.39 fps, 4160.11 kb/s
encoded 1784 frames, 2.42 fps, 4160.11 kb/s
encoded 1784 frames, 2.22 fps, 4160.11 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 1784 frames, 2.39 fps, 4160.11 kb/s
encoded 1784 frames, 2.48 fps, 4160.11 kb/s
encoded 1784 frames, 2.20 fps, 4160.11 kb/s

[LoRd_MuldeR]

Originally Posted by 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

I'm passing "--threads auto" to x264, so the problem (if there is one) shouldn't be on my side.

Anyway, if you are using a CPU with "Hyperthreading" (2 virtual cores per physical core), then 50% total load means that all physical cores are at 100% load, as Windows Taskmanager will only see virtual cores.

Of course it may also happen that your are bottlenecked by the input (decoder throughput, avisynth script) ...

[HymnToLife]

Not a tremendous speed boost here either.
Source is 1080p anime (creditless opening of Michiko e Hatchin), settings are the ones I use for my real-world encodes (except for the CRF 18, I normally use 2 pass bitrate mode and the final RF is usually something between 19-20).
CPU is Phenom II 940 @ 3.2 GHz, running Vista 64. I also updated x264 to r1127 from x264.nl.
I'm going to run another test with standard definition (DVD) anime soon-ish.

Source: C:\software\x264_x64.2009-03-08\michiko_op.avs
Params: --crf 18 --ref 8 --mixed-refs --no-fast-pskip --bframes 4 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock -1:-1 --subme 7 --trellis 1 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --merange 22 --psy-rd 0.8:0 --thread-input --no-dct-decimate --no-psnr --no-ssim

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 1944 frames, 5.02 fps, 7196.12 kb/s
encoded 1944 frames, 5.02 fps, 7196.12 kb/s
encoded 1944 frames, 5.03 fps, 7196.12 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 1944 frames, 5.13 fps, 7197.35 kb/s
encoded 1944 frames, 5.13 fps, 7197.35 kb/s
encoded 1944 frames, 5.16 fps, 7197.35 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 1944 frames, 5.16 fps, 7197.35 kb/s
encoded 1944 frames, 5.17 fps, 7197.35 kb/s
encoded 1944 frames, 5.19 fps, 7197.35 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 1944 frames, 5.21 fps, 7197.35 kb/s
encoded 1944 frames, 5.17 fps, 7197.35 kb/s
encoded 1944 frames, 5.16 fps, 7197.35 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 1944 frames, 5.18 fps, 7197.35 kb/s
encoded 1944 frames, 5.17 fps, 7197.35 kb/s
encoded 1944 frames, 5.15 fps, 7197.35 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 1944 frames, 5.18 fps, 7197.35 kb/s
encoded 1944 frames, 5.16 fps, 7197.35 kb/s
encoded 1944 frames, 5.15 fps, 7197.35 kb/s

[HymnToLife]

Creditless first ending of Sky Girls (DVD, IVTC and resizing to 848x480 were done beforehand).
Once again, real-world settings, and once again, a very minimal speed increase.
In both this case and the one above, a buffer size of 2 MB seems to give the "best" results (if I may say so, given the very minimal difference).

Source: C:\software\x264_x64.2009-03-08\skygirls.avs
Params: --crf 18 --level 4.1 --ref 8 --mixed-refs --no-fast-pskip --bframes 4 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock -1:-1 --subme 7 --trellis 1 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --merange 18 --thread-input --no-dct-decimate --no-psnr --no-ssim

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 2196 frames, 23.58 fps, 2848.26 kb/s
encoded 2196 frames, 23.76 fps, 2848.26 kb/s
encoded 2196 frames, 23.46 fps, 2848.26 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 2196 frames, 24.65 fps, 2848.26 kb/s
encoded 2196 frames, 24.71 fps, 2848.26 kb/s
encoded 2196 frames, 24.86 fps, 2848.26 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 2196 frames, 24.82 fps, 2848.26 kb/s
encoded 2196 frames, 25.49 fps, 2848.26 kb/s
encoded 2196 frames, 24.69 fps, 2848.26 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 2196 frames, 25.49 fps, 2848.26 kb/s
encoded 2196 frames, 25.26 fps, 2848.26 kb/s
encoded 2196 frames, 25.60 fps, 2848.26 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 2196 frames, 24.66 fps, 2848.26 kb/s
encoded 2196 frames, 25.46 fps, 2848.26 kb/s
encoded 2196 frames, 25.50 fps, 2848.26 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 2196 frames, 25.63 fps, 2848.26 kb/s
encoded 2196 frames, 25.17 fps, 2848.26 kb/s
encoded 2196 frames, 25.58 fps, 2848.26 kb/s

[LoRd_MuldeR]

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

[Rodger]

Here is the new Result.

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

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 6820 frames, 101.04 fps, 1831.60 kb/s
encoded 6820 frames, 100.87 fps, 1831.60 kb/s
encoded 6820 frames, 100.73 fps, 1831.60 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 6820 frames, 102.31 fps, 1831.59 kb/s
encoded 6820 frames, 101.27 fps, 1831.59 kb/s
encoded 6820 frames, 101.46 fps, 1831.59 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 6820 frames, 104.79 fps, 1831.59 kb/s
encoded 6820 frames, 104.92 fps, 1831.59 kb/s
encoded 6820 frames, 104.79 fps, 1831.59 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 6820 frames, 104.49 fps, 1831.59 kb/s
encoded 6820 frames, 104.76 fps, 1831.59 kb/s
encoded 6820 frames, 104.12 fps, 1831.59 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 6820 frames, 104.14 fps, 1831.59 kb/s
encoded 6820 frames, 104.31 fps, 1831.59 kb/s
encoded 6820 frames, 103.21 fps, 1831.59 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 6820 frames, 102.05 fps, 1831.59 kb/s
encoded 6820 frames, 101.81 fps, 1831.59 kb/s
encoded 6820 frames, 101.84 fps, 1831.59 kb/s

[Amefurashi]

Some heavy testing on a 720p enc from Blu-Ray source:

Source: C:\LITTLE_MISS_SUNSHINE\little_miss_sunshine.avs
Params: --crf 18 --level 4.1 --keyint 240 --min-keyint 24 --ref 4 --mixed-refs
--bframes 5 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock -2:-1
--subme 9 --trellis 2 --psy-rd 1.0:0 --partitions all --8x8dct --vbv-bufsize 40000
--vbv-maxrate 40000 --me umh --merange 24 --thread-input --aq-strength 1.0
--no-dct-decimate --no-psnr --no-ssim

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 1.43 fps, 10160.85 kb/s
encoded 501 frames, 1.43 fps, 10160.85 kb/s
encoded 501 frames, 1.44 fps, 10160.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 1.74 fps, 10160.85 kb/s
encoded 501 frames, 1.74 fps, 10160.85 kb/s
encoded 501 frames, 1.70 fps, 10160.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 501 frames, 1.65 fps, 10160.85 kb/s
encoded 501 frames, 1.69 fps, 10160.85 kb/s
encoded 501 frames, 1.58 fps, 10160.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 501 frames, 1.66 fps, 10160.85 kb/s
encoded 501 frames, 1.64 fps, 10160.85 kb/s
encoded 501 frames, 1.62 fps, 10160.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 501 frames, 1.72 fps, 10160.85 kb/s
encoded 501 frames, 1.74 fps, 10160.85 kb/s
encoded 501 frames, 1.59 fps, 10160.85 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 501 frames, 1.65 fps, 10160.85 kb/s
encoded 501 frames, 1.68 fps, 10160.85 kb/s
encoded 501 frames, 1.61 fps, 10160.85 kb/s

[LoRd_MuldeR]

Updated x264 binaries to r1137 (Skystrife builds).

[wiak]

this gui is epic simple one little thing am missing is some defoult high profiles and a bitrate calculator and it will be the best GUI for me =)

[HaraldBluetooth]

My PC spec.:

Q8200@2,33GHz
4 GB ram
Windows 7 Ultimate 64-bit

AviSynth script:

DirectShowSource("V:\Temp\Temp2\_Apocalypto.2006.720p.BluRay.x264-ESiR\Apocalypto.2006.720p.BluRay.x264-ESiR.mkv", fps=23.976, audio=false)
SelectRangeEvery
HQDN3D(1.9)
VagueDenoiser(threshold=1.7, method=3, nsteps=6, chromaT=0)
FFT3DGPU(bt=-1, sharpen=0.7)

Commandline:

Params: --crf 24.0 --ref 4 --mixed-refs --bframes 3 --b-adapt 2 --b-pyramid --weightb --deblock -3:-3 --subme 7 --trellis 2 --partitions p8x8,b8x8,i4x4,i8x8

LoRd_MuldeR - I just wan't to give you big thanks for this marvelous GUI.

With your default settings I got a FPS at 7,60. With two encodes at the same time I got a total FPS at 9,94.

I did a normal encode with MeGui in my 32 bit Windows XP SP3 with a FPS 6,92.

So compared to this it's an increase at 9,83% with one encode and with two encodes at the same time an increase at 43,64%.

I don't think I could do two encodes at the same time in 32 bit XP with these filters and x264 settings.

[XadoX]

Intel Xeon E5420

Temp.avs:

DGDecode_mpeg2source("D:\Temp.d2v", info=3)
ColorMatrix(hints=true, threads=0)
crop( 10, 76, -6, -68)
Trim(13767, 16062)

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

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 2296 frames, 78.79 fps, 1127.03 kb/s
encoded 2296 frames, 79.27 fps, 1127.03 kb/s
encoded 2296 frames, 79.60 fps, 1127.03 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 2296 frames, 78.20 fps, 1126.99 kb/s
encoded 2296 frames, 77.46 fps, 1126.99 kb/s
encoded 2296 frames, 78.58 fps, 1126.99 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 2296 frames, 81.86 fps, 1126.99 kb/s
encoded 2296 frames, 82.09 fps, 1126.99 kb/s
encoded 2296 frames, 81.63 fps, 1126.99 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 2296 frames, 80.91 fps, 1126.99 kb/s
encoded 2296 frames, 84.73 fps, 1126.99 kb/s
encoded 2296 frames, 83.44 fps, 1126.99 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 2296 frames, 83.34 fps, 1126.99 kb/s
encoded 2296 frames, 81.77 fps, 1126.99 kb/s
encoded 2296 frames, 83.81 fps, 1126.99 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 2296 frames, 81.95 fps, 1126.99 kb/s
encoded 2296 frames, 81.63 fps, 1126.99 kb/s
encoded 2296 frames, 80.56 fps, 1126.99 kb/s

[wiak]

can someone with some better skills than me list the "encoding options" that is the closest to the MeGUI's DXVA-HD-HQ Profile and the DXVA-SD-HQ Profile? for this GUI please

btw you can also find latest x64 builds by techouse @ http://nwgat.net/x264/

[saint-francis]

@Lord
Any chance of batch encoding capabilities being incorporated into this fantastic tool?

[LoRd_MuldeR]

Originally Posted by wiak

can someone with some better skills than me list the "encoding options" that is the closest to the MeGUI's DXVA-HD-HQ Profile and the DXVA-SD-HQ Profile? for this GUI please

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?

Originally Posted by saint-francis

Any chance of batch encoding capabilities being incorporated into this fantastic tool?

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

[saint-francis]

Originally Posted by LoRd_MuldeR

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

Sure thing! As soon as I retire I'll go back to school and learn how.
I'll just figure out how to do it the old fashioned way.

Thanks for the useful tool. I think it's helping to bring 64 bit awareness to the community.

@Lord_Mulder
I was wondering whether you were planning on continuing support for this utility, or if this is only a proof-of-concept?
The reason I ask this is because to my knowledge, this tool is at this moment about the only option that has a high enough usability for moderately experienced users to allow x64 encodes.
The options we have are, as I understand it:
your pipebuf tool, avisynth64+MeGUI64 (not usable), avs2yuv
I would personally opt for the integration of piping (which one would you recommend; pipebuf or avs2yuv?) into MeGUI that would then also be able to run in x64 mode, but I guess your tool is as good as it gets till that moment arrives...

[LoRd_MuldeR]

Originally Posted by Buggle

@Lord_Mulder
I was wondering whether you were planning on continuing support for this utility, or if this is only a proof-of-concept?
The reason I ask this is because to my knowledge, this tool is at this moment about the only option that has a high enough usability for moderately experienced users to allow x64 encodes.
The options we have are, as I understand it:
your pipebuf tool, avisynth64+MeGUI64 (not usable), avs2yuv
I would personally opt for the integration of piping (which one would you recommend; pipebuf or avs2yuv?) into MeGUI that would then also be able to run in x64 mode, but I guess your tool is as good as it gets till that moment arrives...

You got it wrong. The "avs2yuv" tool reads an Avisynth script and writes the raw video data to STDOUT. This way the x264 process can read the data from STDIN. And this can happen from 32-Bit Avisynth/avs2yuv to 64-Bit x264, because they're running as two separate processes (just communicating through a pipe). Mixing 32-Bit and 64-Bit code within the same process is not possible! That's why we have to use the pipe method. The sole purpose of my "pipebuf" tool is to establish the pipe between avs2yuv and x264. The same could be done with cmd.exe, but cmd.exe doesn't allow to specify the pipe buffer size.

BTW: Yes, I will continue to give support for that tool. But I'm definitely not going to implement any new features. I don't want to maintain yet another x264 GUI...

[LoRd_MuldeR]

Updated x264 binaries to r1165 (JEEB builds).

[komisar]

LoRd_MuldeR, can you update benchmark to support lattest version of x264? (--progress option trouble)