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

[komisar]

new 1206 builds with adapted patches (need testing)
also new VAQ (again :) may help with fades and mbtree) patch by BugMaster in kMod build. (activate by "--aq-mode 3")
http://komisar.gin.by/

[JEEB]

x264 r1206 64bit unpatched:
download (http://jeeb.fiveforty.jp/x264/revision1206/x264.exe) ; hash (http://jeeb.fiveforty.jp/x264/revision1206/x264.md5)

built on Aug 9 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, otherwise defaults

________________________________________________________________________________

x264 r1206 32bit
download (http://jeeb.fiveforty.jp/x264/1206/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1206/relnotes.txt)

built on Aug 10 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=i686


x264 r1206 64bit
download (http://jeeb.fiveforty.jp/x264/1206_x64/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1206_x64/relnotes.txt)

built on Aug 10 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, -march=core2


patched with:

x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pulldown.15_interlace.fix.1206.diff (http://komisar.gin.by/x.patch/x264_hrd_pulldown.15_interlace.fix.1206.diff)


Hurf, I did compile at least one build during ASM'09, but only now do I get at releasing :3 I wish there was an easy way of recording them demos in order to put up for people who have not-so-powerful machines like myself.

[imk]

x264-r1206M_2-imk-win.7z (http://imk.cx/pc/x264/x264-r1206M_2-imk-win.7z)
win_build_info.txt (http://imk.cx/pc/x264/win_build_info.txt)

x264-r1206M_2-imk-osx.7z (http://imk.cx/pc/x264/x264-r1206M_2-imk-osx.7z)

Re-built with:
x264_win_zone_parse_fix_06.diff
x264_hrd_pulldown.15_interlace.fix.1206.diff

[juGGaKNot]

not the file, you link to threads where the patches exist within posts.
which is effectively useless when a thread such as this one is over 100 pages.
but whatever, i had found the rev 05 win zone patch on page 78 of this thread, and that's all i cared about.

I mean posts by me here on the latest pages where there is a patched build

like #2135, i upload all the diffs on mediafire when i post a patched x264.

i said 2 posts up but it was unpatched, my mistake.

LE :

komisar aq3 : ( 4 pictures, aq1, aq2, aq3, xvid )

http://i286.photobucket.com/albums/ll105/juGGaKNot4cs/th_aq1.jpg (http://s286.photobucket.com/albums/ll105/juGGaKNot4cs/?action=view&current=aq1.jpg)http://i286.photobucket.com/albums/ll105/juGGaKNot4cs/th_aq2.jpg (http://s286.photobucket.com/albums/ll105/juGGaKNot4cs/?action=view&current=aq2.jpg)http://i286.photobucket.com/albums/ll105/juGGaKNot4cs/th_aq3.jpg (http://s286.photobucket.com/albums/ll105/juGGaKNot4cs/?action=view&current=aq3.jpg)http://i286.photobucket.com/albums/ll105/juGGaKNot4cs/th_xvid.jpg (http://s286.photobucket.com/albums/ll105/juGGaKNot4cs/?action=view&current=xvid.jpg)

[rack04]

x264 core:70 r1206 32-bit

Download (http://www.sendspace.com/file/477gj3)

Built by rack04 on August 10, 2009, 2:06:11 PM CST
GCC: 4.4.1 (x86.core2.Komisar)
$ ./configure
Platform: X86
System: MINGW
asm: yes
avis input: yes
mp4 output: yes
pthread: yes
debug: no
gprof: no
PIC: no
shared: no
visualize: no
$ --extra-cflags="-march=core2"
$ make fprofiled VIDS="bigbuckbunny.avs LosslessTouhou.avs riverbed.1920x1080.yuv"

Patched with:

x264_hrd_pulldown.15_interlace.fix.1206.diff
x264_win_zone_parse_fix_06.diff

[rack04]

x264 core:70 r1209M 32-bit

Download (http://www.mediafire.com/?sharekey=e6d304fba0af2c04c2b435915e8821d7e04e75f6e8ebb871)

Built by rack04 on August 13, 2009, 4:45:30 PM CST
GCC: 4.4.1 (x86.core2.Komisar)
$ ./configure
Platform: X86
System: MINGW
asm: yes
avis input: yes
mp4 output: yes
pthread: yes
debug: no
gprof: no
PIC: no
shared: no
visualize: no
$ --extra-cflags="-march=core2"
$ make fprofiled VIDS="bigbuckbunny.avs LosslessTouhou.avs riverbed.1920x1080.yuv"

Patched with:

x264_hrd_pulldown.15_interlace.fix.1206.diff
x264_win_zone_parse_fix_06.diff

[JEEB]

x264 r1210 64bit unpatched:
download (http://koti.mbnet.fi/jeeb/x264/revision1210/x264.exe) ; hash (http://koti.mbnet.fi/jeeb/x264/revision1210/x264.md5)

built on Aug 14 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, otherwise defaults

________________________________________________________________________________

x264 r1210 32bit
download (http://koti.mbnet.fi/jeeb/x264/1210/x264.exe) ; release notes (http://koti.mbnet.fi/jeeb/x264/1210/relnotes.txt)

built on Aug 14 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=i686


x264 r1210 64bit
download (http://koti.mbnet.fi/jeeb/x264/1210_x64/x264.exe) ; release notes (http://koti.mbnet.fi/jeeb/x264/1210_x64/relnotes.txt)

built on Aug 14 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=core2


patched with:

x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pulldown.15_interlace.fix.1206.diff (http://komisar.gin.by/x.patch/x264_hrd_pulldown.15_interlace.fix.1206.diff)


Hurf, and the Japanese box I'm using fell for the first time in two or so years :3 Using MBnet as hosting for this build at least temporarily until the box comes back up.

[imk]

r1210M built with ICC.

Windows:
x264-r1210M-imk-win.7z (http://imk.cx/pc/x264/x264-r1210M-imk-win.7z)
win_build_info.txt (http://imk.cx/pc/x264/win_build_info.txt)

Mac OS X:
x264-r1210M-imk-osx.7z (http://imk.cx/pc/x264/x264-r1210M-imk-osx.7z)
osx_build_info.txt (http://imk.cx/pc/x264/osx_build_info.txt)

[deank]

@Dark Shikari:

About my post in BD-Rebuilder thread:

I just tried these latest patched versions from posts above (32bit):

* JEEB's one works.
* imk's one - does not work (gives the same blocky output) (and shows Slow_mod4_stack).

Both tested with same options, same source (720x576p @ 25fps).

Dean

[Dark Shikari]

@Dark Shikari:

About my post in BD-Rebuilder thread:

I just tried these latest patched versions from posts above (win32):

* JEEB's one works.
* imk's one - does not work (gives the same blocky output).

Both tested with same options, same source (720x576i @ 25fps).

DeanThen it sounds like IMK's build has been miscompiled.

[imk]

Slow_mod4_stack only exists for the 32-bit build. Despite saying that, it still ends up to be slightly faster than GCC. It shouldn't affect any quality.

As for the blocky output, I'm not sure. Could you link me to the clip you're using and the args you use so I can run my own tests?

[Selur]

@Trahald: there's a user (http://forum.gleitz.info/showpost.php?p=393212&postcount=430) in the german doom9 forum which got a "Assertion failed: dpb_output_delay < pow( 2, sps->vui.nal_hrd_parameters.i_dpb_output_delay_length ), file encoder/set.c, line 652"-crash using the following command line:
x264 --profile high --crf 22 --level 4 --ref 5 --keyint 50 --min-keyint 25 --scenecut 40 --bframes 3 --b-bias 0 --direct auto --cplxblur 20 --qcomp 0.6 --qblur 0.5 --qpmin 1 --qpmax 51 --qpstep 4 --ipratio 1.4 --pbratio 1.3 --chroma-qp-offset 0 --partitions i4x4,i8x8,p8x8,b8x8 --me hex --merange 16 --subme 10 --no-mixed-refs --no-fast-pskip --aq-mode 1 --aq-strength 1 --deadzone-inter 11 --vbv-maxrate 24000 --vbv-bufsize 30000 --aud --nal-hrd --threads auto --sar 10:11 --filter 0,0 --fps 25 --output "C:\WINDOWS\TEMP\test1_222855078.264" - 720x480 and this (http://forum.doom9.org/showthread.php?p=1314614#post1314614) build.
thought this might help finding the problem.

Cu Selur

[deank]

As for the blocky output, I'm not sure. Could you link me to the clip you're using and the args you use so I can run my own tests?

Here. (http://rapidshare.com/files/267990592/dvddump.m2ts)

[Trahald]

@Selur
I couldnt duplicate the issue with that command line. If whoever it is can document the frame the error occurs on, then run an encode on a build with the assert line removed (so the encode will complete)and send me the output. then i can see the conditions which cause the error. I think the calcs are ok so id like to pin down the prob instead of arbitrarily making the value larger.

[imk]

Here. (http://rapidshare.com/files/267990592/dvddump.m2ts)

Alright, thanks. I'll run some tests on it to see if I can duplicate it or alleviate the problem.

[Selur]

@Trahald: I'll contact the user and ask him to test it like you suggested.
(now I just have to get my build environment running again to provide the user with a build he can use.;))
-> provided him with a new builds, the one without the assertion can through an he'll upload the created file later (will forward it than to you)

[imk]

Here. (http://rapidshare.com/files/267990592/dvddump.m2ts)

Also, which settings are you using with x264?


Edit:
I've been trying my builds and JEEB's builds in Windows, and I tried my ICC build and a GCC build of mine in OS X, and they all output identical, md5sum-matching, bitstreams.


Edit 2:
Alright, it seems to be that the 64-bit ICC build produces identical output to GCC. The 32-bit version is where things are slightly different. Since it has Slow_mod4_stack, I believe that certain C functions are used instead of ASM, which might explain why the output is different. I'm not sure if that would result in “blocky” output, or just slightly different output. I'll run more tests.


Edit 3:
I really can't reproduce this. I get basically the same output. Only the headers differ.

For MD5 sums... 32-bit GCC and 32-bit ICC are identical, but differ from the 64-bit builds. And 64-bit GCC and 64-bit ICC are identical.

There really shouldn't be any different output.

[moviefan]

@Dark Shikari (most probably): The --help documentation misses --aq-mode 3 to be mentioned and described. I just noticed that and thought it's worth mentioning, just to keep up consistency.

[Dark Shikari]

@Dark Shikari (most probably): The --help documentation misses --aq-mode 3 to be mentioned and described. I just noticed that and thought it's worth mentioning, just to keep up consistency.AQ mode 3 is not part of official x264; it's the job of patch maintainers to add their own help.

[moviefan]

Oh, I didn't notice JEEB's binary included an AQ patch... He only names the winzone and the hrd patch.

[juGGaKNot]

--aq 3 was added as a diff by komisar @ 1206 i think , to help fades.

http://komisar.gin.by/index.html

i can compile a 1210 if you want.

[moviefan]

Thanks for the offer, but it seems that JEEB has included the diff already without explicitly mentioning.

[alwa]

I don't think JEEB includes this patch. I think the values of aq-mode are just clipped to valid values. So if you set aq-mode 3, the value will be clipped to 2(the maximum valid value). It doesn't matter if you set it to 2, 3 or even 1337 the output will be the same. (Correct me if I'm wrong)

[rack04]

x264 core:71 r1214 32-bit

Download (http://www.mediafire.com/?sharekey=b39064c936236ab08ef1259ff1b60e81e04e75f6e8ebb871)

Built by rack04 on August 17, 2009, 4:05:18 PM CST
$ gcc --version
gcc.exe (GCC) 4.4.1 (x86.core2.Komisar)
$ ./configure --extra-cflags="-march=core2"
Platform: X86
System: MINGW
asm: yes
avis input: yes
mp4 output: yes
pthread: yes
debug: no
gprof: no
PIC: no
shared: no
visualize: no
$ make fprofiled VIDS="bigbuckbunny.avs LosslessTouhou.avs riverbed.1920x1080.yuv"

Patched with:

x264_hrd_pulldown.15_interlace.fix.1206.diff (http://komisar.gin.by/x.patch/x264_hrd_pulldown.15_interlace.fix.1206.diff)
x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)

[JEEB]

x264 r1214 64bit unpatched:
download (http://jeeb.fiveforty.jp/x264/revision1214/x264.exe) ; hash (http://jeeb.fiveforty.jp/x264/revision1214/x264.md5)

built on Aug 18 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, otherwise defaults

________________________________________________________________________________

x264 r1214 32bit
download (http://jeeb.fiveforty.jp/x264/1214/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1214/relnotes.txt)

built on Aug 18 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=i686


x264 r1214 64bit
download (http://jeeb.fiveforty.jp/x264/1214_x64/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1214_x64/relnotes.txt)

built on Aug 18 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, -march=core2


patched with:

x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pulldown.15_interlace.fix.1206.diff (http://komisar.gin.by/x.patch/x264_hrd_pulldown.15_interlace.fix.1206.diff)


Hint: I do not add patches that are not mentioned. I do not _trust_ myself to do something like that. Anyways, now building without a VM since I moved to a fully 64bit environment at last. Next step would be to update the msys/mingw environment I have :3

[Fr4nz]

IMK ICC x264 1214 builds for x86/x64 here:

http://imk.cx/pc/x264/x264-r1214M-imk-win.7z

[Tarutaru]

x264 r1217 GCC4.4.0 win32 build:
x264-r1217-win32-patched (http://www.mediafire.com/?sharekey=c330f9eea9b6a9ca1bee9a6e9edd9c76a66c1b8c8cdf93cac95965eaa7bc68bc)

pthread, gpac, fprofiled.
patched with:
x264_win_zone_parse_fix_06.diff
x264_hrd_pulldown.15_interlace.fix.1217.diff

[techouse]

x264_hrd_pulldown.15_interlace.fix.1217.diff (http://pastebin.ca/1535080)

[alwa]

x264 r1217 32bit
download (http://www.mediafire.com/?n24zamgjnyn)


built on Aug 19 2009, gcc: 4.4.1 (x86.generic.Komisar)
fprofiled, defaults


x264 r1217 64bit
download (http://www.mediafire.com/?mkyn3jqmtiw)


built on Aug 19 2009, gcc: 4.4.1 (x86_64.generic.Komisar)
fprofiled, defaults



patched with:


x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pulldown.15_interlace.fix.1217.diff (http://www.mediafire.com/?0ijmtdodzty) (own)


I had the build and the updated patch before i saw techouse's updated patch, thats why...

[techouse]

x264_x64_r1217_unpatched (http://techouse.project357.com/builds/revision1217/x264.exe) | MD5 (http://techouse.project357.com/builds/revision1217/x264.md5)
GCC 4.4.1 20090803 (x64.core2.Komisar), unpatched, generic, fprofiled

________________________________________________________________________________

x264_x86_r1217_techouse (http://techouse.project357.com/builds/x264_x86_r1217_techouse.7z) | INFO (http://techouse.project357.com/nfo/x264_x86_r1217_techouse.txt)
GCC 4.4.1 20090803 (x86.core2.Komisar), fprofiled, -march=core2

x264_x64_r1217_techouse (http://techouse.project357.com/builds/x264_x64_r1217_techouse.7z) | INFO (http://techouse.project357.com/nfo/x264_x64_r1217_techouse.txt)
GCC 4.4.1 20090803 (x86_64.core2.Komisar), fprofiled, -march=core2

Patches used:

x264_hrd_pd_interlace.16.diff
x264_win_zone_parse_fix_06.diff

[Trahald]

Attached is hrd 16. it will patch to 1217. There is also a workaround for an inconsistency (not a bug) in x264. i_fps_den is sometimes the value passed from the frame server but other times its LCD to i_fps_num. so i just commented out the line. considering it only does anything when the den/num can be reduced, other times having no effect.
- x264_reduce_fraction( &h->param.i_fps_num, &h->param.i_fps_den );
+ //x264_reduce_fraction( &h->param.i_fps_num, &h->param.i_fps_den );
the framerate section of the sps of a PAL movie will take as many bits now as the sps of a NTSC movie. (negligible)

this should end the assert errors seen sometimes on PAL.

[microchip8]

Thanks Trahald, works nicely here ;)

[rack04]

x264 core:72 r1217M 32-bit

Download (http://www.megaupload.com/?d=GY10GX3F)

Built by rack04 on August 19, 2009, 2:05:45 PM CST
$ gcc --version
gcc.exe GCC: 4.4.1 (x86.core2.Komisar)
$ ./configure --extra-cflags="-march=core2"
Platform: X86
System: MINGW
asm: yes
avis input: yes
mp4 output: yes
pthread: yes
debug: no
gprof: no
PIC: no
shared: no
visualize: no
$ make fprofiled VIDS="bigbuckbunny.avs LosslessTouhou.avs riverbed.1920x1080.yuv"

Patched with:

x264_hrd_pd_interlace.16.diff (http://forum.doom9.org/showthread.php?p=1316462#post1316462)
x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)

[JEEB]

x264 r1217 64bit unpatched:
download (http://jeeb.fiveforty.jp/x264/revision1217/x264.exe) ; hash (http://jeeb.fiveforty.jp/x264/revision1217/x264.md5)

built on Aug 19 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, otherwise defaults

________________________________________________________________________________

x264 r1217 32bit
download (http://jeeb.fiveforty.jp/x264/1217/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1217/relnotes.txt)

built on Aug 19 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=i686


x264 r1217 64bit
download (http://jeeb.fiveforty.jp/x264/1217_x64/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1217_x64/relnotes.txt)

built on Aug 20 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, -march=core2


patched with:

x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pd_interlace.16.diff


Changing dates is what I get from building stuff near midnight.

[JEEB]

x264 r1222 64bit unpatched:
download (http://jeeb.fiveforty.jp/x264/revision1222/x264.exe) ; hash (http://jeeb.fiveforty.jp/x264/revision1222/x264.md5)

built on Aug 20 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, otherwise defaults

________________________________________________________________________________

x264 r1222 32bit
download (http://jeeb.fiveforty.jp/x264/1222/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1222/relnotes.txt)

built on Aug 20 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=i686


x264 r1222 64bit
download (http://jeeb.fiveforty.jp/x264/1222_x64/x264.exe) ; release notes (http://jeeb.fiveforty.jp/x264/1222_x64/relnotes.txt)

built on Aug 20 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, -march=core2


patched with:

x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pd_interlace.16.diff


Guess what is down again, m'kay~ and back up.

[techouse]

x264_x64_r1222_unpatched (http://techouse.project357.com/builds/revision1222/x264.exe) | MD5 (http://techouse.project357.com/builds/revision1222/x264.md5)
GCC 4.4.1 20090803 (x64.core2.Komisar), unpatched, generic, fprofiled

________________________________________________________________________________

x264_x86_r1222_techouse (http://techouse.project357.com/builds/x264_x86_r1222_techouse.7z) | INFO (http://techouse.project357.com/nfo/x264_x86_r1222_techouse.txt)
GCC 4.4.1 20090803 (x86.core2.Komisar), fprofiled, -march=core2

x264_x64_r1222_techouse (http://techouse.project357.com/builds/x264_x64_r1222_techouse.7z) | INFO (http://techouse.project357.com/nfo/x264_x64_r1222_techouse.txt)
GCC 4.4.1 20090803 (x86_64.core2.Komisar), fprofiled, -march=core2

Patches used:

x264_hrd_pd_interlace.16.diff
x264_win_zone_parse_fix_06.diff

[imk]

r1222M built with ICC.

Windows:
x264-r1222M-imk-win.7z (http://imk.cx/pc/x264/x264-r1222M-imk-win.7z)
win_build_info.txt (http://imk.cx/pc/x264/win_build_info.txt)

Mac OS X:
x264-r1222M-imk-osx.7z (http://imk.cx/pc/x264/x264-r1222M-imk-osx.7z)
osx_build_info.txt (http://imk.cx/pc/x264/osx_build_info.txt)



On a side note, I started updating my benchmark spreadsheet with r1217.
x264 Benchmarks (http://spreadsheets.google.com/pub?key=pbffjdC6iUPWs2HtYHwZ2VQ&gid=4&hl=sv)

There's still some I need to finish up with the placebo test, but you can get an idea from all the other results.

If you don't understand what all of the numbers or headers mean, click on the "Information" label at the top.

[komisar]

My 1222 versions of x264:
http://komisar.gin.by/

In addition I published a gdb-6.8.50.20090821-cvs (32/64-bit) (http://komisar.gin.by/mingw/) (need more testing)

[alwa]

@imk:

Your x86 32Bit build doesn't work at all on system. If i want to start an encoding nothing happens, but the process keeps running with 25% cputime (single threaded) like in an infinite loop. I have a C2Q Q9550 E0 on Win 7 x64 RC. The 64Bit build works fine though, so it is nothing dramatic to me.

Edit: r1163 is the latest that works with me, but auto thread detection and the progress indicator do not work. I hope that helps in some way...

[imk]

@imk:

Your x86 32Bit build doesn't work at all on system. If i want to start an encoding nothing happens, but the process keeps running with 25% cputime (single threaded) like in an infinite loop. I have a C2Q Q9550 E0 on Win 7 x64 RC. The 64Bit build works fine though, so it is nothing dramatic to me.

Edit: r1163 is the latest that works with me, but auto thread detection and the progress indicator do not work. I hope that helps in some way...

Can you get on IRC and find me? I'd like to compile some builds with various settings and see which work and which do not.

If you have time, come find me on Freenode in #x264. I use the nick Dopefish there.

[Tarutaru]

x264 r1222 built with gcc 4.4.0 (http://www.mediafire.com/?jdytjlmw5ai)

Compiler options:

-march=i686 -msse4.2
with pthread, gpac
fprofiled


Patches:

x264_hrd_pulldown.16_interlace.diff
x264_win_zone_parse_fix_06.diff

[Wishbringer]

Tried encoding some PSP videos with imk build 1222 in MeGUI (manually copied x264 into folder).
x264 crashed each time.
Tried same with Techouse build 1222, no crashes...
On the other hand, imk 64bit in Ripbot264 works great, so problem seems to be in 32bit build.

[imk]

Yeah, all of the problems seem related specifically to the 32-bit build. It all started happening around the time MBTree got committed. You should be using the 64-bit build if you have a 64-bit OS anyway. ;)

When I get some time I'll try and make some debug builds so I can narrow down what's going on. The 32-bit build works fine during profiling and benchmarking, but aside from that, I haven't actually used the 32-bit build to encode anything.

[juGGaKNot]

Tried encoding some PSP videos with imk build 1222 in MeGUI (manually copied x264 into folder).
x264 crashed each time.
Tried same with Techouse build 1222, no crashes...


It seams that techouse's build also crashes for a friend, i told him to get the patched and unpatched builds from techouse and try --longhelp, reporting back soon.

LE :

techouse and imk crash
jeebs work

i will make a debug build tomorrow.

[juGGaKNot]

x264_r1232_juGGaKNot (http://www.mediafire.com/download.php?adm0owztnvk)
GCC 4.4.1, fprofiled, patched
Source: GIT

Applied patches :

x264_win_zone_parse_fix_06.diff (http://www.mediafire.com/download.php?w4y4mdzymgh)

Please check Doom9.org patches thread (http://forum.doom9.org/showthread.php?t=130364), and GIT shortlog (http://git.videolan.org/gitweb.cgi?p=x264.git;a=shortlog) for more info.

Compiled by juGGaKNot with GCC 4.4.1 on Windows XP SP-2 32-bit.

Platform: X86
System: MINGW
asm: yes
avis input: yes
mp4 output: yes
pthread: yes
debug: no
gprof: no
PIC: no
shared: no
visualize: no

HRD needs to be updated again, Download link (http://www.mediafire.com/download.php?m4mxmr0uuzy)

[techouse]

I fixed the HRD patch so it works with r1232.

x264_hrd_pd_interlace.16.fix.1232.diff (http://pastebin.org/11898)

[imk]

r1232M built with ICC.

Windows:
x264-r1232M-imk-win.7z (http://imk.cx/pc/x264/x264-r1232M-imk-win.7z)
win_build_info.txt (http://imk.cx/pc/x264/win_build_info.txt)

Mac OS X:
x264-r1232M-imk-osx.7z (http://imk.cx/pc/x264/x264-r1232M-imk-osx.7z)
osx_build_info.txt (http://imk.cx/pc/x264/osx_build_info.txt)

[juGGaKNot]

r1232M built with ICC.

Windows:
x264-r1232M-imk-win.7z (http://imk.cx/pc/x264/x264-r1232M-imk-win.7z)
win_build_info.txt (http://imk.cx/pc/x264/win_build_info.txt)

Mac OS X:
x264-r1232M-imk-osx.7z (http://imk.cx/pc/x264/x264-r1232M-imk-osx.7z)
osx_build_info.txt (http://imk.cx/pc/x264/osx_build_info.txt)

if you use complete log you might also want to take a look at the console diff ( shows the encoding settings used in the cmd window )

[techouse]

x264_x64_r1232_unpatched (http://techouse.project357.com/builds/revision1232/x264.exe) | MD5 (http://techouse.project357.com/builds/revision1232/x264.md5)
GCC 4.4.1 20090803 (x64.core2.Komisar), unpatched, generic, fprofiled

________________________________________________________________________________

x264_x86_r1232_techouse (http://techouse.project357.com/builds/x264_x86_r1232_techouse.7z) | INFO (http://techouse.project357.com/nfo/x264_x86_r1232_techouse.txt)
GCC 4.4.1 20090803 (x86.core2.Komisar), fprofiled, -march=core2

x264_x64_r1232_techouse (http://techouse.project357.com/builds/x264_x64_r1232_techouse.7z) | INFO (http://techouse.project357.com/nfo/x264_x64_r1232_techouse.txt)
GCC 4.4.1 20090803 (x86_64.core2.Komisar), fprofiled, -march=core2

Patches used:

x264_hrd_pd_interlace.16.fix.1232.diff (http://pastebin.org/11898)
x264_win_zone_parse_fix_06.diff

[JEEB]

x264 r1232 64bit unpatched:
download (http://jeeb.fiveforty.jp/x264/revision1232/x264.exe) ; hash (http://jeeb.fiveforty.jp/x264/revision1232/x264.md5)

built on Aug 25 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, otherwise defaults

________________________________________________________________________________

x264 r1232 32bit
download (http://jeeb.fiveforty.jp/x264/1232/x264.exe) ; release notes

built on Aug 25 2009, gcc: 4.3.4 20090220 (prerelease) (x32.generic.Komisar)
fprofiled, -march=i686


x264 r1232 64bit
download (http://jeeb.fiveforty.jp/x264/1232_x64/x264.exe) ; release notes

built on Aug 25 2009, gcc: 4.3.4 20090220 (prerelease) (x64.generic.Komisar)
fprofiled, -march=core2


patched with:

x264_win_zone_parse_fix_06.diff (http://kemuri9.net/dev/x264/patches/x264_win_zone_parse_fix_06.diff)
x264_hrd_pd_interlace.16.fix.1232.diff (http://pastebin.org/11898)


I will upload release notes with the changelogs later on as I will have time :3 Nothing really has changed on that side, for the exception of the nal_hrd patch version of course, so I guess it's alright.