From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] mov: Reduce the verbosity of the warning about fragmented MP4 vs advanced edit lists
Date: Tue, 31 Jan 2023 14:37:59 +0200 (EET)
Message-ID: <15556b8-a239-5dda-954c-9d46e8e15e@martin.st> (raw)
In-Reply-To: <2d0fe4ab-e8cd-7e80-9442-a79e81b1acd9@gmail.com>
On Mon, 23 Jan 2023, Derek Buitenhuis wrote:
> On 1/17/2023 9:31 AM, Martin Storsjö wrote:
>> Only warn if the advanced_editlist option is enabled (it is enabled
>> by default though) so we don't print one warning for each track, and
>> demote the warning to AV_LOG_LEVEL_VERBOSE; this message does get
>> generated whenever parsing a fragmented MP4 file, regardless of
>> whether the file actually uses multiple edits or not.
>>
>> Later when parsing the mov structures, the demuxer does warn if
>> the file did contain multiple edits which would require the
>> advanced_editlist option enabled for decoding correctly.
>>
>> Adjust the warning message for the case when the file seemed like it
>> actually would have needed handling of advanced edit lists, to
>> reflect the fact that it doesn't help to try set the option as
>> it has been automatically disabled.
>> ---
>> libavformat/isom.h | 1 +
>> libavformat/mov.c | 20 ++++++++++++++------
>> 2 files changed, 15 insertions(+), 6 deletions(-)
>
> LGTM.
Pushed now, thanks!
// Martin
_______________________________________________
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".
prev parent reply other threads:[~2023-01-31 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 9:31 Martin Storsjö
2023-01-23 13:59 ` Derek Buitenhuis
2023-01-31 12:37 ` Martin Storsjö [this message]
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=15556b8-a239-5dda-954c-9d46e8e15e@martin.st \
--to=martin@martin.st \
--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