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 1CDE849FF9 for ; Wed, 17 Apr 2024 14:22:12 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7A90168D2D1; Wed, 17 Apr 2024 17:22:10 +0300 (EEST) Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E970B68CF80 for ; Wed, 17 Apr 2024 17:22:03 +0300 (EEST) Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w4.tutanota.de (Postfix) with ESMTP id 8516B1060277 for ; Wed, 17 Apr 2024 14:22:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1713363723; s=s1; d=lynne.ee; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=8mVTmeul6Np0HW61zGGYjivTPsx3I5AH6SQInCVc7Zc=; b=xSWwCKDtYL3SkfBQEZsY4G7kAeYhs19mL9Bvez1ca1h88GpmLADw31eCmtOd49Td RoCrBzK3Q6kN4VptjZ5bCjS7xPnlTFiWt4Mn/CS0XET6LV2AvYCJvo+2K4p2jr3fESb L21tA2bqnMJFaAvFtJIyblJfvR//63URL5FZ/7qe+etMiNIqRZRjtTe6lU+IJSKJnrT vFOoArJUECveh1t+c45C2ho5pBl7+ErKMvawzjibRgM+hOiizixaTtD8wxeQpFfr7Ux QFR4zcpe7tP4z+tYbdEKMPYqa4TYD2v1+DSg1MV9uiKqaS281gXxxHF1SDv+KfaI8RP uqTbzxYtew== Date: Wed, 17 Apr 2024 16:22:03 +0200 (CEST) From: Lynne To: FFmpeg development discussions and patches Message-ID: In-Reply-To: <20240417135832.GJ6420@pb2> References: <20240417135832.GJ6420@pb2> MIME-Version: 1.0 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: Apr 17, 2024, 15:58 by michael@niedermayer.cc: > 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) > Just no. > * ffchat > (expand into realtime chat / zoom) this would > bring in more users and developers, and we basically have almost > Better leave that for others. There's an infinite amount of discord clones already. > all parts for it already but some people where against it > * 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 > Maybe. Some WASM-based converter would be helpful. Though it may put us on fire, as we'd be distributing binaries of our code which may cause issues with "rights holders". > * 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 > These take enormous amounts of compute power to train, vast amounts of good high-quality data, and at the end, you'd have something as lasting as wet paper, because a competitor is literally weeks away, and they beat us with inferior methods by simply having vastly more compute than we do. > * [your idea here] > We keep doing what we're doing. It's what we're good at. _______________________________________________ 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".