[FFmpeg-devel] Fix get wrong frame rate with rm/rmvb files

Reimar Döffinger Reimar.Doeffinger
Sat Nov 14 18:05:24 CET 2009


On Sat, Nov 14, 2009 at 11:51:14AM +0200, Kostya wrote:
> On Sat, Nov 14, 2009 at 09:25:43AM +0100, Reimar D?ffinger wrote:
> > On Sat, Nov 14, 2009 at 10:20:25AM +0200, Kostya wrote:
> > > On Sat, Nov 14, 2009 at 07:49:24AM +0200, Kostya wrote:
> > > > On Fri, Nov 13, 2009 at 11:31:45PM +0000, Carl Eugen Hoyos wrote:
> > > [...]
> > > > > 
> > > > > @Kostya; Decoding says
> > > > > [rv40 @ 0x88e9380]Need DQUANT
> > > > > [rv40 @ 0x88e9380]Need DQUANT
> > > > > [rv40 @ 0x88e9380]Need DQUANT
> > > > > [rv40 @ 0x88e9380]Slice indicates MB offset 0, got 76%  1%  0.7% 0 0
> > > > > [rv40 @ 0x88e9380]Dquant for B-frame
> > > > > [rv40 @ 0x88e9380]Dquant for B-frame
> > > > > [rv40 @ 0x88e9380]Dquant for B-frame
> > > > > [rv40 @ 0x88e9380]Dquant for B-frame
> > > > > [rv40 @ 0x88e9380]Dquant for B-frame
> > > > > [rv40 @ 0x88e9380]concealing 0 DC, 0 AC, 0 MV errors
> > > > > for one frame that looks broken, works fine with the binary decoder.
> > > > 
> > > > Thanks, I'll look at it.
> > > 
> > > Looks like another case when decoder should concatenate slices.
> > 
> > Well, I'd say it's the demuxer that should concatenate them though
> > (which is obviously what MPlayer's demuxer does) or alternatively
> > a parser.
> 
> Actually, decoder does that - since MPlayer demuxer fails this one too
> and binary decoder does not produce wrong picture.

Oh. Just because Carl said it worked with MPlayer's native demuxer,
though I don't know if that has the side-effect of choosing the binary
decoder or something.



More information about the ffmpeg-devel mailing list