Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 16:45:53 +0100
Message-ID: <CABGuwEnJ8d8ZugOyB+TPA5mzoapq=mRoodPeCeDf-JUunw2PDg@mail.gmail.com> (raw)
In-Reply-To: <CABGuwE==VfV+7aPadx-y9d-4uPPN-CWACSfQ9ZL6Fj7O7P9-Sg@mail.gmail.com>

On Fri, May 23, 2025 at 4:00 PM Kieran Kunhya <kieran618@googlemail.com> wrote:
>
> On Fri, May 23, 2025 at 3:50 PM Devin Heitmueller
> <devin.heitmueller@ltnglobal.com> wrote:
> >
> > Hello Michael,
> >
> > On Fri, May 23, 2025 at 5:45 AM Michael Niedermayer
> > <michael@niedermayer.cc> wrote:
> > > On Thu, May 22, 2025 at 07:55:40PM -0400, Devin Heitmueller wrote:
> > > > On Thu, May 22, 2025 at 7:42 PM Kieran Kunhya via ffmpeg-devel
> > > > <ffmpeg-devel@ffmpeg.org> wrote:
> > > > > I wanted to put on the record that adding RaptorQ to FFmpeg isn't
> > > > > maintenance of FFmpeg.
> > >
> > > i agree adding RaptorQ itself is probably not maintenance
> >
> > Ok, so that much everybody seems to agree on.  Great.
> >
> > > > > It's adding an obscure FEC protocol to FFmpeg,
> > >
> > > tornado and raptor codes are not obscure.
> > > and FFmpeg supports hundreads of much more obscure things
> >
> > Sure, no disagreement there.  While I've personally never used any of
> > the codecs that support video games from the 1990's, I don't really
> > have any problem with them being in ffmpeg.  That said, in my opinion,
> > I doubt STF would really think it's a good use of their funds to add
> > support for new codecs for such games.
> >
> > > > I'm not sure I've seen any commercial gear that does RaptorQ for FEC,
> > > > so it's not clear what the use cases are if the goal is
> > > > interoperability.
> > >
> > > its IMHO for communication between tools that on both sides
> > > use our software
> > >
> > > If no commercial gear uses a reliable FEC system all teh better
> > > for us
> >
> > Wow, that's quite a leap to suggest that because there aren't open
> > standards using RaptorQ that there isn't commercial video transmission
> > gear out there that doesn't do a good job with FEC.
> >
> > > > If somebody really wants to be paid to work on
> > > > reliable transport protocols, the time would be better spent improving
> > > > the RIST or SRT integration, which is where most of the industry is
> > > > putting their energy.
> > >
> > > FEC is supperior to ARQ
> > > for ARQ, each receiver needs to request the lost packet
> > > while for FEC the sender just needs to know or guess how many packets
> > > where lost.
> > > 1. FEC is lower latency

This isn't true. You need a large FEC matrix to handle burst packet
loss and you have to buffer for the duration of this matrix.
At low bitrates this duration can be really long. (100 packets at
1mbit/s is already roughly a second).

Regards,
Kieran Kunhya
_______________________________________________
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:[~2025-05-23 15:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 23:42 Kieran Kunhya via ffmpeg-devel
2025-05-22 23:55 ` Devin Heitmueller
2025-05-23  3:48   ` Lynne
2025-05-23 14:37     ` Devin Heitmueller
2025-05-23  9:45   ` Michael Niedermayer
2025-05-23  9:58     ` Michael Niedermayer
2025-05-23 11:25       ` Kieran Kunhya via ffmpeg-devel
2025-05-23 14:57       ` Devin Heitmueller
2025-05-23 15:59         ` Michael Niedermayer
2025-05-23 11:32     ` Kieran Kunhya via ffmpeg-devel
2025-05-23 16:24       ` Tristan Matthews via ffmpeg-devel
2025-05-23 14:50     ` Devin Heitmueller
2025-05-23 15:00       ` Kieran Kunhya via ffmpeg-devel
2025-05-23 15:45         ` Kieran Kunhya via ffmpeg-devel [this message]
2025-05-23 20:35           ` Michael Niedermayer
2025-05-23 21:45             ` Kieran Kunhya via ffmpeg-devel
2025-05-23 16:04       ` Michael Niedermayer
2025-05-23  3:44 ` Lynne
2025-05-23  6:50   ` Kieran Kunhya via ffmpeg-devel
2025-05-23  9:53     ` Lynne
2025-05-23  7:51   ` Kieran Kunhya via ffmpeg-devel
2025-05-23 11:33     ` Michael Niedermayer
2025-05-23 12:13       ` Kieran Kunhya via ffmpeg-devel
2025-05-23 14:43         ` Michael Niedermayer
2025-05-24 16:39         ` [FFmpeg-devel] Previous trac server hosting Was: " Michael Niedermayer
2025-05-24 17:48           ` Kieran Kunhya via ffmpeg-devel
2025-06-02  4:29             ` Baptiste Coudurier
2025-05-23 14:58       ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel

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='CABGuwEnJ8d8ZugOyB+TPA5mzoapq=mRoodPeCeDf-JUunw2PDg@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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