From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 17:59:10 +0200
Message-ID: <20250523155910.GC29660@pb2> (raw)
In-Reply-To: <CAHGibzH6FCdR02iQb13yKGo_RXHqxcCBdkHHcRYDgMWQ55wpzQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1975 bytes --]
Hi Devin
On Fri, May 23, 2025 at 10:57:37AM -0400, Devin Heitmueller wrote:
> On Fri, May 23, 2025 at 5:58 AM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> > Theres also the human element, where people are not machienes that can
> > be placed and told things arbitrary. RaptorQ is "cool", ARQ is boring
> >
> > Some people enjoy working on "cool" things, dont tell them to work on
> > boring things please. Its bad for them, and likely bad for the results.
> >
> > If you find RIST/SRT important, you should work on it, or fund someone
> > to do it or to submit a project idea to STF/GsoC/... and work on it
> > with their funding ...
> >
> > Also IMO if you have someone who wants to do a project that moves FFmpeg
> > forward, be supportive of the effort and try to find a way to make it happen
> > be that inside or outside STF.
> > Arguing against efforts to move to teh cutting edge of technology
> > will do only one thing and thats havig competitors take the space
> > and FFmpeg fall behind
>
> To be clear, I have no desire to discourage developers from working on
> anything that interests them. I've spoken to Lynne about her txproto
> work, and while I can't offer any guidance due to the NDA with my
> employer, I admire her initiative and really hope that research turns
> into something useful.
>
> This discussion though really started about what the scope of work is
> that can be funded by STF. My understanding is that STF intends for
> the funds to be used for maintenance and work that contributes toward
> project sustainability. At least for me personally, I am not
> confident I could argue that the RaptorQ work proposed falls within
> that definition.
yes, as it was proposed on the wiki and as i remember STF, i agree.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No great genius has ever existed without some touch of madness. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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 15:59 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 [this message]
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=20250523155910.GC29660@pb2 \
--to=michael@niedermayer.cc \
--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