From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Moving edit list handling out of demuxers
Date: Fri, 13 Jun 2025 20:07:03 +0530
Message-ID: <edda6f95-230a-4405-be85-6800430fe78c@gyani.pro> (raw)
In-Reply-To: <19ff1126f1e93cdb4fdcf50fee499c02c5e85ea7.camel@haerdin.se>
On 2025-06-13 04:25 pm, Tomas Härdin wrote:
> The present level of
> edit list support could be reimplemented by just fiddling with the -ss
> and -t options. That is, the ffmpeg CLI could automatically derive -ss
> and -t from the edit list extracted by lavf.
In mov.c, edit lists are per-track and can compose their edited tracks
differently. So if the stream index/tables are to be no longer
reconstituted within mov,c, -ss and -t may not return synchronized
packets (as per the intended elst) from all streams.
Regards,
Gyan
_______________________________________________
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:37 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
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 [this message]
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=edda6f95-230a-4405-be85-6800430fe78c@gyani.pro \
--to=ffmpeg@gyani.pro \
--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