Re: [FFmpeg-devel] STF RaptorQ

From: Devin Heitmueller <devin.heitmueller@ltnglobal.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 10:37:37 -0400
Message-ID: <CAHGibzG5zUa8LroC7_q7TOo9OyVrrE6jFPUj_FO+AnrFd_+gKw@mail.gmail.com> (raw)
In-Reply-To: <6660de1f-601c-40f9-9827-8cfaa4d01ca0@lynne.ee>

Hello Lynne,

On Thu, May 22, 2025 at 11:48 PM Lynne <dev@lynne.ee> wrote:
> > 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.

Yes, I am aware of the difference between an algorithm and a protocol,
thanks.  My (perhaps incorrect) assumption was that you also intended
to implement the RaptorQ over RTP protocol spec (RFC 6682), since
algorithms themselves aren't very useful without some form of working
implementation.  If your intent is to implement just the algorithm
without any protocol that demonstrates it, then my concerns are even
greater regarding whether this is a good use of STF funds.

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

Yeah, I suspect much of this comes down to a discussion on what STF
expects/requires funds to be used for.

Devin

-- 
Devin Heitmueller, Senior Software Engineer
LTN Global Communications
o: +1 (301) 363-1001
w: https://ltnglobal.com  e: devin.heitmueller@ltnglobal.com
_______________________________________________
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".