Apr 26, 2021, 02:36 by c...@passwd.hu: > > > On Sun, 25 Apr 2021, Lynne wrote: > >> This is the same patch sent in January, rebased on top of the ABI bump >> patchset. >> >> Two additions mirror exactly what AVFrame has - an opaque field >> and an opaque_ref for user-side private data. >> For justification on the void *opaque field, you can read the archives, >> since the question was brought up in January. >> >> As for the time_base field, for now, it will only be used to inform the user, >> and will not alter the behavior of the libraries. That change will come as an >> optional flag. >> > > I would like to see some documentation and code which shows when the > time_base is respected and when it is not before it is added to AVPacket. > After the bump we usually have a 1-2 months of cooldown when the ABI can > change, so there really is no rush. >
I didn't mean to say that it'll be done during the bump, but rather after it. Once we add time_base, there are no ABI-breaking changes to support what I was thinking of. Or do you still want to see some code? It's not a small amount of work. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
