Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6 0/1] avformat: add Software Defined Radio support
Date: Sun, 2 Jul 2023 20:52:16 +0200 (CEST)
Message-ID: <NZMwgyL--3-9@lynne.ee> (raw)
In-Reply-To: <ZKGg2sd2HEyB4o9d@phare.normalesup.org>

Jul 2, 2023, 18:08 by george@nsup.org:

> Jean-Baptiste Kempf (12023-07-02):
>
>> Absolutely not.
>> You are the only one who believes that.
>>
>
> Except for the person who created FFmpeg in the first place. And
> probably other people too.
>
> Most great Libre Software projects are hackers playgrounds first. They
> become immensely useful as a byproduct. There is a classical fable to
> illustrate the shortsightedness of people who want FFmpeg to be a
> Serious OpenSource Project TM, it's called The Goose that Laid the
> Golden Eggs, I assume everybody knows how it ends.
>

git master is not a playground, but it is certainly a place for developers
to experiment with ideas they're *seriously* exploring.

Sonic and Snow were experiments. They didn't work out, but nevertheless,
they made their mark on the status quo of compression research at the time.

FFV1 was an experiment. It worked out, being an IETF standard.
The native mpeg encoders were experiments. They worked out, and their
rate control system largely inspired x264's rate control systems.
The DNN filtering stuff was an experiment. It didn't work out.The native Opus encoder was an experiment, and it holds up well against
libopus, if a bit slow and misguided.
The AAC encoder was always an experiment. Did it work out? Let's
find out after the third rewrite :)

As for libavsdr? Time will tell. But it's certainly got a niche to fill,
as currently, you have to setup large and complex gnuradio filterchains.
But, I would prefer for it to be in a separate repository.
_______________________________________________
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".

  parent reply	other threads:[~2023-07-02 18:52 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 21:25 Michael Niedermayer
2023-06-28 21:25 ` [FFmpeg-devel] [PATCH v6] " Michael Niedermayer
2023-06-29 15:43 ` [FFmpeg-devel] [PATCH v6 0/1] " Paul B Mahol
2023-06-30 14:08   ` Michael Niedermayer
2023-06-30 14:38     ` Jean-Baptiste Kempf
2023-06-30 17:40       ` Michael Niedermayer
2023-06-30 17:57         ` Paul B Mahol
2023-06-30 18:02         ` Michael Niedermayer
2023-07-01 15:28           ` Rémi Denis-Courmont
2023-07-01 18:56             ` Michael Niedermayer
2023-07-01 19:30               ` Paul B Mahol
2023-07-02  9:40           ` Nicolas George
2023-07-02 10:08             ` Paul B Mahol
2023-07-02 13:47               ` Rémi Denis-Courmont
2023-07-02 16:01                 ` Nicolas George
2023-07-02 18:21                   ` Rémi Denis-Courmont
2023-07-02 11:00       ` Michael Niedermayer
2023-07-02 16:11         ` Nicolas George
2023-07-02 18:55         ` Lynne
2023-07-02 21:14           ` Michael Niedermayer
2023-07-02 22:03             ` Lynne
2023-07-02 22:46               ` Michael Niedermayer
2023-07-10  6:57                 ` Lynne
2023-07-11 21:09                   ` Michael Niedermayer
2023-06-30 17:00     ` Kieran Kunhya
2023-07-01 15:20       ` Michael Niedermayer
2023-06-30 21:36     ` Martin Storsjö
2023-07-01 14:44       ` Michael Niedermayer
2023-07-01 19:41         ` Martin Storsjö
2023-07-01 19:56           ` Tomas Härdin
2023-07-01 20:06           ` Michael Niedermayer
2023-07-01 20:42             ` Kieran Kunhya
2023-07-01 21:25               ` Michael Niedermayer
2023-07-01 21:32                 ` Kieran Kunhya
2023-07-01 19:08       ` Anton Khirnov
2023-07-01 19:35       ` Michael Niedermayer
2023-07-02  9:58       ` Nicolas George
2023-07-02 10:10         ` Paul B Mahol
2023-07-02 10:43         ` Jean-Baptiste Kempf
2023-07-02 16:07           ` Nicolas George
2023-07-02 18:13             ` Jean-Baptiste Kempf
2023-07-02 18:20               ` Nicolas George
2023-07-02 18:32                 ` Michael Niedermayer
2023-07-02 18:52             ` Lynne [this message]
2023-07-02 19:52               ` Nicolas George
2023-07-02 20:29                 ` Lynne
2023-06-30 22:02     ` Tomas Härdin
2023-07-02  9:28       ` Nicolas George

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=NZMwgyL--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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