From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Moving edit list handling out of demuxers Date: Wed, 18 Jun 2025 05:55:24 +0200 Message-ID: <20250618035524.GO29660@pb2> (raw) In-Reply-To: <e558d20fa8d8fe3afa24eafa18b20395e209aa8b.camel@haerdin.se> [-- Attachment #1.1: Type: text/plain, Size: 3797 bytes --] Hi Tomas On Tue, Jun 17, 2025 at 11:15:25PM +0200, Tomas Härdin wrote: > fre 2025-06-13 klockan 18:19 +0200 skrev Michael Niedermayer: [...] > > > > > The main issue I see with this is that it risks turning ffmpeg > > > > > into > > > > > an > > > > > NLE tool, > > > > > > > > If ffmpeg could do NLE, that would not be a bad thing > > > > And a full implementation of edit lists may be equivalent to > > > > this. > > > > I think thats a win not a loss > > > > > > Fair enough. So long as I don't have to implement it or think > > > particularly much about it. > > > > it will be needed to think about "if its possible" to implement > > during API design > > > > That said if > > * proper edit list implementation is bascially NLE support > > > > Then not only is it alot of work, it also allows us to attract a new > > group of developers and users > > *We* shouldn't necessarily be attracting them. Libre multimedia is more > than just FFmpeg. It is better to focus NLE efforts on melt. Projects grow or they shrink there is no standing still. Not attracting new developers is madness and would be the end of FFmpeg. We all surely realize we are mostly a bunch of old man, we do need new developers. > We can If we dont have developers or maintainers we can do nothing What you suggest or hint toward to me, in plain english sounds like, drop the ffmpeg command line tool because it would otherwise need to have NLE support. Do a vote about this, if you belive people support a ffmpeg that doesnt support mov/mp4 My way is forward, a streaming server (IF there are people who want to work on it), NLE (IF there are people who want to work on it) anything else multimedia related (IF there are people who want to work on it) If the community chooses not to move forward even though it would be a lower effort to move forward. Then I clearly am in the wrong community. [...] > FFmpeg's architecture is wholly unsuitable for NLE work. That way lies > madness. This becomes apparent when looking at melt. I suggest more > devs take a look at it. Just move toward a full implementation of edit lists, and you have done everything i ask for. If we dont implement full edit list support, then we should not pretend 1. ffmpeg even supports mov or mp4 (and thats the end of ffmpeg.) 2. that this could replace the hacks in the demuxer Again theres no standing still. either FFmpeg grows or it shrinks and if it shrinks it will die. Iam NOT asking anyone to compete with or replace any NLE tool. That may or may not happen as a sideffect. Now technically, for edit list support you need at minimum 1. demuxers exporting metadata, 2. muxers importing it 3. a way to apply a edit list, so mov (with edit list) -> mov (without edit list) works There are 2 cases here, one with a decoder and encoder and one without. the first must always work the 2nd only sometimes and this 2nd one is equivalent to our hacks more or less. Whats optional: 4. export and import edit lists in a json format or something like that, allow the user to make changes 1-4 == basic NLE support, yes theres UI, intermediate formats, caches, transitions and and and, but for basic NLE support 1-4 is whats needed now i probbaly missed something but the technical details where not the point of my mail anyway. also iam wrting this after 5am so probably i missed something or said something dumb :) thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Whats the most studid thing your enemy could do ? Blow himself up Whats the most studid thing you could do ? Give up your rights and freedom because your enemy blew himself up. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
next prev parent reply other threads:[~2025-06-18 3:55 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-13 10:55 Tomas Härdin 2025-06-13 12:51 ` Kieran Kunhya via ffmpeg-devel 2025-06-13 13:28 ` Derek Buitenhuis 2025-06-13 14:34 ` Tomas Härdin 2025-06-13 14:41 ` Derek Buitenhuis 2025-06-13 14:21 ` Michael Niedermayer 2025-06-13 14:53 ` Tomas Härdin 2025-06-13 14:57 ` Gyan Doshi 2025-06-17 20:42 ` Tomas Härdin 2025-06-13 16:19 ` Michael Niedermayer 2025-06-17 21:15 ` Tomas Härdin 2025-06-18 3:55 ` Michael Niedermayer [this message] 2025-06-18 10:02 ` Michael Niedermayer 2025-06-18 10:09 ` Nicolas George 2025-06-18 15:50 ` Tomas Härdin 2025-06-13 16:22 ` Michael Niedermayer 2025-06-13 14:37 ` Gyan Doshi 2025-06-17 21:33 ` Tomas Härdin 2025-06-18 4:15 ` Gyan Doshi 2025-06-18 7:17 ` Nicolas George 2025-06-13 16:57 ` Nicolas George
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250618035524.GO29660@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git