From: Derek Buitenhuis <derek.buitenhuis-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Moving edit list handling out of demuxers
Date: Fri, 13 Jun 2025 14:28:24 +0100
Message-ID: <adf3fcb8-9e1c-44e8-a7c3-b42a03cfa5db@gmail.com> (raw)
In-Reply-To: <mailman.3176.1749819125.1384.ffmpeg-devel@ffmpeg.org>
On 6/13/2025 1:51 PM, Kieran Kunhya via ffmpeg-devel wrote:
> Derek did this in 2018:
>
> https://ffmpeg.org/pipermail/ffmpeg-devel/2018-March/227437.html
elenril had some good comments, others were so bad I never sent a v2
because every time I looked at the replies I was demotivated by their
severe asshole-ish-ness.
I think it is a good starting point; this was an issue I have been pointing
out since before the edit list support patch set from youtube even went in,
in the reviews for it, but was overruled as "some support is better than none".
The key point of the set was generic support (e.g. MKV too) and to make
sure it was, as noted by Thomas too, it is applied at presentation level,
after decode.
- Derek
_______________________________________________
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 13:28 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 [this message]
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
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=adf3fcb8-9e1c-44e8-a7c3-b42a03cfa5db@gmail.com \
--to=derek.buitenhuis-at-gmail.com@ffmpeg.org \
--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