From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id BF2424C08D for ; Fri, 23 May 2025 09:45:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 2192F68DEA0; Fri, 23 May 2025 12:45:23 +0300 (EEST) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 6ED9168CF80 for ; Fri, 23 May 2025 12:45:16 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id BBF0A439F2 for ; Fri, 23 May 2025 09:45:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1747993515; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8JSlVYIqYtiviHR2WHj3qKt3W/u4vyn2DWw52s0KFPs=; b=ek/GMJuT1/VJSecj1DnGsXQnzKoGwCZ7cn7GhHMJYCsx2je3xxMROj6iDwbzqJ36ANif/l cBudBckuVY0lzCUDSnwiI++0RqiPukGo7RALu8Np2Ikf3+kNtwBmziht24Wvq8h3P6kCtK CGHQ7oL77iKBpmGqyoB13GUBcA6sbD/CtNEhd+BIaU86nA8egGsw8T7ea5CtaN6I8wG7m7 IzJ+MrYrhMs9jHZEq5FV2ohvtcvebg6Matk4QfAeLdkhawRxf5TXGZRtClpxQoX6wrXlfO 7hD8iJ4gbhkSTzG/JsQ6Yp8pg2OwNuG+pEgaEJb6Hpe9Ma1O79OTpNgdRSE6iQ== Date: Fri, 23 May 2025 11:45:14 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20250523094514.GW29660@pb2> References: MIME-Version: 1.0 In-Reply-To: X-GND-State: clean X-GND-Score: -70 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtddtgdekhedvucdltddurdegfedvrddttddmucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdeftddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttdejnecuhfhrohhmpefoihgthhgrvghlucfpihgvuggvrhhmrgihvghruceomhhitghhrggvlhesnhhivgguvghrmhgrhigvrhdrtggtqeenucggtffrrghtthgvrhhnpeelkeeggfffiedufeejueffjeduhedttdduledtheevveevtdeiueelhfdtuedtkeenucfkphepgedurdeiiedrieejrdduudefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepgedurdeiiedrieejrdduudefpdhhvghloheplhhotggrlhhhohhsthdpmhgrihhlfhhrohhmpehmihgthhgrvghlsehnihgvuggvrhhmrgihvghrrdgttgdpnhgspghrtghpthhtohepuddprhgtphhtthhopehffhhmphgvghdquggvvhgvlhesfhhfmhhpvghgrdhorhhg X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] STF RaptorQ X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============2874734752989660629==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2874734752989660629== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Lzr+Hbob7NAzMVM+" Content-Disposition: inline --Lzr+Hbob7NAzMVM+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi On Thu, May 22, 2025 at 07:55:40PM -0400, Devin Heitmueller wrote: > On Thu, May 22, 2025 at 7:42=E2=80=AFPM Kieran Kunhya via ffmpeg-devel > 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 > 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. FEC is supperior to ARQ for ARQ, each receiver needs to request the lost packet while for FEC the sender just needs to know or guess how many packets where lost. 1. FEC is lower latency 2. FEC does not suffer from "oops the retrasmit was lost too" 3. if you have 3 receivers one lost packet 5 one packet 8 and one packet 0 with ARQ you need to send 3 individual packets with FEC you CAN broadcast the same 1 packet to all 3 receivers to recover them. Also FEC is VERY widely used, just not where you are looking. =66rom compact disks, to phone networks to inter planetary communication since over 50 years its the standard, voyager in 1970 used FEC already. >=20 > I agree with Kieran that this seems to largely be outside the STF > objectives (i.e. sustainability for open source projects). A new implementation of RIST, SRT, Raptor and so on may fall outside but redesigning the protocol layer in FFmpeg would perfectly fit inside "sustainability for open source projects" When you want A and B and both are connected, you ask for the funding to be for the side that fits inside the guidelines So this STF project could be changed to center on maintaince of the protocol layer instead of a RaptorQ/SRT/RIST implementation i think. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are too smart to engage in politics are punished by being governed by those who are dumber. -- Plato=20 --Lzr+Hbob7NAzMVM+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCaDBDpgAKCRBhHseHBAsP q3ZVAJ9/7Ca04dZs3cA2DY7Rd7Vu8OyIsgCfQ3RtcMh0iwNN6nm5v5M7pHfTQ+E= =Codq -----END PGP SIGNATURE----- --Lzr+Hbob7NAzMVM+-- --===============2874734752989660629== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============2874734752989660629==--