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 71DA74A8E9 for ; Tue, 23 Apr 2024 00:21:01 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id BEFE868D353; Tue, 23 Apr 2024 03:20:59 +0300 (EEST) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 66FFA68D0F6 for ; Tue, 23 Apr 2024 03:20:53 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 7F66940004 for ; Tue, 23 Apr 2024 00:20:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1713831652; 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=2W8NyLbqAxFM5Z49sm/BCclkklymQ5MWacNGRrOYDmI=; b=UNmXBpq5k+GTfnxZFiqPjkDzJAVhHJN0Izqe4m4egWsjzfX78mAGaDZ77WFluEbGD2TaV2 WpfaXKlu8rhKax2zD2hJ5SD+e0TvqBK014I/M3tS0LGgq2ZhtzpdxymsLtyU8CkFjpdRPg jhrPXgZAioO/ogzWxzZcKu9w8AE0VXcFTT8S/fXVcHfpEWJltFfyzNJ3aC2N7dnj8C6sU0 fEa8h23X+VAv5wazYlpLQBDUNta/YzBgjzitdmbEjrecIEFBsMfUm+bYojvDUvdyA+C8JZ 4jI68y8lz3YbU5txgsHmlzprT6VF4hnZscV2Jjt2k1ShinmjeOS4Ics+LvglQA== Date: Tue, 23 Apr 2024 02:20:51 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240423002051.GG6420@pb2> References: <20240417135832.GJ6420@pb2> MIME-Version: 1.0 In-Reply-To: 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="===============4106280714600232908==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============4106280714600232908== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bwUCDsBYWWe0GlFX" Content-Disposition: inline --bwUCDsBYWWe0GlFX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 18, 2024 at 10:46:35AM +0200, Stefano Sabatini wrote: > On date Wednesday 2024-04-17 15:58:32 +0200, Michael Niedermayer wrote: > > Hi all > >=20 > > The pace of inovation in FFmpeg has been slowing down. > > Most work is concentarted nowadays on code refactoring, and adding > > support for new codecs and formats. > >=20 > > Should we > > * make a list of longer term goals > > * vote on them > > * and then together work towards implementing them > > ? > >=20 > > (The idea here is to increase the success of larger efforts > > than adding codecs and refactoring code) > > It would then also not be possible for individuals to object > > to a previously agreed goal. > > And it would add ideas for which we can try to get funding/grants for > >=20 > > (larger scale changes need consensus first that we as a whole want > > them before we would be able to ask for funding/grants for them) > >=20 > > Some ideas and why they would help FFmpeg: > >=20 > [...] > > * client side / in browser support > > (expand towards webapps, webpages using ffmpeg client side in the b= rowser) > > bring in more users and developers, and it will be costly for us > > if we let others take this area as its important and significant >=20 > There are already several projects on github, the most prominent one: > https://github.com/ffmpegwasm/ffmpeg.wasm/ >=20 > In general it would be useful to provide libav* bindings to other > languages, for example: > https://github.com/PyAV-Org/PyAV > https://github.com/zmwangx/rust-ffmpeg >=20 > Not sure these should be really moved to FFmpeg though. =46rom a user PoV it would be nice if there was a official python, rust and wasm binding It also would draw in more developers and users to FFmpeg. test coverage might also improve I think the 2 questions are. 1. is there a binding for some language that wants to become the official FFmpeg binding for that language ? 2. does the FFmpeg community want that too ? thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Old school: Use the lowest level language in which you can solve the problem conveniently. New school: Use the highest level language in which the latest supercomputer can solve the problem without the user falling asleep waiting. --bwUCDsBYWWe0GlFX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZib+3wAKCRBhHseHBAsP q0cqAJ923PVAboi1+DeFZ8FzCH4qQVoiIACeMnp/lMdBIacHpHs4klQRb6uwUds= =oSvd -----END PGP SIGNATURE----- --bwUCDsBYWWe0GlFX-- --===============4106280714600232908== 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". --===============4106280714600232908==--