Simple x264/x265 Launcher v2.94 (2019-10-05)

LoRd_MuldeR · 9th January 2009, 17:32

Simple x264/x265 Launcher

Quote:

This application is a lightweight GUI front-end for the x264 H.264/AVC
as well as the x265 H.265/HEVC encoder, based on the Qt toolkit.

Some key features of the Simple x264/x265 Launcher software include:

* Support for creating H.264/AVC (x264) and H.265/HEVC (x265) files
* Fully self-contained, *no* additional Codecs or Plugin's are required
* 64-Bit as well as 32-Bit encoder binaries are fully supported
* Optionally the "high bit-depth" encoder variants can be selected
* Batch encoding (job control) support is implemented
* If desired, multiple encoding jobs can be executed concurrently
* Adding new jobs via command-line interface is supported
* Input from the Avisynth *and* VapurSynth frame servers is supported
* 32-Bit Avisynth/VapourSynth can be mixed with 64-Bit x264/x265
* Straightforward encoder setup thanks to the Preset and Tuning system
* Custom encoder parameters can be added, if desired
* Easily manage your encoder configurations with user-defined templates
* Consistent "look & feel" on all systems thanks to the Qt toolkit

System Requirements:

* Windows Vista with Service Pack 2 or any later Windows system
* 64-Bit Windows is highly recommended (32-Bit Windows works as well)
* The CPU must support at least the MMX and SSE instruction sets
* Avisynth input only available with Avisynth 2.5+ installed
* VapourSynth input only available with VapourSynth R19+ installed
* YV16/YV24 color spaces require Avisynth 2.6 (see section 10)

Simple x264 Launcher is 100% standalone, i.e. it does *not* require
Mircrosoft.NET, Java Runtime Environment or other dependencies.

The required Qt DLLs and encoder binaries are included in the setup.

Download the latest version here:

See also:

http://www.portablefreeware.com/?id=2240

Quote:

Note: Occasionally your Antivirus program may mistakenly detect "malware" (virus, trojan, worm, etc.) in some of the files here.
This is called a "false-positive" and the files are actually innocent (clean). It's a failure in your specific Antivirus software.
In case you encounter such problems, go to http://www.virustotal.com/ and check the file again with multiple Antivirus engines!
And take care with results like "suspicious", "generic" or "packed". Those are *not* real hits, they are just wild speculation...

LoRd_MuldeR · 9th January 2009, 18:40

352x288 with "slow" settings on WindowsXP x64-Edition:

Code:

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

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 2262 frames, 49.21 fps, 463.48 kb/s
encoded 2262 frames, 49.48 fps, 463.48 kb/s
encoded 2262 frames, 49.43 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 2262 frames, 56.84 fps, 463.48 kb/s
encoded 2262 frames, 56.31 fps, 463.48 kb/s
encoded 2262 frames, 56.97 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 2262 frames, 55.11 fps, 463.48 kb/s
encoded 2262 frames, 56.88 fps, 463.48 kb/s
encoded 2262 frames, 55.23 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 2262 frames, 55.89 fps, 463.48 kb/s
encoded 2262 frames, 47.14 fps, 463.48 kb/s
encoded 2262 frames, 55.85 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 2262 frames, 56.91 fps, 463.48 kb/s
encoded 2262 frames, 56.15 fps, 463.48 kb/s
encoded 2262 frames, 56.93 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 2262 frames, 56.53 fps, 463.48 kb/s
encoded 2262 frames, 56.50 fps, 463.48 kb/s
encoded 2262 frames, 56.05 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 2262 frames, 55.59 fps, 463.48 kb/s
encoded 2262 frames, 56.22 fps, 463.48 kb/s
encoded 2262 frames, 55.62 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 2262 frames, 54.38 fps, 463.48 kb/s
encoded 2262 frames, 51.74 fps, 463.48 kb/s
encoded 2262 frames, 54.73 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 2262 frames, 51.80 fps, 463.48 kb/s
encoded 2262 frames, 51.59 fps, 463.48 kb/s
encoded 2262 frames, 51.37 fps, 463.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 2262 frames, 45.06 fps, 463.48 kb/s
encoded 2262 frames, 45.00 fps, 463.48 kb/s
encoded 2262 frames, 45.18 fps, 463.48 kb/s

352x288 with "fast" settings on WindowsXP x64-Edition:

