From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support
Date: Fri, 23 Jun 2023 23:18:05 +0200
Message-ID: <20230623211805.GP3250409@pb2> (raw)
In-Reply-To: <da949553a59bba2d47439d08f8d250a9fd310934.camel@haerdin.se>
[-- Attachment #1.1: Type: text/plain, Size: 1676 bytes --]
Hi Tomas
On Fri, Jun 23, 2023 at 10:10:29PM +0200, Tomas Härdin wrote:
> No. Absolutely not.
>
> Radio stuff belongs in radio projects such as GNU Radio. This is
> extreme scope creep.
>
> I can throw an AM detector together in 15 minutes. That doesn't mean it
> belongs in FFmpeg. You are also treading into modem territory, among
> other things. Please contribute to actually existing free radio
> projects instead.
And DSP belongs in DSP projects, mpeg decoding belongs in libmpeg2
png, ogg, vorbis belong in their respective projects
in fact FFmpeg shouldnt exist we should all have been contributing to
gstreamer
Wouldnt that be the same line of thought ?
But seriously there are 2 things.
Theres myself and what is fun for me to work on (you suggest i shouldnt have fun?)
And there is FFmpeg that is missing any and all SDR support
Are you planing to add SDR support through some library like GNU radio
to FFmpeg ?
I think GNU radio is a poor choice, even just the base package has
"Installed-Size: 407 MB" that would be huge dependancy to avoid ATM 2 pages
of modem code, also GNU Radio is not LGPL, i think FFmpeg generally prefers
LGPL over GPL. Not that i personally have anything against GPL, I like GPL
but thats not the preferred license in FFmpeg
do you suggest we should create a libavradio ?
or can you suggest an existing library that would fit the C + clean ASM
LGPL style that FFmpeg tends to prefer ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who are too smart to engage in politics are punished by being
governed by those who are dumber. -- Plato
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2023-06-23 21:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 22:28 Michael Niedermayer
2023-06-22 13:43 ` Michael Niedermayer
2023-06-22 13:55 ` James Almer
2023-06-22 15:05 ` Michael Niedermayer
2023-06-22 15:10 ` James Almer
2023-06-22 16:26 ` Michael Niedermayer
2023-06-22 16:42 ` James Almer
2023-06-22 22:00 ` Michael Niedermayer
2023-06-23 2:34 ` Kieran Kunhya
2023-06-23 11:17 ` Michael Niedermayer
2023-06-23 11:36 ` Kieran Kunhya
2023-06-23 16:37 ` Rémi Denis-Courmont
2023-06-23 18:12 ` Michael Niedermayer
2023-06-23 18:17 ` Paul B Mahol
2023-06-23 18:56 ` Michael Niedermayer
2023-06-23 19:10 ` Paul B Mahol
2023-06-23 19:16 ` James Almer
2023-06-24 20:27 ` Rémi Denis-Courmont
2023-06-24 21:03 ` Tomas Härdin
2023-06-25 13:53 ` Michael Niedermayer
2023-06-25 14:25 ` Michael Niedermayer
2023-06-24 22:19 ` Nicolas George
2023-06-25 14:10 ` Michael Niedermayer
2023-06-27 19:09 ` Rémi Denis-Courmont
2023-06-28 22:15 ` Tomas Härdin
2023-06-29 7:14 ` Nicolas George
2023-06-29 9:46 ` Jean-Baptiste Kempf
2023-06-30 21:51 ` Tomas Härdin
2023-07-02 8:11 ` Michael Niedermayer
2023-07-02 9:34 ` Nicolas George
2023-07-02 9:54 ` Tomas Härdin
2023-07-02 9:56 ` Nicolas George
2023-06-23 20:10 ` Tomas Härdin
2023-06-23 21:18 ` Michael Niedermayer [this message]
2023-06-24 9:51 ` Tomas Härdin
2023-06-24 21:01 ` Michael Niedermayer
2023-06-24 22:01 ` Tomas Härdin
2023-06-25 9:54 ` Michael Niedermayer
2023-06-27 9:00 ` Tomas Härdin
2023-06-27 10:57 ` Nicolas George
2023-06-27 17:07 ` Tomas Härdin
2023-06-27 17:11 ` Nicolas George
2023-06-25 10:23 ` Kieran Kunhya
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=20230623211805.GP3250409@pb2 \
--to=michael@niedermayer.cc \
--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