Changes (r641-r644) in lemans terms?

[MetalPhreak]

Could someone please explain to me what the latest changes in x264 mean to me (ie the average user)? The changelog is always a bit condensed and I don't understand the code.
Sorry for being a nuisance.

[akupenguin]

It's faster, and I fixed a bug that no one probably ever encountered. You can ignore the side effects of r642.

[MetalPhreak]

Okay then, thanks akupenguin.

[LoRd_MuldeR]

akupenguin, were there any changes that effect the Interface of the libx264.dll ???
According to Gruntster "anything after R641 causes Avidemux to crash"

[akupenguin]

Jarod helped me track it down. Diagnosis: gcc on x86_32 fails to ensure alignment of data on the stack, even when I explicitly ask for alignment. r642 added sse2 quant functions, which manipulate data on the stack. sse2 crashes if it's misaligned.

[LoRd_MuldeR]

Jarod helped me track it down. Diagnosis: gcc on x86_32 fails to ensure alignment of data on the stack, even when I explicitely ask for alignment. r642 added sse2 quant functions, which manipulate data on the stack. sse2 crashes if it's misaligned.

Thanks for reply. But can you explain in simple words what this does mean for x264 users? :o

[akupenguin]

It means you can't use the new sse2 optimizations until I find a workaround.

[LoRd_MuldeR]

It means you can't use the new sse2 optimizations until I find a workaround.

allright. good luck then :)

[akupenguin]

Workaround: http://akuvian.org/src/x264/x264_stack_align.0.diff
Any testers? I could never reproduce the problem on my own computer, so I can't tell if this fixes it.

[gruntster]

It does the trick for me. Works well again. :)

[LoRd_MuldeR]

It does the trick for me. Works well again. :)

Could you upload the fixed DLL, so I can test it?

[gruntster]

Could you upload the fixed DLL, so I can test it?

Sure.

Available here: http://www.razorbyte.com.au/x264

[LoRd_MuldeR]

Sure.

Available here: http://www.razorbyte.com.au/x264

Works like a charm. Thank you!