[MPlayer-dev-eng] [PATCH] ve_lavc delayed frames
Michael Niedermayer
michaelni at gmx.at
Wed Jul 28 13:31:50 CEST 2004
Hi
On Wednesday 28 July 2004 12:47, Loren Merritt wrote:
> On Wed, 28 Jul 2004, Michael Niedermayer wrote:
> > On Tuesday 27 July 2004 00:49, Loren Merritt wrote:
> > > When encoding to lavc with b-frames, mencoder emits some dummy frames
> > > at the beginning of the output video (because lavc hasn't returned any
> > > compressed frames yet). This causes A-V desync, and (the case that I
> > > first noticed) messes with timestamps in a variable-framerate video.
> > >
> > > This patch supresses the dummy frames.
> >
> > why do u use lavc_venc_context->coded_frame->pict_type instead of
> > outsize?
>
> I'm pretty sure frames aren't supposed to be of type '?', while I saw no
> particular reason that size 0 should be invalid. Maybe I'm wrong, though.
see output_example.c in ffmpeg cvs, but u are right pict_type may work too,
its just not exactly supposed to be used for this, it could be uninitalzed or
coded_frame could be NULL, as no frame has been written yet theres no
gurantee that coded_frame contains meaningfull values ...
[...]
--
Michael
level[i]= get_vlc(); i+=get_vlc(); (violates patent EP0266049)
median(mv[y-1][x], mv[y][x-1], mv[y+1][x+1]); (violates patent #5,905,535)
buf[i]= qp - buf[i-1]; (violates patent #?)
for more examples, see http://mplayerhq.hu/~michael/patent.html
stop it, see http://petition.eurolinux.org & http://petition.ffii.org/eubsa/en
More information about the MPlayer-dev-eng
mailing list