On 9/5/2023 2:31 PM, James Almer wrote: > Users relying on global side data being in the first packet need to call > the inject() lavf function to enable said functionality. As that > function is now deprecated, they will get the relevant warning and be > directed to the global side data API. > Nothing is being dropped silently. Their code will behave as usual > during the deprecation period.
Thanks for clarifying. > What makes this different to every other API that was introduced with > relevant documentation and references to it in the deprecacted/replaced API? This is true, FFmpeg has terrible doc policies, but it is worth pointing how awful they are once in a while when new ones are added. TBF that is what keeps a whole cottage industry of people employed: Simply knowing the FFmpeg API, as it is non-trivial to know what doc / func / struct you even need for a given problem. > It's IMO very clear in the doxy: Instead of calling inject() and looking > at packet side data, just look at the always available avctx side data. > Similarly, instead of looking or filling AVStream.side_data, you look or > fill the field in AVStream.codecpar. We can agree to disagree. - Derek _______________________________________________ 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".
