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 5D3D54A8BC for ; Thu, 18 Apr 2024 14:02:17 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id ADFC768D292; Thu, 18 Apr 2024 17:02:14 +0300 (EEST) Received: from haasn.dev (haasn.dev [78.46.187.166]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 4E55268D063 for ; Thu, 18 Apr 2024 17:02:08 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=haasn.xyz; s=mail; t=1713448928; bh=OXAslNlZtzfsc67cP3AqXEf2XPrH+DwANSbLJHSyUBw=; h=Date:From:To:Subject:In-Reply-To:References:From; b=mqRoUvFo60f+dnH+8Cv6RBVPEFRTjaU91mNi3Sd+i/P3NVKIvcbCJwer4RznnuV/O 98NeSD/xCasxCoyDy4aIDsL8DnehiuSdR0mBAuoc9GimrLocXdsiM33ZP0TeFYGT8a 9KcmRQhjSDSMLbHQlkKbbINsY/aRhl99kbxoB0lw= Received: from haasn.dev (unknown [10.30.0.2]) by haasn.dev (Postfix) with ESMTP id 0A66E42385 for ; Thu, 18 Apr 2024 16:02:08 +0200 (CEST) Date: Thu, 18 Apr 2024 16:02:07 +0200 Message-ID: <20240418160207.GB45500@haasn.xyz> From: Niklas Haas To: FFmpeg development discussions and patches In-Reply-To: <20240417135832.GJ6420@pb2> References: <20240417135832.GJ6420@pb2> MIME-Version: 1.0 Content-Disposition: inline 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Wed, 17 Apr 2024 15:58:32 +0200 Michael Niedermayer wrote: > Hi all > > 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. > > Should we > * make a list of longer term goals > * vote on them > * and then together work towards implementing them > ? > > (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 > > (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) > > Some ideas and why they would help FFmpeg: > > * Switch to a plugin architecture > (Increase the number of developers willing to contribute and reduce > friction as the team and community grows) This would almost surely hurt productivity as it will require exposing, versioning, documenting and maintaining a vast number of internal APIs which we are currently at the liberty of modifying freely. > * ffchat > (expand into realtime chat / zoom) this would > bring in more users and developers, and we basically have almost > all parts for it already but some people where against it This seems like a user application on top of FFmpeg, not something that should be part of FFmpeg core. Can you explain what modifications in FFmpeg would be necessary for something like this? > * client side / in browser support > (expand towards webapps, webpages using ffmpeg client side in the browser) > 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 I don't understand this point - don't all major browsers already vendor FFmpeg for decoding? > * AI / neural network filters and codecs > The future seems to be AI based. Future Filters and Codecs will use > neural networks. FFmpeg can be at the forefront, developing these We already have TensorFlow support, no? (vf_sr etc.) What more is needed? > * [your idea here] > > thx > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > It is what and why we do it that matters, not just one of them. > _______________________________________________ > 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". _______________________________________________ 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".