Re: [FFmpeg-devel] What is FFmpeg and what should it be

From: Kieran Kunhya <kieran618@googlemail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] What is FFmpeg and what should it be
Date: Sun, 30 Jul 2023 19:29:09 +0100
Message-ID: <CABGuwEn-3KqGUiLtaW80JCAkOh3562K+v-G6ri4-adoGYVACvA@mail.gmail.com> (raw)
In-Reply-To: <CAA7-ZoquufTyNCc5sZxBinXCNa6v3LCbc6+TWsDYoHs7LriR4Q@mail.gmail.com>

On Sun, Jul 30, 2023 at 6:07 PM Andrey Turkin <andrey.turkin@gmail.com> wrote:
>
> вс, 30 июл. 2023 г. в 16:04, Nicolas George <george@nsup.org>:
>
> > 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.
> >
>
> There is a good reason to have some part of TCP implemented in FFmpeg
> though. It would be _extremely_ useful to be able to read and replay pcap
> dumps of an RTP stream, or an HLS or DASH stream, or whichever else
> multi-connection streams are there.

I plan to write a more detailed response to Nicolas' email. However,
this response is superb because it immediately points out the flaw in
the arguments. Users will not tolerate "incomplete" features, they
will always want their edge case (packet capture replay) to work. This
is Open Source, there are no product managers and roadmaps to
constrain user requests so we have to decide as a community what is in
scope and what is not.

Kieran
_______________________________________________
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".