On Fri, 23 May 2025, 10:45 Michael Niedermayer, <mich...@niedermayer.cc> wrote:
> Hi > > 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 > > > > > > > > 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 > > > [...] > > > 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 > But Lynne is insisting it's not a protocol. The work would just be the low level RaptorQ algorithm. UDP based retransmit/FEC protocols are essentially impossible to develop well without an event loop / timers. You can look at libsrt and librist of examples of how trying to reinvent an event loop in threads and creating lots of bugs in the process as each lib struggles to synchronise a complex state machine between threads. Adding event loop support to FFmpeg would be a great STF project. 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-requ...@ffmpeg.org with subject "unsubscribe".