Code:

Source: C:\TEMP\x264\sample.avs
Params: --crf 22 --subme 2 --me hex --analyse none

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 2262 frames, 373.14 fps, 542.81 kb/s
encoded 2262 frames, 386.07 fps, 542.81 kb/s
encoded 2262 frames, 392.37 fps, 542.81 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 2262 frames, 362.85 fps, 542.82 kb/s
encoded 2262 frames, 357.46 fps, 542.82 kb/s
encoded 2262 frames, 358.31 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 2262 frames, 403.21 fps, 542.82 kb/s
encoded 2262 frames, 396.63 fps, 542.82 kb/s
encoded 2262 frames, 374.07 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 2262 frames, 378.96 fps, 542.82 kb/s
encoded 2262 frames, 386.01 fps, 542.82 kb/s
encoded 2262 frames, 391.21 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 2262 frames, 370.27 fps, 542.82 kb/s
encoded 2262 frames, 389.19 fps, 542.82 kb/s
encoded 2262 frames, 370.21 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 2262 frames, 323.84 fps, 542.82 kb/s
encoded 2262 frames, 328.25 fps, 542.82 kb/s
encoded 2262 frames, 331.28 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 2262 frames, 300.32 fps, 542.82 kb/s
encoded 2262 frames, 355.66 fps, 542.82 kb/s
encoded 2262 frames, 378.01 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 2262 frames, 329.02 fps, 542.82 kb/s
encoded 2262 frames, 368.34 fps, 542.82 kb/s
encoded 2262 frames, 334.37 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 2262 frames, 393.39 fps, 542.82 kb/s
encoded 2262 frames, 316.81 fps, 542.82 kb/s
encoded 2262 frames, 330.56 fps, 542.82 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 2262 frames, 394.49 fps, 542.82 kb/s
encoded 2262 frames, 328.30 fps, 542.82 kb/s
encoded 2262 frames, 312.00 fps, 542.82 kb/s

Seems bigger pipe buffer doesn't help much here. Default value (0 MByte) aka "let Windows choose" already gives good results

Maybe 1 MB or 2 MB may be a good choice ???

Fishman0919 · 9th January 2009, 19:15

loadplugin("DGAVCDecode.dll")
AVCSource("file.dga")
Spline64Resize(1280,720)
trim(0, 3500)
ConvertToYV12()

First 3501 frames from Journey to the Center of the Earth (2008)
BluRay 1080p

Vista 64

Code:

Source: C:\Temp\test.avs
Params: --crf 22

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 3501 frames, 30.45 fps, 2896.24 kb/s
encoded 3501 frames, 31.07 fps, 2896.24 kb/s
encoded 3501 frames, 31.15 fps, 2896.24 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 3501 frames, 31.61 fps, 2896.23 kb/s
encoded 3501 frames, 31.96 fps, 2896.23 kb/s
encoded 3501 frames, 31.98 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 3501 frames, 32.22 fps, 2896.23 kb/s
encoded 3501 frames, 32.27 fps, 2896.23 kb/s
encoded 3501 frames, 31.88 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 3501 frames, 32.26 fps, 2896.23 kb/s
encoded 3501 frames, 32.24 fps, 2896.23 kb/s
encoded 3501 frames, 32.27 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 3501 frames, 31.71 fps, 2896.23 kb/s
encoded 3501 frames, 31.83 fps, 2896.23 kb/s
encoded 3501 frames, 31.88 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 3501 frames, 32.03 fps, 2896.23 kb/s
encoded 3501 frames, 32.14 fps, 2896.23 kb/s
encoded 3501 frames, 32.05 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 3501 frames, 31.56 fps, 2896.23 kb/s
encoded 3501 frames, 31.56 fps, 2896.23 kb/s
encoded 3501 frames, 31.56 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 3501 frames, 30.77 fps, 2896.23 kb/s
encoded 3501 frames, 31.13 fps, 2896.23 kb/s
encoded 3501 frames, 31.13 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 3501 frames, 29.90 fps, 2896.23 kb/s
encoded 3501 frames, 29.98 fps, 2896.23 kb/s
encoded 3501 frames, 29.97 fps, 2896.23 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 3501 frames, 27.69 fps, 2896.23 kb/s
encoded 3501 frames, 27.80 fps, 2896.23 kb/s
encoded 3501 frames, 27.65 fps, 2896.23 kb/s

