On Fri, Mar 1, 2024 at 10:34 PM Lynne <d...@lynne.ee> wrote: > >> If it's the last case, or simply being a one-off, I can agree with > deprecating > >> and remove it next bump. But if the developer thinks they will have > time and > >> have motivation to work on it in the future, I think we should leave it > at just > >> deprecation plus disabling building the encoder by default, until the > issue is > >> brought up again at say, after the next version bump. > >> After all, CELT started out more than 10 years before Opus was > standardized, > >> and its EC code has made it all the way to AV2 despite its core > remaining > >> visibly similar over the years. And FFv1 was used as an inspiration for > FLIC, > >> which went on to become JPEG-XL. > >> > > > > Sure, but there was active interest in all of these. I see no active > > interest in Sonic. > > > > No one had any interest in CELT for years until it was used in Mumble, > or Speex initially, or FLIC, as it they were not competitive enough on its > own, > and Vorbis, or Opus for the first few years. >
There is nothing stopping developers to work on their own fork and release the codec when ready, or at least there is moderate interest The developer has said there's interest in continuing to work on it > in the future. > The developer expressed interest in literally everything in ffmpeg, there needs to be a threshold in what is reasonably expected to be worked on in a lifetime. I don't see why we shouldn't give him a chance to work on it for > a bit longer before we bring it up again for removal. > Because people had 10 years to work on it a bit longer and they didn't. Claiming interest only because there is an active removal process is not very healthy for the codebase (or the community). -- Vittorio _______________________________________________ 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".
