From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] What is FFmpeg and what should it be
Date: Wed, 2 Aug 2023 14:55:21 +0200
Message-ID: <20230802125521.GG7802@pb2> (raw)
In-Reply-To: <CABLWnS-j+xYPYDJ88FdoWF46bEkaw-bqtZhdygTfU4E3Ea+JaQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2403 bytes --]
Hi Vittorio
On Wed, Aug 02, 2023 at 03:44:13AM +0200, Vittorio Giovara wrote:
> On Sun, Jul 30, 2023 at 3:04 PM Nicolas George <george@nsup.org> wrote:
>
> > Kieran Kunhya (12023-07-28):
> > > FFmpeg doesn't implement TCP in userspace, it doesn't implement the
> > > WiFi protocol etc etc. Different layers are delegated to different
> > > programs.
> >
> > Hi. You seem to be discussing this in more good faith than I previously
> > imagined, so I will try to tone done the irritation in my mails.
> >
>
> sorry for jumping in mid discussion, but shouldn't that be the case always?
>
> But if people started to routinely use FFmpeg on some kind of
> > bare-metal microcontroller where network hardware exists but the
> > official network stack is too big to share the space with FFmpeg, and if
> > somebody were to propose a limited network stack based on lavu's
> > cryptographic primitives, then it would totally make sense to accept it.
> >
>
> no? that sounds a terrible maintenance burden in terms of both code size
> and security issues, nobody wants that!
> what could be a viable compromise is *maybe* providing the hooks where
> needed where custom io and callbacks can be implemented, but afaict there
> are plenty of those in ffmpeg already
>
> FFmpeg has been successful because it relied on pragmatism rather than
> > dogmatic adherence to principles. Let us continue that way.
> >
>
> ffmpeg has been successful because points of contentions were resolved with
> consensus (most of the times) and not by sheer number of emails or email
> length about the topic. I am not even familiar with this avradio thing but
> if the community seems so against it, let's maybe find another solution
> (separate library, repository, tool etc) instead of wasting time and energy
> over the same points.
the code already is in a seperate repository. And is basically isolated
in a single demuxer and single input device.
Some people still complain that it exists
About the community i do not know what the majority wants. About users
iam fairly confident that they prefer having the option to use it than
not having the option.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
it is not once nor twice but times without number that the same ideas make
their appearance in the world. -- Aristotle
[-- 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-08-02 12:55 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 19:29 [FFmpeg-devel] [PATCH 1/6] configure: libavradio support Michael Niedermayer
2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 2/6] avutil/log: Add AV_CLASS_CATEGORY_RADIO_INPUT Michael Niedermayer
2023-07-22 20:30 ` Paul B Mahol
2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 3/6] avformat: add support for demuxers/inputs from avradio Michael Niedermayer
2023-07-22 20:35 ` Paul B Mahol
2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 4/6] avdevice/utils: add test for AV_CLASS_CATEGORY_RADIO_INPUT Michael Niedermayer
2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 5/6] fftools: avradio support Michael Niedermayer
2023-07-22 21:39 ` Lynne
2023-07-23 15:23 ` Michael Niedermayer
2023-07-23 18:49 ` Tomas Härdin
2023-07-23 19:01 ` James Almer
2023-07-23 22:56 ` Michael Niedermayer
2023-07-24 8:19 ` Nicolas George
2023-07-24 15:57 ` Michael Niedermayer
2023-07-24 22:30 ` Tomas Härdin
2023-07-25 14:17 ` Tomas Härdin
2023-07-24 20:19 ` Tomas Härdin
2023-07-25 9:37 ` Nicolas George
2023-07-26 10:37 ` Michael Niedermayer
2023-07-27 13:05 ` Tomas Härdin
2023-07-27 18:36 ` Michael Niedermayer
2023-07-27 18:48 ` Nicolas George
[not found] ` <CC2992B9-B047-4724-8DE5-01C02CBE31FD@cosmin.at>
2023-08-01 19:51 ` Cosmin Stejerean
2023-08-01 20:06 ` Paul B Mahol
2023-08-02 12:46 ` Michael Niedermayer
2023-08-02 13:00 ` Paul B Mahol
2023-08-02 13:01 ` Michael Niedermayer
2023-07-24 8:13 ` Nicolas George
2023-07-24 20:22 ` Tomas Härdin
2023-07-25 9:33 ` Nicolas George
2023-07-25 9:51 ` Kieran Kunhya
2023-07-25 9:56 ` Nicolas George
2023-07-25 10:16 ` Kieran Kunhya
2023-07-25 13:55 ` Nicolas George
2023-07-25 14:37 ` Kieran Kunhya
2023-07-27 17:56 ` Nicolas George
2023-07-28 11:07 ` Kieran Kunhya
2023-07-30 13:04 ` [FFmpeg-devel] What is FFmpeg and what should it be Nicolas George
2023-07-30 17:07 ` Andrey Turkin
2023-07-30 18:29 ` Kieran Kunhya
2023-07-30 18:54 ` Nicolas George
2023-08-01 7:48 ` Rémi Denis-Courmont
2023-07-31 13:56 ` Tomas Härdin
2023-08-03 13:25 ` Nicolas George
2023-08-03 20:50 ` Tomas Härdin
2023-08-02 1:44 ` Vittorio Giovara
2023-08-02 12:55 ` Michael Niedermayer [this message]
2023-08-02 12:59 ` Jean-Baptiste Kempf
2023-08-02 14:12 ` Brad Isbell
2023-08-02 14:19 ` Nicolas George
2023-08-02 14:26 ` Michael Niedermayer
2023-08-02 14:30 ` Nicolas George
[not found] ` <A3B35B92-8333-4637-B4AA-FA9D9750E784@cosmin.at>
2023-08-02 15:46 ` Cosmin Stejerean
2023-08-03 15:40 ` Michael Niedermayer
2023-08-02 14:20 ` Michael Niedermayer
2023-08-02 14:44 ` Jean-Baptiste Kempf
2023-08-03 17:45 ` Michael Niedermayer
2023-08-03 18:24 ` Kieran Kunhya
2023-08-03 19:25 ` Michael Niedermayer
2023-08-03 20:04 ` Kieran Kunhya
2023-08-04 17:09 ` Michael Niedermayer
2023-08-04 17:35 ` Nicolas George
2023-08-04 23:17 ` Kieran Kunhya
2023-08-05 18:55 ` Michael Niedermayer
2023-08-05 19:17 ` Paul B Mahol
2023-08-05 23:32 ` Vittorio Giovara
2023-08-06 8:28 ` Tomas Härdin
2023-08-06 19:53 ` Michael Niedermayer
2023-08-07 15:39 ` Rémi Denis-Courmont
2023-08-08 15:22 ` Michael Niedermayer
2023-08-08 15:37 ` Paul B Mahol
2023-08-08 18:53 ` Rémi Denis-Courmont
2023-08-09 15:59 ` Michael Niedermayer
2023-08-09 16:24 ` Paul B Mahol
2023-08-10 12:39 ` Nicolas George
2023-08-10 14:58 ` Vittorio Giovara
2023-08-12 17:12 ` Michael Niedermayer
2023-08-10 15:01 ` James Almer
2023-08-10 15:43 ` Jean-Baptiste Kempf
2023-08-10 18:39 ` Tomas Härdin
2023-08-03 11:38 ` Tomas Härdin
2023-08-03 13:29 ` Nicolas George
2023-07-25 12:02 ` [FFmpeg-devel] [PATCH 5/6] fftools: avradio support Tomas Härdin
2023-07-22 19:29 ` [FFmpeg-devel] [PATCH 6/6] tools/uncoded_frame: " Michael Niedermayer
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=20230802125521.GG7802@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