Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec: remove sonic lossy/lossless audio
Date: Thu, 29 Feb 2024 15:44:46 +0100
Message-ID: <CABLWnS82f258MfwPrfjULMx+94db7dnzdSrq-EPCDcCoVBFTEA@mail.gmail.com> (raw)
In-Reply-To: <Nrp2tIS--3-9@lynne.ee>

On Thu, Feb 29, 2024 at 2:31 PM Lynne <dev@lynne.ee> wrote:

> Feb 29, 2024, 02:50 by vittorio.giovara@gmail.com:
>
> > On Wed, Feb 28, 2024 at 11:13 PM Lynne <dev@lynne.ee> wrote:
> >
> >> Feb 28, 2024, 14:29 by michael@niedermayer.cc:
> >>
> >> > 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 ...
> >> >
> >>
> >> I would strongly prefer for it to be kept around as well.
> >>
> >> Otherwise it creates precedence to throw out codecs if they're
> >> not popular enough, and we're known for being able to play
> >> most formats ever created.
> >>
> >
> > IMO there is a big difference between a game codec and an experimental
> > codec that hasn't come out of ffmpeg
> >
>
> We offer support for it. Someone must have used it.
> I'm sure there are less used game codecs we support than Sonic.
>

the point here is that game codecs are part of digital preservation and and
effort against digital obsolescence
an "experimental codec" that nobody (read: a very limited amount of users)
used except ffmpeg devs as playground does not warrant it being in the
codebase (but rather a branch or personal fork) IMO
-- 
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-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2024-02-29 14:45 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 [this message]
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
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=CABLWnS82f258MfwPrfjULMx+94db7dnzdSrq-EPCDcCoVBFTEA@mail.gmail.com \
    --to=vittorio.giovara@gmail.com \
    --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