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-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 12:48:18 +0900
Message-ID: <6660de1f-601c-40f9-9827-8cfaa4d01ca0@lynne.ee> (raw)
In-Reply-To: <CAHGibzGhTePabJygyVHmHwMSwKzVoEg5QrizDwye1q21BJBRtA@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1626 bytes --]

On 23/05/2025 08:55, 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.
>>
>> It's adding an obscure FEC protocol to FFmpeg, which is not going to be
>> implemented well without an event loop anyway.
>>
>> I do not think it's a suitable STF project.
> 
> I see the task on the TRAC page for STF 2025, and while intellectually
> interesting to a nerd like me who does lots of work with reliable
> protocols, I'm not confident this particular protocol makes much sense
> to work on, especially for 24,000 EUR.

It's not a protocol.

> 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.  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.

Again, it's not a protocol. It's an FEC algorithm. No current mainstream 
protocol specifies using it. It will take decades, at least, and it 
definitely cannot fit into existing protocols.

Custom closed-source video transmission protocols are using it.
But, I do believe it's the future for open-source protocols too.
> I agree with Kieran that this seems to largely be outside the STF
> objectives (i.e. sustainability for open source projects).Like I mentioned, I believe the STF is not maintenance-only, or so I gather.

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 637 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 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".

  reply	other threads:[~2025-05-23  3:48 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 [this message]
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
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=6660de1f-601c-40f9-9827-8cfaa4d01ca0@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