[FFmpeg-cvslog] r18376 - trunk/doc/APIchanges
Ronald S. Bultje
Thu Apr 9 03:05:10 CEST 2009
On Wed, Apr 8, 2009 at 8:50 PM, Uoti Urpala <uoti.urpala at pp1.inet.fi> wrote:
> And exactly what are you supposed to place in the AVPacket? Presumably
> packets from libavformat are OK, but what about other data? Exactly
> which fields need to be filled? This entry doesn't really tell how you
> should convert code using the old API to the new one.
If I had such questions, I'd look at the API docs for the functions,
not at a file that quickly documents API changes. But it's true, this
information is missing from the API docs as well. Got a patch? Right
now just flags, data and size are used.
I suppose eventually someone could "fix" all these horrible B-frame
containing codecs so that the timestamp of the output frame
(regardless of delay) is somehow available without having to use all
these hacks to set user data of obscure fields in AVCodecContext.
More information about the ffmpeg-cvslog