On 11/26/2017 12:19 PM, Nicolas George wrote: > James Almer (2017-11-26): >> The old decode API is not scheduled for removal right now probably >> because 99% of decoders need to be ported. > > I think this statement contains some confusion that is harmful to the > discussion. > > There are two interfaces worth considering in this discussion: the > application -> library interface, i.e. the avcodec_decode_*dio() > functions, and the framework -> decoder interface, i.e. the decode / > receive_frame / ... callbacks. > > When you are stating "because 99% of decoders need to be ported", you > are referring to the framework-decoder interface. On the other hand, the > misuse of the API that is at the origin of this thread is related to the > application-library interface.
Yes, my bad. Got the public API and the internal callbacks mixed. So ignore that part. Guess then that the functions did not get a removal schedule because they are still too ubiquitous downstream. My second paragraph stands, in any case. I consider this a good chance to get downstreams to migrate. > > We could deprecate avcodec_decode_*dio() right now even though the > decoders are not all ported. They are already deprecated. I assume you meant remove. > > Regards, > > > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
