From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec: remove sonic lossy/lossless audio Date: Fri, 01 Mar 2024 21:33:18 +0100 Message-ID: <170932519868.29002.10487420365575257741@lain.khirnov.net> (raw) In-Reply-To: <NrvXOAl--3-9@lynne.ee> Quoting Lynne (2024-03-01 20:41:53) > Mar 1, 2024, 19:59 by anton@khirnov.net: > > > Quoting Lynne (2024-02-29 14:30:55) > > > >> We offer support for it. Someone must have used it. > >> I'm sure there are less used game codecs we support than Sonic. > >> > > > > [citation needed] > > > > Is there any evidence that it was used for anything other than > > development and testing? That anyone has any actual samples in it they'd > > like to play? > > > > There's always the possibility that someone encoded samples years > ago and deleted the originals. Same as with Snow. > > My only concern is that this sets a sensitive precedent to get rid of > old codec code with low weight under unclear conditions. Where do > we draw the line? > SMPTE? ISO/IEC standardization? IETF? AOM? > Having *a* spec (Sonic doesn't, but neither did FFv1 until a few years > ago)? > A single company pushing for it many years ago with no spec, > like SpeedHQ, or the many niche lossless/intra-only codecs? > > Or simply having one single implementation in FFmpeg, and no spec at all, > and having an experimental flag, and no activity for a very long amount of time? I'd draw the line somewhere around what I said above - some evidence that it was used "seriously". > 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. -- Anton Khirnov _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-03-01 20:33 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 12:56 [FFmpeg-devel] [PATCH 1/2] MAINTAINERS: remove inactive developer J. Dekker 2024-02-28 12:56 ` [FFmpeg-devel] [PATCH 2/2] avcodec: remove sonic lossy/lossless audio J. Dekker 2024-02-28 13:23 ` Andreas Rheinhardt 2024-02-28 13:29 ` Michael Niedermayer 2024-02-28 13:31 ` J. Dekker 2024-02-28 13:41 ` Nicolas George 2024-02-28 13:57 ` Vittorio Giovara 2024-02-28 14:08 ` J. Dekker 2024-02-28 17:55 ` James Almer 2024-02-28 18:36 ` Jean-Baptiste Kempf 2024-03-10 13:12 ` Alexander Strasser via ffmpeg-devel 2024-02-28 20:23 ` Rémi Denis-Courmont 2024-02-28 22:13 ` Lynne 2024-02-29 1:50 ` Vittorio Giovara 2024-02-29 13:30 ` Lynne 2024-02-29 14:44 ` Vittorio Giovara 2024-03-01 1:13 ` Michael Niedermayer 2024-03-10 19:45 ` Leo Izen 2024-03-01 18:59 ` Anton Khirnov 2024-03-01 19:03 ` Nicolas George 2024-03-01 19:41 ` Lynne 2024-03-01 20:33 ` Anton Khirnov [this message] 2024-03-01 21:34 ` Lynne 2024-03-02 13:33 ` Vittorio Giovara 2024-03-01 20:14 ` Tomas Härdin 2024-02-28 14:38 ` [FFmpeg-devel] [PATCH 1/2] MAINTAINERS: remove inactive developer Vittorio Giovara
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=170932519868.29002.10487420365575257741@lain.khirnov.net \ --to=anton@khirnov.net \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git