Code:

Source: C:\Temp\test.avs
Params: --crf 22 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --keyint 24 --min-keyint 2 --direct auto --b-adapt 2 --subme 7 --trellis 2 --partitions all --8x8dct --me umh --merange 24 --no-fast-pskip

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 3501 frames, 13.99 fps, 3174.75 kb/s
encoded 3501 frames, 14.05 fps, 3174.75 kb/s
encoded 3501 frames, 14.03 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 3501 frames, 15.15 fps, 3174.75 kb/s
encoded 3501 frames, 15.22 fps, 3174.75 kb/s
encoded 3501 frames, 15.21 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 3501 frames, 15.26 fps, 3174.75 kb/s
encoded 3501 frames, 15.27 fps, 3174.75 kb/s
encoded 3501 frames, 15.27 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 3501 frames, 15.29 fps, 3174.75 kb/s
encoded 3501 frames, 15.29 fps, 3174.75 kb/s
encoded 3501 frames, 15.25 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 3501 frames, 15.27 fps, 3174.75 kb/s
encoded 3501 frames, 15.26 fps, 3174.75 kb/s
encoded 3501 frames, 15.25 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 3501 frames, 15.25 fps, 3174.75 kb/s
encoded 3501 frames, 15.21 fps, 3174.75 kb/s
encoded 3501 frames, 15.24 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 3501 frames, 15.17 fps, 3174.75 kb/s
encoded 3501 frames, 15.20 fps, 3174.75 kb/s
encoded 3501 frames, 15.17 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 3501 frames, 15.07 fps, 3174.75 kb/s
encoded 3501 frames, 15.08 fps, 3174.75 kb/s
encoded 3501 frames, 15.09 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 3501 frames, 14.68 fps, 3174.75 kb/s
encoded 3501 frames, 14.64 fps, 3174.75 kb/s
encoded 3501 frames, 14.70 fps, 3174.75 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 3501 frames, 14.37 fps, 3174.75 kb/s
encoded 3501 frames, 14.33 fps, 3174.75 kb/s
encoded 3501 frames, 14.32 fps, 3174.75 kb/s

turbojet · 9th January 2009, 23:37

X2 3800+ at 2.5 ghz, Vista 64

CoreAVC feeding a 1920x1080 stream, just directshowsource in avs.

Code:

Params: --crf 22

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 1377 frames, 4.10 fps, 9437.87 kb/s
encoded 1377 frames, 3.78 fps, 9437.87 kb/s
encoded 1377 frames, 3.89 fps, 9437.87 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 1377 frames, 4.06 fps, 9437.88 kb/s
encoded 1377 frames, 4.08 fps, 9437.88 kb/s
encoded 1377 frames, 4.14 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 1377 frames, 4.12 fps, 9437.88 kb/s
encoded 1377 frames, 4.10 fps, 9437.88 kb/s
encoded 1377 frames, 4.22 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 1377 frames, 4.30 fps, 9437.88 kb/s
encoded 1377 frames, 4.06 fps, 9437.88 kb/s
encoded 1377 frames, 3.47 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 1377 frames, 3.48 fps, 9437.88 kb/s
encoded 1377 frames, 4.48 fps, 9437.88 kb/s
encoded 1377 frames, 4.40 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 1377 frames, 4.15 fps, 9437.88 kb/s
encoded 1377 frames, 4.17 fps, 9437.88 kb/s
encoded 1377 frames, 4.08 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 1377 frames, 4.11 fps, 9437.88 kb/s
encoded 1377 frames, 4.07 fps, 9437.88 kb/s
encoded 1377 frames, 4.34 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 1377 frames, 4.34 fps, 9437.88 kb/s
encoded 1377 frames, 4.23 fps, 9437.88 kb/s
encoded 1377 frames, 4.18 fps, 9437.88 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 1377 frames, 3.90 fps, 9437.88 kb/s
encoded 1377 frames, 3.93 fps, 9437.88 kb/s
encoded 1377 frames, 3.97 fps, 9437.88 kb/s

Thanks for your launcher app btw, I've been getting some good use out of it.

If your intention is to go beyond 32 vs 64 bit and do a good benchmark from different cpus, might I make a suggestion to make a more accurate test? That's include a small 1080p m2ts, dgavcdecode.dll, .dga and 2 avs for 720p and 1080p, and have a 'fast' encode setting and 'normal' encode setting both as a part of the benchmark.

