[FFmpeg-devel] FATE wmv8_x8intra.wmv sample?

Reimar Döffinger Reimar.Doeffinger at gmx.de
Mon Jan 9 11:00:00 CET 2012


On Mon, Jan 09, 2012 at 04:11:53AM +0100, Michael Niedermayer wrote:
> On Sun, Jan 08, 2012 at 07:15:10PM +0100, Reimar Döffinger wrote:
> > On Sun, Jan 08, 2012 at 12:33:16PM +0100, Reimar Döffinger wrote:
> > > On Fri, Jan 06, 2012 at 03:06:53AM +0100, Michael Niedermayer wrote:
> > > > On Thu, Jan 05, 2012 at 05:02:21PM +0100, Reimar Döffinger wrote:
> > > > > Hello,
> > > > > it seems we have a file wmv8_x8intra.wmv in fate-suite but no test runs
> > > > > it?
> > > > > The issue with that is that the MPlayer regression tests use it and the
> > > > > result changed.
> > > > > Since FFmpeg doesn't seem to test it I now have no idea what to do about
> > > > > that (result looks fine as far as I can tell, but that does not have to
> > > > > mean much).
> > > > > Any suggestions?
> > > > 
> > > > what commit caused the change ?
> > > 
> > > I don't know. And I also forgot to ask the most important question:
> > > why is that sample file not used during "make fate"??
> > 
> > Hm, it looks like it gives two sets of results: one for x86_64 and one
> > for everything else.
> 
> i get the same values on x86_32 and 64
> and different ones between different compiler versions on openbsd
> and iam seeing the same on the ppc machines

Hm, I don't see any all that clear pattern I have to admit.

> > That stays like that even with -flags +bitexact and -idct simple.
> > Any ideas?
> 
> -idct simple is wrong it should be the wmv2 idct

Shouldn't really matter when it comes to eliminating differences in the
result between machines.

> Anyway, IMHO until this is debuged & fixed the test should be disabled,
> it doesnt serve any purpose when it doesnt work

Well, it would serve as a reminder that there is something very strange
going on in the wmv8 decoder. But I admit that's not much value.


More information about the ffmpeg-devel mailing list