Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Tristan Matthews via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Tristan Matthews <httamt@protonmail.com>,
	Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 16:24:33 +0000
Message-ID: <0NdPzMfAQkqilJLq5gKzcUfnYFzP7-Om_lA6-2WxeqisSgrEQEbBepYTcWN8qjOLZBpZdilnuytKlNjNV_vzlzGZUJfRhhFELZQgVC0eW6w=@protonmail.com> (raw)
In-Reply-To: <CABGuwEkSn=hP+ozHfbEPEGq-DSnrX+8RotA9wJhNCWHqeqGhzQ@mail.gmail.com>

Hi,

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

I just wanted to drop a giant +1 that event loop support in FFmpeg would be a big win (and unblock a lot of other improvements for e.g. FFmpeg's network stack IMO) and should seriously be considered for an STF project if someone has the wherewithal. It's obviously a pretty large undertaking.

Best,
Tristan
_______________________________________________
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 16:24 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 [this message]
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='0NdPzMfAQkqilJLq5gKzcUfnYFzP7-Om_lA6-2WxeqisSgrEQEbBepYTcWN8qjOLZBpZdilnuytKlNjNV_vzlzGZUJfRhhFELZQgVC0eW6w=@protonmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=httamt@protonmail.com \
    --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