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

LoRd_MuldeR · 20th July 2009, 00:56

Quote:

Originally Posted by St Devious

don't know what that is , looks like a c program.

What does "Default is medium" mean ?

It means that using "--preset medium" is like not using the "--preset" switch at all, because the "medium" preset is equal to the x264 defaults (and consequently will do nothing).

And if you take a look at the x264 commandline, you will notice that my x264 launcher tool won't even involve the "--preset" switch, if "Medium" is selected in the "Preset" combo box

(BTW: In a C or C++ program /* and */ surround comments, so the code I quoted really doesn't do anything)

St Devious · 20th July 2009, 01:29

Quote:

Originally Posted by LoRd_MuldeR

It means that using "--preset medium" is like not using the "--preset" switch at all, because the "medium" preset is equal to the x264 defaults (and consequently will do nothing).

And if you take a look at the x264 commandline, you will notice that my x264 launcher tool won't even involve the "--preset" switch, if "Medium" is selected in the "Preset" combo box

(BTW: In a C or C++ program /* and */ surround comments, so the code I quoted really doesn't do anything)

alrite that clears things up. thanks.

LoRd_MuldeR · 21st July 2009, 14:37

Updated x264 to r1184 (JEEB's builds). Download link updated.

LoRd_MuldeR · 21st July 2009, 19:04

Quote:

Originally Posted by LoRd_MuldeR

Updated x264 to r1184 (JEEB's builds). Download link updated.

Previous JEEB builds had some strange error which caused x264 to crash with "short" commandline parameters (e.g. "-h").

Not sure whether there were other problems as well. Anyway, JEEB has fixed his built environment and provided fresh r1184 builds.

Download link in first post updated. I highly recommend to updated again, if you downloaded the update earlier this day!

St Devious · 21st July 2009, 19:18

Quote:

Originally Posted by LoRd_MuldeR

Previous JEEB builds had some strange error which caused x264 to crash with "short" commandline parameters.

Not sure whether there were other problems as well. Anyway, JEEB has fixed his built environment and provided fresh r1184 builds.

Download link in first post updated. I highly recommend to updated again, if you downloaded the update earlier this day!

thanks

twist3d · 21st July 2009, 19:43

Core 2 Duo E7200 overclocked to 3.02GHz, 2GB DDR2, P43 Chipset, Windows 7 Ultimate RC1 X64

500 frame clip from "A Love Song for Bobby Long" PAL R2

avisynth:
DGDecode_mpeg2source("C:\work\bobbylong.d2v", info=3)
ColorMatrix(hints=true, threads=0)
crop( 2, 0, 0, 0)
LanczosResize(720,576)
trim(15500,16000)

Code:

Source: C:\work\bobbylong.avs
Preset: Fast
Tuning: None
Profile: High
Params: 

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 51.95 fps, 936.46 kb/s
encoded 501 frames, 51.88 fps, 936.46 kb/s
encoded 501 frames, 51.93 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 52.54 fps, 936.46 kb/s
encoded 501 frames, 51.89 fps, 936.46 kb/s
encoded 501 frames, 52.64 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 501 frames, 52.80 fps, 936.46 kb/s
encoded 501 frames, 53.04 fps, 936.46 kb/s
encoded 501 frames, 52.98 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 501 frames, 52.85 fps, 936.46 kb/s
encoded 501 frames, 51.61 fps, 936.46 kb/s
encoded 501 frames, 52.94 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 501 frames, 51.70 fps, 936.46 kb/s
encoded 501 frames, 46.54 fps, 936.46 kb/s <- window auto-lost focus here
encoded 501 frames, 51.18 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 501 frames, 47.61 fps, 936.46 kb/s <- and here
encoded 501 frames, 51.55 fps, 936.46 kb/s
encoded 501 frames, 51.09 fps, 936.46 kb/s

also ran the same test with icc builds from http://imk.cx/pc/x264/, seems to lower fps on 32-bit but raise it with 64-bit... :

Code:

Source: C:\work\bobbylong.avs
Preset: Fast
Tuning: None
Profile: High
Params: 

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 48.28 fps, 936.46 kb/s
encoded 501 frames, 47.73 fps, 936.46 kb/s
encoded 501 frames, 48.42 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 52.88 fps, 936.46 kb/s
encoded 501 frames, 53.65 fps, 936.46 kb/s
encoded 501 frames, 53.75 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 501 frames, 54.02 fps, 936.46 kb/s
encoded 501 frames, 54.34 fps, 936.46 kb/s
encoded 501 frames, 54.41 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 501 frames, 54.24 fps, 936.46 kb/s
encoded 501 frames, 54.31 fps, 936.46 kb/s
encoded 501 frames, 54.35 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 501 frames, 52.69 fps, 936.46 kb/s
encoded 501 frames, 53.74 fps, 936.46 kb/s
encoded 501 frames, 53.81 fps, 936.46 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 501 frames, 52.66 fps, 936.46 kb/s
encoded 501 frames, 52.64 fps, 936.46 kb/s
encoded 501 frames, 52.64 fps, 936.46 kb/s

LoRd_MuldeR · 27th July 2009, 01:10

Updated x264 to r1189 (JEEB's builds). Also allow the Quantizer for CRF mode to be a Float. Download link updated.

alwa · 27th July 2009, 12:17

Could you built in a benchmark case where the buffer size is frame oriented (e.g. buffer size = Framewidth x Frameheigth x 1.5 Bytes). It migth be interesting to see whether ther is a dependency.

Thanks anyway.

LoRd_MuldeR · 27th July 2009, 13:25

Quote:

Originally Posted by alwa

Could you built in a benchmark case where the buffer size is frame oriented (e.g. buffer size = Framewidth x Frameheigth x 1.5 Bytes). It migth be interesting to see whether ther is a dependency.

I tried this once, but it didn't improve the results at all. So I dropped that idea.

[EDIT]

Updated x264 to r1190 (JEEB's builds). Download link in first post updated.

LoRd_MuldeR · 28th July 2009, 22:01

Updated x264 to r1193 (JEEB's builds). Download link in first post updated.

twist3d · 29th July 2009, 14:32

some fast tests again, now with akira r2 remastered special edition, jeeb's 1193 and imk.cx icc 1193.

- quick conclusion would be that icc builds are faster on x64
- 1mb/2mb/4mb buffers are the fastest

Code:

DGDecode_mpeg2source("C:\work\akira.d2v", info=3)
ColorMatrix(hints=true, threads=0)
crop( 2, 0, 0, 0)
BilinearResize(720,576)
trim(29000,29500)

jeeb's 1193:

Code:

Source: C:\work\test.avs
Preset: Veryfast
Tuning: Animation
Profile: High
Params: 

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 80.81 fps, 1459.69 kb/s
encoded 501 frames, 80.82 fps, 1459.69 kb/s
encoded 501 frames, 79.33 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 74.55 fps, 1459.69 kb/s
encoded 501 frames, 73.29 fps, 1459.69 kb/s
encoded 501 frames, 75.20 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 501 frames, 79.32 fps, 1459.69 kb/s
encoded 501 frames, 78.93 fps, 1459.69 kb/s
encoded 501 frames, 78.72 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 501 frames, 78.89 fps, 1459.69 kb/s
encoded 501 frames, 78.58 fps, 1459.69 kb/s
encoded 501 frames, 78.59 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 501 frames, 76.33 fps, 1459.69 kb/s
encoded 501 frames, 78.84 fps, 1459.69 kb/s
encoded 501 frames, 78.10 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 501 frames, 76.09 fps, 1459.69 kb/s
encoded 501 frames, 77.47 fps, 1459.69 kb/s
encoded 501 frames, 76.61 fps, 1459.69 kb/s

imk.cx icc:

Code:

Source: C:\work\test.avs
Preset: Veryfast
Tuning: Animation
Profile: High
Params: 

[Type: 32-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 66.30 fps, 1459.69 kb/s
encoded 501 frames, 67.84 fps, 1459.69 kb/s
encoded 501 frames, 67.15 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 0 MByte]
encoded 501 frames, 79.41 fps, 1459.69 kb/s
encoded 501 frames, 79.35 fps, 1459.69 kb/s
encoded 501 frames, 79.78 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 1 MByte]
encoded 501 frames, 80.90 fps, 1459.69 kb/s
encoded 501 frames, 81.16 fps, 1459.69 kb/s
encoded 501 frames, 80.95 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 2 MByte]
encoded 501 frames, 79.56 fps, 1459.69 kb/s
encoded 501 frames, 81.33 fps, 1459.69 kb/s
encoded 501 frames, 80.59 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 4 MByte]
encoded 501 frames, 80.51 fps, 1459.69 kb/s
encoded 501 frames, 80.42 fps, 1459.69 kb/s
encoded 501 frames, 80.68 fps, 1459.69 kb/s

[Type: 64-Bit, Pipe Buffer Size: 8 MByte]
encoded 501 frames, 78.20 fps, 1459.69 kb/s
encoded 501 frames, 78.91 fps, 1459.69 kb/s
encoded 501 frames, 77.73 fps, 1459.69 kb/s

LoRd_MuldeR · 29th July 2009, 14:37

Updated x264 to r1195 (Techouse builds). I recommend updating, QPRD was borked in previous builds. Download link in first post updated.

juGGaKNot · 29th July 2009, 15:24

Quote:

Originally Posted by LoRd_MuldeR

borked

What does that mean, you use it all the time ?

LoRd_MuldeR · 29th July 2009, 15:35

Quote:

Originally Posted by juGGaKNot

What does that mean, you use it all the time ?

It means that if (and only if) you used QPRD (aka SubME=10), then your output wasn't as the developers had intended, because there was a bug in QPRD.

But by chance the GCC builds still gave "reasonable" output, while ICC builds would simply have crashed. The problem is fixed now

http://forum.doom9.org/showthread.ph...15#post1309515

juGGaKNot · 6th August 2009, 18:57

No, i mean what does the word mean, i know about the bug

LoRd_MuldeR · 6th August 2009, 20:04

Quote:

Originally Posted by juGGaKNot

No, i mean what does the word mean, i know about the bug

http://www.urbandictionary.com/define.php?term=borked

LoRd_MuldeR · 9th August 2009, 00:13

Updated x264 to r1203 (x264.nl builds). Also added support for the new presets. Download link in first post updated.

LoRd_MuldeR · 9th August 2009, 21:56

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

GZZ · 14th August 2009, 10:19

avs2yuv dosnt work with avs script that uses DGDecodeNV.dll (Nvidia version og DGIndex), it just hang without continue.

LoRd_MuldeR · 14th August 2009, 11:26

Quote:

Originally Posted by GZZ

avs2yuv dosnt work with avs script that uses DGDecodeNV.dll (Nvidia version og DGIndex), it just hang without continue.

This is the wrong place to report. I don't even have a license to test DGDecodeNV

21st July 2009, 14:37	#83 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,251	Updated x264 to r1184 (JEEB's builds). Download link updated. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

27th July 2009, 01:10	#87 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,251	Updated x264 to r1189 (JEEB's builds). Also allow the Quantizer for CRF mode to be a Float. Download link updated. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

28th July 2009, 22:01	#90 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,251	Updated x264 to r1193 (JEEB's builds). Download link in first post updated. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

29th July 2009, 14:37	#92 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,251	Updated x264 to r1195 (Techouse builds). I recommend updating, QPRD was borked in previous builds. Download link in first post updated. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

9th August 2009, 00:13	#97 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,251	Updated x264 to r1203 (x264.nl builds). Also added support for the new presets. Download link in first post updated. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

27th July 2009, 12:17	#88 \| Link
alwa Registered User Join Date: May 2006 Posts: 29	Could you built in a benchmark case where the buffer size is frame oriented (e.g. buffer size = Framewidth x Frameheigth x 1.5 Bytes). It migth be interesting to see whether ther is a dependency. Thanks anyway.

9th August 2009, 21:56	#98 \| Link
LoRd_MuldeR Software Developer Join Date: Jun 2005 Location: Last House on Slunk Street Posts: 13,251	Updated x264 to r1206 (Komisar's builds). Download link in first post updated. __________________ Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

14th August 2009, 10:19	#99 \| Link
GZZ Registered User Join Date: Jan 2002 Posts: 581	avs2yuv dosnt work with avs script that uses DGDecodeNV.dll (Nvidia version og DGIndex), it just hang without continue.

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