LoRd_MuldeR · 10th January 2009, 02:11

Quote:

Originally Posted by turbojet

If your intention is to go beyond 32 vs 64 bit and do a good benchmark from different cpus, might I make a suggestion to make a more accurate test? That's include a small 1080p m2ts, dgavcdecode.dll, .dga and 2 avs for 720p and 1080p, and have a 'fast' encode setting and 'normal' encode setting both as a part of the benchmark.

My intention is mainly to find out whether the 64-Bit version (using piped input) is truly faster than the 32-Bit version (using native AVS input).

Also I try to find out whether any user-defined buffer size can give a benefit over the default buffer size (aka "let Windows decide").

RunningSkittle · 10th January 2009, 03:35

Code:

DGDecode_mpeg2source("D:\dvdrips\totoro\VTS_07_VOBID_009_CELLID_001_1.d2v")
tfm(order=1).tdecimate(mode=1)
crop( 8, 6, -6, -14)
LanczosResize(720,384)

Q6600@ 3.0ghz
Vista X64
4gb DDRII 800

Short clip from R1 Totoro:

Code:

Source: D:\dvdrips\totoro\VTS_07_VOBID_009_CELLID_001_1.avs
Params: --crf 18 --ref 5 --mixed-refs --bframes 3 --b-adapt 2 --b-pyramid --weightb --deblock -1:-1 --trellis 2 --partitions all  --8x8dct --me umh --aud

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 437 frames, 21.55 fps, 1792.72 kb/s
encoded 437 frames, 21.60 fps, 1792.72 kb/s
encoded 437 frames, 21.68 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 437 frames, 24.09 fps, 1792.72 kb/s
encoded 437 frames, 23.86 fps, 1792.72 kb/s
encoded 437 frames, 23.92 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 437 frames, 24.29 fps, 1792.72 kb/s
encoded 437 frames, 24.15 fps, 1792.72 kb/s
encoded 437 frames, 24.17 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 437 frames, 24.02 fps, 1792.72 kb/s
encoded 437 frames, 23.98 fps, 1792.72 kb/s
encoded 437 frames, 24.02 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 437 frames, 23.90 fps, 1792.72 kb/s
encoded 437 frames, 23.98 fps, 1792.72 kb/s
encoded 437 frames, 24.09 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 437 frames, 23.53 fps, 1792.72 kb/s
encoded 437 frames, 23.37 fps, 1792.72 kb/s
encoded 437 frames, 23.60 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 437 frames, 23.38 fps, 1792.72 kb/s
encoded 437 frames, 23.83 fps, 1792.72 kb/s
encoded 437 frames, 23.89 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 437 frames, 23.47 fps, 1792.72 kb/s
encoded 437 frames, 23.74 fps, 1792.72 kb/s
encoded 437 frames, 23.58 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 437 frames, 23.12 fps, 1792.72 kb/s
encoded 437 frames, 22.65 fps, 1792.72 kb/s
encoded 437 frames, 22.50 fps, 1792.72 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 437 frames, 22.57 fps, 1792.72 kb/s
encoded 437 frames, 23.23 fps, 1792.72 kb/s
encoded 437 frames, 23.04 fps, 1792.72 kb/s

RunningSkittle · 10th January 2009, 14:50

Code:

avcsource()
trim(0,999)

First 1000 frames from Dead space. 1080p.

