Vittorio Giovara <vittorio.giov...@gmail.com> writes: > On Wed, Feb 28, 2024 at 2:38 PM J. Dekker <j...@itanimul.li> wrote: > >> >> Michael Niedermayer <mich...@niedermayer.cc> writes: >> >> > [[PGP Signed Part:Undecided]] >> > On Wed, Feb 28, 2024 at 01:56:10PM +0100, J. Dekker wrote: >> >> This was an experimental/research codec of which ffmpeg is the only >> >> encoder and decoder, >> > >> > >> >> development has stalled >> > >> > Thats not true, there was private dicussion making sonic the most >> > advanced audio codec in FFmpeg a few months ago. >> > Iam not saying that will happen, i am just saying there was a >> > discussion about it. And that iam in principle interrested in >> > working on this. Its possible i will not have enough time ... >> > >> >> The last commit which actually changed the codec was >> 6026a5ad4f135476c7a1f51f8cfa7f4cc2ca0283 by you in 2013 which is over 10 >> years ago. For an experimental codec I think it's pretty safe to say >> that development has stalled. >> >> Keeping the codec around based on 'what if?'s doesn't seem >> reasonable. Besides, if you do make sonic the most advanced audio codec >> in FFmpeg there's nothing which says you couldn't re-add it at a later >> date when it's being actively developed again. >> > > +1 > > but please do the deprecation dance as suggested
As mentioned on IRC the suggestion was to leave the codec IDs as-is so that they can still be identified even if we cannot decode them. So there is no need to deprecate anything here, public API is left untouched and codec removed as if it were disabled at compile time. Will post an updated patch. -- jd _______________________________________________ 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".
