From: "Tomas Härdin" <git@haerdin.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Moving edit list handling out of demuxers Date: Fri, 13 Jun 2025 16:53:14 +0200 Message-ID: <4b2e369b5c72b6b9933acbb1af3158c4cce6e36d.camel@haerdin.se> (raw) In-Reply-To: <20250613142118.GC29660@pb2> fre 2025-06-13 klockan 16:21 +0200 skrev Michael Niedermayer: > > 3) remove edit list hacks from all demuxers, especially mov.c > > +1 (with ABI +2 bump) I'm not sure why a (major?) bump would be necessary. Are removal of options a major bump, not a minor one? Either way, we could make the options ffmpeg.c ones rather than mov.c ones. There's going to be pain either way, partly because doing this in the demuxer was the wrong thing to do in the first place. Another case of "oh let's just do a quick and dirty thing" coming back to bite us. Come to think of this, perhaps hiding this behind a major bump is not such a bad idea. That allows making more sweeping changes, including behavioral ones. > > 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. > > I haven't sketched out any API yet, but it would probably closely > > mirror how elst works in MOV. Care should be taken that MXF > > operational > > pattern 3a can also fit into this API. Possibly even OP3c. > > > > Thoughts? > > it would be cool if someone implemented this, its not trivial as all > sides need to support it. demuxer, muxer, player, ffmpeg We don't need it everywhere immediately. But yeah, it's a lot. We probably need a layer above lavf at some point. libavpresentation? Probably with a cache. That's what libmlt does. It's also why I'm skeptical of going too far with this, because that's dev time not spent on libmlt. I probably need to double-check that I can spend the time to implement this on the demuxer side, and possibly in fftools, before I commit to it. This being a blocker for getting segmented indexes working and upstreamed might help. I'm assuming complete removal of elst support is out of the question. For now I'll probably dummy out elst support and the associated tests just to make progress on segmented indexes. /Tomas _______________________________________________ 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-13 14:53 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 [this message] 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 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=4b2e369b5c72b6b9933acbb1af3158c4cce6e36d.camel@haerdin.se \ --to=git@haerdin.se \ --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