Current Patches, Where to get them, How they affect speed/output - Page 23

lexor · 1st July 2008, 16:29

Quote:

Originally Posted by MythCreator

@Wishbringer:
http://mailman.videolan.org/pipermai...ne/004656.html

I don't understand that message, it's talking like hrd was only ever used for interlaced encoding. But nal-hrd switch had to be used for 360/PS3 blu-ray/hddvd profiles even on progressive material.

So I don't see how that patch is a substitute for original.

Sharktooth · 1st July 2008, 16:45

it is NOT.

lexor · 1st July 2008, 17:19

Quote:

Originally Posted by Sharktooth

it is NOT.

What's not? Not needed or not substitute?

If the former, it's in every megui profile for hd formats.

If the later, original question was why hrd patch isn't in, and MythCreator replied with that link. That suggests that he thinks it's a substitute. Since he does builds, I assumed he knew what the patches were for.

Sharktooth · 1st July 2008, 17:20

it's not a substitute.
infact i dont use myth's builds for megui.

MythCreator · 2nd July 2008, 09:15

x264.893.modified.exe
source

General thread:
http://forum.doom9.org/showthread.php?t=130364

x264_psy_rdo.r889.diff
http://forum.doom9.org/showthread.php?t=138293
X264_progress.indication.diff
http://forum.doom9.org/showthread.php?t=135905
x264_qpfile_relax.diff
http://forum.doom9.org/showthread.ph...19#post1151919
x264_hrd_pulldown.04_interlace.diff
HRD and pulldown for HD compatibility, updated patch for interlacing
http://forum.doom9.org/showthread.ph...19#post1047919

Link to x264 patches collected: http://files.x264.nl/x264_patches/

GCC 3.4.5 build fprofiled

bob0r · 2nd July 2008, 18:30

x264.895.modified.01.exe
x264.895.modified.01.source.zip

x264_psy_rdo.r889.diff
http://forum.doom9.org/showthread.php?t=138293
http://forum.doom9.org/showthread.ph...82#post1151782
x264_hrd_pulldown.04_interlace.diff
HRD and pulldown for HD compatibility, updated patch for interlacing
http://forum.doom9.org/showthread.ph...19#post1047919
x264.progress.indication.01.diff
http://forum.doom9.org/showthread.php?t=135905
x264_qpfile_relax.diff
http://forum.doom9.org/showthread.ph...19#post1151919

Link to x264 patches collected: http://files.x264.nl/x264_patches/

Here is the output of the patching process:
http://files.x264.nl/x264.895.modified.01.patch.out.txt

Here is the output of the compiling process:
http://files.x264.nl/x264.895.modifi...ofiled.out.txt

gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-generate -c -o encoder/set.o encoder/set.c
encoder/set.c: In function `x264_sps_init':
encoder/set.c:215: warning: unused variable `cpbBrVclFactor'

gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-use -c -o encoder/encoder.o encoder/encoder.c
encoder/encoder.c: In function `x264_encoder_encode':
encoder/encoder.c:1278: warning: 'cpb_removal_delay' might be used uninitialized in this function

darkorange = x264_hrd_pulldown.04_interlace.diff

The warnings that are not in the GIT code are highlighted with a color, and should not be there.
(The GIT warnings are there because of a bug in Windows, they prevent the usage of extended zones, example: x264 --zones 1,100,bframes=0)
The GIT warnings:

gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-generate -c -o common/common.o common/common.c
common/common.c: In function `x264_param_parse':
common/common.c:252: warning: unused variable `saveptr'

gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-generate -c -o encoder/ratecontrol.o encoder/ratecontrol.c
encoder/ratecontrol.c: In function `parse_zone':
encoder/ratecontrol.c:564: warning: unused variable `saveptr'
encoder/ratecontrol.c: In function `parse_zones':
encoder/ratecontrol.c:607: warning: unused variable `saveptr'

MythCreator · 3rd July 2008, 14:59

x264.897.modified.exe
source

General thread:
http://forum.doom9.org/showthread.php?t=130364

x264_psy_rdo.r889.diff
http://forum.doom9.org/showthread.php?t=138293
X264_progress.indication.diff
http://forum.doom9.org/showthread.php?t=135905
x264_qpfile_relax.diff
http://forum.doom9.org/showthread.ph...19#post1151919
x264_hrd_pulldown.04_interlace.diff
HRD and pulldown for HD compatibility, updated patch for interlacing
http://forum.doom9.org/showthread.ph...19#post1047919

Link to x264 patches collected: http://files.x264.nl/x264_patches/

GCC 3.4.5 build fprofiled

kemuri-_9 · 4th July 2008, 22:39

x264 r899 builds with mods:

x264_psy_rdo.r889.diff
http://forum.doom9.org/showthread.php?t=138293
x264_qpfile_relax.diff
http://forum.doom9.org/showthread.ph...19#post1151919
x264_hrd_pulldown.04_interlace.diff
http://forum.doom9.org/showthread.ph...19#post1047919
X264_progress.indication.diff
http://forum.doom9.org/showthread.php?t=135905

builds using -march flags (if specified)
k8 (AMD) flavor
http://kemuri9.net/dev/x264/x264_k8.exe
prescott (Intel) flavor
http://kemuri9.net/dev/x264/x264_prescott.exe
unspecified (generic) flavor
http://kemuri9.net/dev/x264/x264.exe

GCC 4.2.1-sjlj build fprofiled
can see how much gcc -march affects the speeds and which one works best for you.

see http://gcc.gnu.org/onlinedocs/gcc-4....4-Options.html for information on -march specs

chainring · 5th July 2008, 07:27

Quote:

Originally Posted by kemuri-_9

x264 r899 builds with mods:

x264_psy_rdo.r889.diff
http://forum.doom9.org/showthread.php?t=138293
x264_qpfile_relax.diff
http://forum.doom9.org/showthread.ph...19#post1151919
x264_hrd_pulldown.04_interlace.diff
http://forum.doom9.org/showthread.ph...19#post1047919
X264_progress.indication.diff
http://forum.doom9.org/showthread.php?t=135905

builds using -march flags (if specified)
k8 (AMD) flavor
http://kemuri9.net/dev/x264-arch/x264_k8.exe
nocona (Intel) flavor
http://kemuri9.net/dev/x264-arch/x264_nocona.exe
unspecified (generic) flavor
http://kemuri9.net/dev/x264.exe

GCC 4.2.1-sjlj build fprofiled
can see how much gcc -march affects the speeds and which one works best for you.

see http://gcc.gnu.org/onlinedocs/gcc-4....4-Options.html for information on -march specs

Any possibility you could do one with '-march=prescott'? I have a lowly core duo, but it bombs on the nocona build, so I'm guessing it doesn't support the 64 bit extensions.

akupenguin · 5th July 2008, 08:52

Quote:

Originally Posted by kemuri-_9

nocona (Intel) flavor

Nocona fails as a generic Intel flavor. In fact, both core2 and pentium4 run march=k8 faster than march=nocona.
Note that my results are specific to x264; apps with floating-point will differ.

Underground78 · 5th July 2008, 11:01

Quote:

Originally Posted by kemuri-_9

builds using -march flags (if specified)
k8 (AMD) flavor
http://kemuri9.net/dev/x264-arch/x264_k8.exe
unspecified (generic) flavor
http://kemuri9.net/dev/x264.exe

Both builds crash for me ...

burfadel · 5th July 2008, 11:38

Both builds work fine for me, core 2 duo e6600 (soon to be q9400)

wouldn't by any chance be running an overclock? If the overclock is too high certain things can start to go awry... someone I know had one of those 'big' overclocks, it wasn't until he knocked back his q6600 to around 3.2ghz did all his random crashes stop. Even if it was after 2 days with something not responding as well as it should! at 3.2ghz he hasn't had any problems with any programmes (this was about 4 weeks ago, leaves the computer on all the time). Its not worth going those few extra hundred mhz at the expense of rock stability. Those that go to 4ghz with the e8400, they can run tests on it for 2 days and not have a problem, but then have a random crash they blame on windows instead...

Underground78 · 5th July 2008, 11:59

I have an Athlon X2 6000+ @ 3 Ghz so without any overclocking ...

burfadel · 5th July 2008, 12:04

Memory timings?

Underground78 · 5th July 2008, 12:09

Default ones but builds from x264.nl work fine so I'm not sure it can be an hardware problem ...

cyberbeing · 5th July 2008, 12:56

Have you tried re-downloading it? Maybe your first download was incomplete or corrupt.

Dark Shikari · 5th July 2008, 12:59

Quote:

Originally Posted by Underground78

Both builds crash for me ...

I wouldn't be surprised; a build I made with -march=core2 crashed for me the other day because GCC was incorrectly autovectorizing on an unaligned array.

Sharktooth · 5th July 2008, 15:28

optimizing x264 via -march flag for more than i686 (or Pentium2) is USELESS.
it has been proven at least 5 (or even more) times... USELESS.
repeat with me... USELESS.
repeat again until you get it right...
USELESS.

lexor · 5th July 2008, 16:44

Quote:

Originally Posted by Sharktooth

optimizing x264 via -march flag for more than i686 (or Pentium2) is USELESS.
it has been proven at least 5 (or even more) times... USELESS.
repeat with me... USELESS.
repeat again until you get it right...
USELESS.

I think you should put an addendum to that statement. Most people who do builds won't just compile x264 itself, but also a bunch of other libraries (for mp4 and mkv support at least), and those libraries could benefit from compiler optimizations, last I saw their code they weren't nearly as handwritten-asm heavy as x264 is.

LoRd_MuldeR · 5th July 2008, 17:21

Quote:

Originally Posted by lexor

I think you should put an addendum to that statement. Most people who do builds won't just compile x264 itself, but also a bunch of other libraries (for mp4 and mkv support at least), and those libraries could benefit from compiler optimizations, last I saw their code they weren't nearly as handwritten-asm heavy as x264 is.

Nevertheless I highly doubt that the muxer libs will ever become the bottleneck, even when using very "fast" x264 settings...

1st July 2008, 16:45	#442 \| Link
Sharktooth Mr. Sandman Join Date: Sep 2003 Location: Haddonfield, IL Posts: 11,768	it is NOT. __________________ MPEG-4 ASP Custom Matrices: EQM V1(old), EQM AutoGK Sharpmatrix (aka EQM V2), EQM V3HR (updated 01/10/2004), EQM V3LR, EQM V3ULR (updated 04/02/2005), EQM V3UHR (updated 17/12/2004) and EQM V3EHR (updated 05/10/2004) Info about my ASP matrices. MPEG-4 AVC Custom Matrices: EQM AVC-HR Info about my AVC matrices My x264 builds. Mooo!!!

1st July 2008, 17:20	#444 \| Link
Sharktooth Mr. Sandman Join Date: Sep 2003 Location: Haddonfield, IL Posts: 11,768	it's not a substitute. infact i dont use myth's builds for megui. __________________ MPEG-4 ASP Custom Matrices: EQM V1(old), EQM AutoGK Sharpmatrix (aka EQM V2), EQM V3HR (updated 01/10/2004), EQM V3LR, EQM V3ULR (updated 04/02/2005), EQM V3UHR (updated 17/12/2004) and EQM V3EHR (updated 05/10/2004) Info about my ASP matrices. MPEG-4 AVC Custom Matrices: EQM AVC-HR Info about my AVC matrices My x264 builds. Mooo!!!

4th July 2008, 22:39	#448 \| Link
kemuri-_9 Compiling Encoder Join Date: Jan 2007 Posts: 1,348	x264 r899 builds with mods: x264_psy_rdo.r889.diff http://forum.doom9.org/showthread.php?t=138293 x264_qpfile_relax.diff http://forum.doom9.org/showthread.ph...19#post1151919 x264_hrd_pulldown.04_interlace.diff http://forum.doom9.org/showthread.ph...19#post1047919 X264_progress.indication.diff http://forum.doom9.org/showthread.php?t=135905 builds using -march flags (if specified) k8 (AMD) flavor http://kemuri9.net/dev/x264/x264_k8.exe prescott (Intel) flavor http://kemuri9.net/dev/x264/x264_prescott.exe unspecified (generic) flavor http://kemuri9.net/dev/x264/x264.exe GCC 4.2.1-sjlj build fprofiled can see how much gcc -march affects the speeds and which one works best for you. see http://gcc.gnu.org/onlinedocs/gcc-4....4-Options.html for information on -march specs Last edited by kemuri-_9; 6th July 2008 at 16:11. Reason: nocona -> prescott; url changes

5th July 2008, 15:28	#458 \| Link
Sharktooth Mr. Sandman Join Date: Sep 2003 Location: Haddonfield, IL Posts: 11,768	optimizing x264 via -march flag for more than i686 (or Pentium2) is USELESS. it has been proven at least 5 (or even more) times... USELESS. repeat with me... USELESS. repeat again until you get it right... USELESS. __________________ MPEG-4 ASP Custom Matrices: EQM V1(old), EQM AutoGK Sharpmatrix (aka EQM V2), EQM V3HR (updated 01/10/2004), EQM V3LR, EQM V3ULR (updated 04/02/2005), EQM V3UHR (updated 17/12/2004) and EQM V3EHR (updated 05/10/2004) Info about my ASP matrices. MPEG-4 AVC Custom Matrices: EQM AVC-HR Info about my AVC matrices My x264 builds. Mooo!!!

2nd July 2008, 09:15	#445 \| Link
MythCreator Registered User Join Date: Dec 2007 Location: Beijing,China Posts: 92	x264.893.modified.exe source General thread: http://forum.doom9.org/showthread.php?t=130364 x264_psy_rdo.r889.diff http://forum.doom9.org/showthread.php?t=138293 X264_progress.indication.diff http://forum.doom9.org/showthread.php?t=135905 x264_qpfile_relax.diff http://forum.doom9.org/showthread.ph...19#post1151919 x264_hrd_pulldown.04_interlace.diff HRD and pulldown for HD compatibility, updated patch for interlacing http://forum.doom9.org/showthread.ph...19#post1047919 Link to x264 patches collected: http://files.x264.nl/x264_patches/ GCC 3.4.5 build fprofiled

2nd July 2008, 18:30	#446 \| Link
bob0r Pain and suffering Join Date: Jul 2002 Posts: 1,337	x264.895.modified.01.exe x264.895.modified.01.source.zip x264_psy_rdo.r889.diff http://forum.doom9.org/showthread.php?t=138293 http://forum.doom9.org/showthread.ph...82#post1151782 x264_hrd_pulldown.04_interlace.diff HRD and pulldown for HD compatibility, updated patch for interlacing http://forum.doom9.org/showthread.ph...19#post1047919 x264.progress.indication.01.diff http://forum.doom9.org/showthread.php?t=135905 x264_qpfile_relax.diff http://forum.doom9.org/showthread.ph...19#post1151919 Link to x264 patches collected: http://files.x264.nl/x264_patches/ Here is the output of the patching process: http://files.x264.nl/x264.895.modified.01.patch.out.txt Here is the output of the compiling process: http://files.x264.nl/x264.895.modifi...ofiled.out.txt gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-generate -c -o encoder/set.o encoder/set.c encoder/set.c: In function `x264_sps_init': encoder/set.c:215: warning: unused variable `cpbBrVclFactor' gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-use -c -o encoder/encoder.o encoder/encoder.c encoder/encoder.c: In function `x264_encoder_encode': encoder/encoder.c:1278: warning: 'cpb_removal_delay' might be used uninitialized in this function darkorange = x264_hrd_pulldown.04_interlace.diff The warnings that are not in the GIT code are highlighted with a color, and should not be there. (The GIT warnings are there because of a bug in Windows, they prevent the usage of extended zones, example: x264 --zones 1,100,bframes=0) The GIT warnings: gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-generate -c -o common/common.o common/common.c common/common.c: In function `x264_param_parse': common/common.c:252: warning: unused variable `saveptr' gcc -O4 -ffast-math -Wall -I. -DHAVE_MMX -DARCH_X86 -DSYS_MINGW -DPTW32_STATIC_LIB -DHAVE_PTHREAD -s -fomit-frame-pointer -fprofile-generate -c -o encoder/ratecontrol.o encoder/ratecontrol.c encoder/ratecontrol.c: In function `parse_zone': encoder/ratecontrol.c:564: warning: unused variable `saveptr' encoder/ratecontrol.c: In function `parse_zones': encoder/ratecontrol.c:607: warning: unused variable `saveptr'

3rd July 2008, 14:59	#447 \| Link
MythCreator Registered User Join Date: Dec 2007 Location: Beijing,China Posts: 92	x264.897.modified.exe source General thread: http://forum.doom9.org/showthread.php?t=130364 x264_psy_rdo.r889.diff http://forum.doom9.org/showthread.php?t=138293 X264_progress.indication.diff http://forum.doom9.org/showthread.php?t=135905 x264_qpfile_relax.diff http://forum.doom9.org/showthread.ph...19#post1151919 x264_hrd_pulldown.04_interlace.diff HRD and pulldown for HD compatibility, updated patch for interlacing http://forum.doom9.org/showthread.ph...19#post1047919 Link to x264 patches collected: http://files.x264.nl/x264_patches/ GCC 3.4.5 build fprofiled

5th July 2008, 11:38	#452 \| Link
burfadel Registered User Join Date: Aug 2006 Posts: 2,229	Both builds work fine for me, core 2 duo e6600 (soon to be q9400) wouldn't by any chance be running an overclock? If the overclock is too high certain things can start to go awry... someone I know had one of those 'big' overclocks, it wasn't until he knocked back his q6600 to around 3.2ghz did all his random crashes stop. Even if it was after 2 days with something not responding as well as it should! at 3.2ghz he hasn't had any problems with any programmes (this was about 4 weeks ago, leaves the computer on all the time). Its not worth going those few extra hundred mhz at the expense of rock stability. Those that go to 4ghz with the e8400, they can run tests on it for 2 days and not have a problem, but then have a random crash they blame on windows instead...

5th July 2008, 11:59	#453 \| Link
Underground78 Registered User Join Date: Oct 2004 Location: France Posts: 567	I have an Athlon X2 6000+ @ 3 Ghz so without any overclocking ...

5th July 2008, 12:04	#454 \| Link
burfadel Registered User Join Date: Aug 2006 Posts: 2,229	Memory timings?

5th July 2008, 12:09	#455 \| Link
Underground78 Registered User Join Date: Oct 2004 Location: France Posts: 567	Default ones but builds from x264.nl work fine so I'm not sure it can be an hardware problem ...

5th July 2008, 12:56	#456 \| Link
cyberbeing Broadband Junkie Join Date: Oct 2005 Posts: 1,859	Have you tried re-downloading it? Maybe your first download was incomplete or corrupt.