[MPlayer-dev-eng] branching off rc4

[Reimar Döffinger]

On Sat, Jul 10, 2010 at 03:53:50PM -0400, compn wrote:
> On Sat, 10 Jul 2010 16:58:13 +0200, Steinar H. Gunderson wrote:
> >On Fri, Jun 25, 2010 at 12:07:43PM +0200, Attila Kinali wrote:
> >> Are there any known regressions or bugs that should be fixed
> >> before a release?
> >
> >I ran my codec test suite (mostly binary) against current trunk, and it's
> >bombing left and right. Something central has changed, although I cannot say
> >exactly what, nor whether it's something benign (ie. some roundoff somewhere
> >changed) or sign of a real bug. (FWIW, the test asks MPlayer to decode a
> >sample to an yuv4mpeg output and then compares its checksum to a known one,
> >so it will certainly be sensitive to changes in roundoff.)
> >
> >Does anyone have any good ideas that would save me from a long bisect?
> >The tests are:
> >
> >Passing: fraps qt3ivx qtavui qtcvid qtprores qtsvq3 rv40win wmv9dmo wmvdmo wmvvc1dmo
> >Failing (different output): divxds ffh264 indeo5 msuscls qt261 smartsight vp6 vp7 vsswlt wmv8 zmbv
> 
> according to my binaries, it was between r30521 and r31372 for
> vp6. so at least that narrows it down a bit.

What is the difference exactly? It's unlikely there's any bug in real-world
use with ffh264, I'm quite convinced someone whould have noticed.

> btw, why not use -vo md5sum?

The way that does the calculation has changed as well, so anything
except grayscale pictures would be "broken" when just comparing
its output.