*warning x264 revision 307 broken*

[bob0r]

x264 revision 307 has some problems encoding, most likely something small, just be aware of it, when you encode your videos!

source:
http://mirror05.x264.nl/public/x264-source.png

307:
http://mirror05.x264.nl/public/x264-307.png

Edit:
NOT using --weightb, or using --no-asm (what CREXbzh said) can be used as "temporary solution", untill revision 308 hopefully ;)

--weightb = Weighted biprediction (B-frames)
--no-asm = Disable all CPU optimizations

[CREXbzh]

Another solution is to either disable the ASM code, or to use an AMD-64 in 64 bits mode, which apparently doesn't suffer from the bug

[Revgen]

@Bob0r

Does this happen when encoding to MP4? Or both MP4 and Matroska?

FAIK this new version just updates the GPAC sources, which shouldn't affect Matroska output should it?

[bob0r]

@Bob0r

Does this happen when encoding to MP4? Or both MP4 and Matroska?

FAIK this new version just updates the GPAC sources, which shouldn't affect Matroska output should it?

This occurs with .264, .mp4, .mkv and .avi

My builds always get compiled with the latest gpac, first gpac gets updated/compiled, then the new x264 revision gets compiled.

So its an x264 encoder issue (unless its not a bug and libavcodec-decoder needs updating)

[Revgen]

Looks like I'll wait until it's fixed.

Thanks.

[bond]

FAIK this new version just updates the GPAC sources, which shouldn't affect Matroska output should it?every new revision uses a changed version of x264 or said the other way round a new compile is only done when x264 changes

[Pasqui]

x264 revision 308:
typo in ia32 x264_pixel_avg_weight_w8_mmxext
Seems like problem should be fixed with up-to-date build.

[bob0r]

Affirmative.