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 7ADF14ACA7 for ; Tue, 18 Jun 2024 10:45:02 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E900468D77D; Tue, 18 Jun 2024 13:44: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 D99CF68D706 for ; Tue, 18 Jun 2024 13:44:52 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 3A9A54000B for ; Tue, 18 Jun 2024 10:44:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1718707492; 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=wJRuZVwd2WONf/FiFfQxQdie5Fun/S0HhKfPolxbsoQ=; b=nNMzJT50QmhMOCi6FE/e8HUKKDIByjE2mBn/U2YFHSVti0NzrG3F0rT3583YzU6WdsB+Iy /XBxk3W1qQ4ZfA8fjmZR+0tzgumggrX4Nx+5ShLdBs8GRKkS7NVvUaFoUkVpXh+OFn/6iQ R78rmnszDrdh/1hkGp5ZVgnoLAkbkAdUvEfAcY6MHz5bFEDS/vUHNDTtMy3UMD0IjOmfN7 HeZIV2ka5l+DzUWl+LyOBjLMC+JhG8gpKRNG6U/+jgbmnNjEd84EJz07WGIsViAAhXqKbO xIlQSo04jca5iYJLaqnvSs+EvS2hzXc5QThcl9ccByhm0OicnmAvS/1zJ43OXw== Date: Tue, 18 Jun 2024 12:44:51 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240618104451.GG4991@pb2> References: <20240417135832.GJ6420@pb2> <5b12eaff-f12d-4e61-a886-845d8d00e557@gmail.com> <20240430174253.GP6420@pb2> <20240617183439.GD4991@pb2> <3281348E-8694-4381-A7B4-F5822EC37239@remlab.net> MIME-Version: 1.0 In-Reply-To: <3281348E-8694-4381-A7B4-F5822EC37239@remlab.net> 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="===============4976412568447519053==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============4976412568447519053== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="S5HS5MvDw4DmbRmb" Content-Disposition: inline --S5HS5MvDw4DmbRmb Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 17, 2024 at 11:02:31PM +0200, R=E9mi Denis-Courmont wrote: >=20 >=20 > Le 17 juin 2024 20:34:39 GMT+02:00, Michael Niedermayer a =E9crit=A0: [...] > >We should turn ffplay into a fully competetive player. >=20 > No. First there is no such thing as "a fully competitive player". You wou= ld need at least one mobile player, one smart TV and STB player and one des= ktop player, on top of the existing crude CLI player. And that's if you man= age Android and iOS, mac and Windows, together. Otherwise it's even more pl= ayers. Maybe "fully competetive player" was a bad term I think ffplay is quite close to being fully competetive. I do use it 95% o= f the time and iam not feeling like iam missing something >=20 > Then you would need each of them to have features that FFmpeg doesn't hav= e as a back-end, notably media library management. we support various playlists. That could be extended but i agree some kind of playlist display and editing / (media library mana= gement seems a fancy term for that) is important for some users >=20 > That's a lot of work, mostly GUI work. No offence but you and most other = devs here don't strike me as GUI devs. VLC is pretty much dead now for unde= r-estimating how hard it was to rewrite the desktop UI. How will you find a= nd keep motivated the developers for all that UI work? They are not going t= o manifest spontaneously, even less so in a community with a deservedly hor= rible reputation as FFmpeg's. I have written basic GUIs in some toy projects long prior ffmpeg, I remember having had a multi level menu and a animated raytraced mouse cursor in one = ;) it was just a few lines of C + ASM code but looked quite good for the time. And in the software defined radio code i had written there was a vissualiza= tion with the decoded channel/artist/song names drawn on the spectrum waterfall plot = thingy. If one wants to write a GUI with 10 differnt high level APIs, its going to = be alot of code and hard to maintain (keeping up with each platforms / lib GUI APIs an= d all the bugs) I see nothing wrong with making it easy for people to do this if one wants = to maintain a specific GUI for a specific platform. But supporting 10 GUI libs wasnt what i had in mind Instead really we need just one GUI, and 2 variants (one for touchscreens a= nd one for non touchscreens) implementing this with nothing but ANSI C and a framebuffer / 2d array of p= ixels is very doable. It can be made to look quite good, it depends on no APIs, and its not alot = of code. One can of course also instead use some portable GUI library, i think whoev= er works on such GUI would decide how to do it. >=20 > Unless you just won the Euromillion or something like that, this is not g= oing to happen. No ifs or buts about it. I think we where thinking of different things thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Republics decline into democracies and democracies degenerate into despotisms. -- Aristotle --S5HS5MvDw4DmbRmb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZnFlHwAKCRBhHseHBAsP q1UIAJ9GiWSbhBrf5NMaUx7sUBDumzP7+QCbBIli/K+b6Xdg4wnxx+et3q1TzqI= =hfm2 -----END PGP SIGNATURE----- --S5HS5MvDw4DmbRmb-- --===============4976412568447519053== 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". --===============4976412568447519053==--