Code:

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 1000 frames, 3.26 fps, 17443.48 kb/s
encoded 1000 frames, 3.26 fps, 17443.48 kb/s
encoded 1000 frames, 3.28 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 1000 frames, 3.58 fps, 17443.48 kb/s
encoded 1000 frames, 3.50 fps, 17443.48 kb/s
encoded 1000 frames, 3.47 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 1000 frames, 3.50 fps, 17443.48 kb/s
encoded 1000 frames, 3.49 fps, 17443.48 kb/s
encoded 1000 frames, 3.52 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 1000 frames, 3.51 fps, 17443.48 kb/s
encoded 1000 frames, 3.63 fps, 17443.48 kb/s
encoded 1000 frames, 3.63 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 1000 frames, 3.64 fps, 17443.48 kb/s
encoded 1000 frames, 3.63 fps, 17443.48 kb/s
encoded 1000 frames, 3.64 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 1000 frames, 3.64 fps, 17443.48 kb/s
encoded 1000 frames, 3.64 fps, 17443.48 kb/s
encoded 1000 frames, 3.64 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 1000 frames, 3.63 fps, 17443.48 kb/s
encoded 1000 frames, 3.62 fps, 17443.48 kb/s
encoded 1000 frames, 3.45 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 1000 frames, 3.63 fps, 17443.48 kb/s
encoded 1000 frames, 3.64 fps, 17443.48 kb/s
encoded 1000 frames, 3.58 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 1000 frames, 3.60 fps, 17443.48 kb/s
encoded 1000 frames, 3.60 fps, 17443.48 kb/s
encoded 1000 frames, 3.60 fps, 17443.48 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 1000 frames, 3.58 fps, 17443.48 kb/s
encoded 1000 frames, 3.58 fps, 17443.48 kb/s
encoded 1000 frames, 3.57 fps, 17443.48 kb/s

roozhou · 10th January 2009, 15:12

Quote:

Originally Posted by LoRd_MuldeR

My intention is mainly to find out whether the 64-Bit version (using piped input) is truly faster than the 32-Bit version (using native AVS input).

Also I try to find out whether any user-defined buffer size can give a benefit over the default buffer size (aka "let Windows decide").

Once I have 64-bit Windows installed, i will try to add directshow input support, which is already done in win32, to 64-bit x264.

Unfortunately i cannot run your test coz i don't have 64-bit Windows installed at present.

LoRd_MuldeR · 10th January 2009, 16:02

Quote:

Originally Posted by roozhou

Once I have 64-bit Windows installed, i will try to add directshow input support, which is already done in win32, to 64-bit x264.

That certainly would be an interesting option, but we'd still need to use 64-Bit DirectShow filters and 64-Bit Avisynth. So it may be good for certain purposes (use DirectShow input, have a suitable DirectShow 64-bit Decoder available and don't need Avisynth), but it doesn't solve the basic problem - the lack of 32-Bit Avisynth input. Therefore it's not hard to predict that the pipe method will be around for quite some time...

roozhou · 10th January 2009, 23:07

Quote:

Originally Posted by LoRd_MuldeR

That certainly would be an interesting option, but we'd still need to use 64-Bit DirectShow filters and 64-Bit Avisynth. So it may be good for certain purposes (use DirectShow input, have a suitable DirectShow 64-bit Decoder available and don't need Avisynth), but it doesn't solve the basic problem - the lack of 32-Bit Avisynth input. Therefore it's not hard to predict that the pipe method will be around for quite some time...

Most of avisynth plugins are open source. Try to make them compile for 64-bit. If it fails, just drop it.

P.S. ffdshow's built-in filters are awesome. Resizer in ffdshow runs 50%~100% faster than avisynth's.

LoRd_MuldeR · 10th January 2009, 23:09

Quote:

Originally Posted by roozhou

Most of avisynth plugins are open source. Try to make them compile for 64-bit. If it fails, just drop it.

Good luck with that

Atak_Snajpera · 10th January 2009, 23:10

it looks like 4mb buffer works well

LoRd_MuldeR · 10th January 2009, 23:13

Quote:

Originally Posted by Atak_Snajpera

it looks like 4mb buffer works well

Agreed. More than 4 MB seems to be no good. Also "slow" settings seem to profit from 64-Bit more than "fast" settings.

Atak_Snajpera · 10th January 2009, 23:17

Quote:

Also "slow" settings seem to profit from 64-Bit more than "fast" settings.

I'm not surprised

turbojet · 17th January 2009, 10:09

Do you plan on adding a queue system to the launcher?
If you did add a queue system I'd use it regularly, at the speeds I run at every little bit of speed helps.

I'm not aware of any gui with x64 264 support and a queue system. So I might not be the only one wanting something like this.

I like the simple ui, one thing I do wish I could do is delete saved command lines I don't want to keep. Would that be possible as well?

Also is there a way to define buffer in the command line?

vucloutr · 20th January 2009, 11:35

here with some really slow settings, OS: Server 2008 x64, CPU: Q6600@3GHz

Code:

