[FFmpeg-devel] About guess_correct_pts / AVFrame.best_effort_timestamp
Thu Feb 17 21:09:17 CET 2011
Le nonidi 29 pluvi?se, an CCXIX, Ronald S. Bultje a ?crit?:
> I disagree here. If other frameworks, SDKs or wrapper-style thingies
> want to interoperate with FFmpeg, they have to fullfill our API
Of course they have to. But a library is there to help programming
applications, not to act as a dictator or a spoiled brat, and therefore the
API requirements should be reasonable and practical.
Now, let me state it clearly:
lavc should be usable to decode (up to a timestamp on the decoded frame)
MPEG-4 or H.264 with B-frames coming from an AVI decoded by a lightweight
If you do not share this principle, I guess we should simply agree to
disagree and stop there.
> But like I said, my motivation for this subject is gone. The patch is
> rejected, I've explained why, and that's all I'll say about it.
Well, I sincerely think I can not be blamed for the API divergence.
By the way, is someone working on removing guess_correct_pts from ffmpeg and
ffplay? That would be coherent with the rest of the discourse.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
More information about the ffmpeg-devel