From: Lynne <dev@lynne.ee> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] STF RaptorQ Date: Fri, 23 May 2025 12:44:15 +0900 Message-ID: <760c7e13-eca2-43b0-9cee-2baf6908bea0@lynne.ee> (raw) In-Reply-To: <CABGuwEn=eGSUvacTyzamxbdeoWgLMr=ZWmyF7ze4QoQ6egbPUA@mail.gmail.com> [-- Attachment #1.1.1.1: Type: text/plain, Size: 1223 bytes --] On 23/05/2025 08:42, Kieran Kunhya via ffmpeg-devel wrote: > Hello, > > I wanted to put on the record that adding RaptorQ to FFmpeg isn't > maintenance of FFmpeg. It isn't -- it's research. > It's adding an obscure FEC protocol to FFmpeg, which is not going to be > implemented well without an event loop anyway. You're mixing up FEC implementation details that don't matter for a library. It works much like a decoder - you put N blocks of Y bytes data in, and you get X blocks of Z byes out. > I do not think it's a suitable STF project. STF is not maintenance-only from what I understand, but also for innovation, in this case, research. I have no strong opinions on including this into STF. It's just work I'm interested in doing, which is currently obscure, but that's because it's still young and recently standardized. It will likely be used in future multimedia work, or so I'd like to think. I'd like to ask for you to judge this without prejudice, however. When we spoke on IRC, you had (and still have, in the case of the event loop point), inaccurate understanding of the algorithm, and resorted to asking very technical questions about a recent algorithm to AI chatbots. [-- 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".
next prev parent reply other threads:[~2025-05-23 3:44 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 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 [this message] 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=760c7e13-eca2-43b0-9cee-2baf6908bea0@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