From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 3212F4A8B5 for ; Mon, 17 Jun 2024 18:34:51 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 546DE68D77D; Mon, 17 Jun 2024 21:34:48 +0300 (EEST) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 0DDD368D2C8 for ; Mon, 17 Jun 2024 21:34:42 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 31D9A1BF205 for ; Mon, 17 Jun 2024 18:34:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1718649281; 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=ll48+u+o45hNc3nEGrLJyO607Zi24OxMi8+ZshFlSOA=; b=lzL5k7F2N4dQH0Ii1fJ99R0efqBc1+iiulCN4seYIKUSBqF/VhsSG6xShngLdprvu9L/z1 b5tP/NROj5l5nwO1l0Q8IEpCI5+nUlN6h40wBReMUQdZvHDFEGBOkRI3kR7M5HzL5Ql+68 LaRt7LsWranxTsqJ+/vUAy3nvY8sAHA9V2NVVDclIWz6hym0u64bEWNnBnHliBOIJMVt0i 9WGWZAYhlorKRpIvgGjln/meITzAoEkuwvUdkfCsGj1AO2FRt6LEATdSGizg7CyfDgcIim Ai4Fd0SEiESTTucrL5PFIt4jMCY1/guYcj2dcfzfK8ZSzA1MKWOJIzw9VfTQAg== Date: Mon, 17 Jun 2024 20:34:39 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240617183439.GD4991@pb2> References: <20240417135832.GJ6420@pb2> <5b12eaff-f12d-4e61-a886-845d8d00e557@gmail.com> <20240430174253.GP6420@pb2> MIME-Version: 1.0 In-Reply-To: <20240430174253.GP6420@pb2> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [RFC] 5 year plan & Inovation 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="===============5459129523216190536==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5459129523216190536== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="/unnNtmY43mpUSKx" Content-Disposition: inline --/unnNtmY43mpUSKx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 30, 2024 at 07:42:53PM +0200, Michael Niedermayer wrote: > On Mon, Apr 22, 2024 at 01:32:27PM +0200, Lynne wrote: > > Apr 22, 2024, 13:07 by stefasab@gmail.com: > >=20 > > > On date Sunday 2024-04-21 22:12:56 -0300, James Almer wrote: > > > > > >> On 4/17/2024 10:58 AM, Michael Niedermayer wrote: > > >> > > > [...] > > > > > >> A full rewrite of ffserver, using only public API, and with modern s= treaming > > >> in mind. It would give a lot of code in lavf some use. > > >> > > > > > > If this is going to happen, my advice is to use "ffstream" to stick to > > > the ffVERB convention (with the exeption of ffmpeg, which might still > > > be converted to ffconvert with some proper aliasing) and to avoid > > > association with the old incompatible tool . > > > > >=20 > > That's basically what txproto is, only that it also does transcoding > > and filtering. It can accept incoming streams and output them to > > multiple destinations via remux or transcode. It was built as an > > ffmpeg.c with a scriptable interface and with dynamic switching. > > It doesn't do this out of the box, it's something you have to script, > > but that was largely the case that ffserver had. > >=20 > > What is missing is something that ffserver had, which was that > > it was able to express exactly what lavf had in its context on both > > the sender and receiver, for which it needed private APIs. > > AVTransport can largely fill that niche. >=20 > hmm > how would we (assert(people agreeing)) go from what you describe > to a (very easy to use) ffserver "2.0" in something on the ffmpeg.org dow= nload page > ? also if you look at google trends, even today more people search for ffserv= er than txproto. In fact at every point in time more people searched for ffser= ver than txproto. https://trends.google.com/trends/explore?date=3Dall&q=3Dtxproto,ffserver So even though ffserver is dead, removed and unmaintained, it has more users And this comes back to what i said many times. We should use the name FFmpeg, our domain and NOT push every bit of new inovation out into sub projects. We should put a newly developed ffserver into the main ffmpeg git. We should put wasm build support into the main ffmpeg git. We should turn ffplay into a fully competetive player. =2E.. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope --/unnNtmY43mpUSKx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZnCBvAAKCRBhHseHBAsP q6LdAJ9/cEFqOShtmaFaEzhZ8Z1fm8c6IACfblwFHS/2WI2cJjeK4P+GPax3Jgo= =wkrI -----END PGP SIGNATURE----- --/unnNtmY43mpUSKx-- --===============5459129523216190536== 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". --===============5459129523216190536==--