Source: D:\x264launcher\720p.avs
Params: --keyint 240 --min-keyint 24 --bframes 4 --b-adapt 2 --b-pyramid --ref 9 --deblock -3,-2 --crf 19
--ipratio 1.4 --pbratio 1.0 --aq-strength 0.8 --direct auto --weightb --me esa --merange 24 --subme 9
--mixed-refs --8x8dct --no-fast-pskip --no-dct-decimate --deadzone-intra 9 --deadzone-inter 5
--no-psnr --no-ssim --thread-input

[Mode: 32-Bit, Pipe Buffer: 0 MByte]
encoded 334 frames, 2.50 fps, 10648.77 kb/s
encoded 334 frames, 2.50 fps, 10648.77 kb/s
encoded 334 frames, 2.49 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 0 MByte]
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 1 MByte]
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 2 MByte]
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.69 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 4 MByte]
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 8 MByte]
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 16 MByte]
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.69 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 32 MByte]
encoded 334 frames, 2.70 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s
encoded 334 frames, 2.66 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 64 MByte]
encoded 334 frames, 2.66 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.68 fps, 10648.77 kb/s

[Mode: 64-Bit, Pipe Buffer: 128 MByte]
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s
encoded 334 frames, 2.67 fps, 10648.77 kb/s

LoRd_MuldeR · 21st January 2009, 00:50

Quote:

Originally Posted by turbojet

Do you plan on adding a queue system to the launcher?

Not planned.

Quote:

Originally Posted by turbojet

I'm not aware of any gui with x64 264 support and a queue system. So I might not be the only one wanting something like this.

Think 64-Bit support will be added to RipBot264, if not done already.

Quote:

Originally Posted by turbojet

I like the simple ui, one thing I do wish I could do is delete saved command lines I don't want to keep. Would that be possible as well?

Edit the INI file

Quote:

Originally Posted by turbojet

Also is there a way to define buffer in the command line?

Yes. In the commandline for pipebuf.exe

Code:

PipeBuffer by LoRd_MuldeR <mulder2@gmx.de>, Version 1.03

Usage:
  pipebuf.exe <program_out> [<args>] : <program_in> [<args>] : [<buffer_size>]

Options:
  <program_out>  Executable to read stdout from
  <program_in>   Executable to write stdin to
  <args>         Optional command-line arguments
  <buffer_size>  Pipe buffer in MByte [0]

LoRd_MuldeR · 24th January 2009, 04:47

Updated x264 binaries to r1088 (built by Skystrife) and set default buffer size to 4 MB, as that seems to perform best

turbojet · 27th January 2009, 18:37

Pity you don't plan on adding a little queue. Do you mind if I have someone try to add one?

Good news about RipBot264 getting x64 support. It's a gui I use every once in awhile.

Where is the .ini file for the launcher?

Thanks for the pipebuf info.

LoRd_MuldeR · 27th January 2009, 18:42

Quote:

Originally Posted by turbojet

Pity you don't plan on adding a little queue. Do you mind if I have someone try to add one?

The sources are attached, available for anybody who thinks they can be helpful

So if anybody feels like implementing a queue, have your fun

10th January 2009, 23:10	#12 \| Link
Atak_Snajpera RipBot264 author Join Date: May 2006 Location: Poland Posts: 7,237	it looks like 4mb buffer works well __________________ Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper

17th January 2009, 10:09	#15 \| Link
turbojet Registered User Join Date: May 2008 Posts: 1,840	Do you plan on adding a queue system to the launcher? If you did add a queue system I'd use it regularly, at the speeds I run at every little bit of speed helps. I'm not aware of any gui with x64 264 support and a queue system. So I might not be the only one wanting something like this. I like the simple ui, one thing I do wish I could do is delete saved command lines I don't want to keep. Would that be possible as well? Also is there a way to define buffer in the command line? Last edited by turbojet; 17th January 2009 at 10:18.

24th January 2009, 04:47	#18 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,050	Updated x264 binaries to r1088 (built by Skystrife) and set default buffer size to 4 MB, as that seems to perform best __________________ There was of course no way of knowing whether you were being watched at any given moment. How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

27th January 2009, 18:37	#19 \| Link
turbojet Registered User Join Date: May 2008 Posts: 1,840	Pity you don't plan on adding a little queue. Do you mind if I have someone try to add one? Good news about RipBot264 getting x64 support. It's a gui I use every once in awhile. Where is the .ini file for the launcher? Thanks for the pipebuf info.