Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: don't abort on duplicate Mastering Display Metadata boxes
Date: Tue, 26 Mar 2024 21:16:44 -0300
Message-ID: <8dad9db1-6b77-4a3b-8918-fae08577adbe@gmail.com> (raw)
In-Reply-To: <GV1P250MB0737672E80BD727AE2183AA78F342@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>

On 3/26/2024 9:13 PM, Andreas Rheinhardt wrote:
> James Almer:
>> The VP9 spec defines a SmDm box for this information, and the ISOBMFF spec defines a
>> mdvc one. If both are present, just ignore one of them.
>> This is in line with clli and CoLL boxes.
>>
>> Fixes ticket #10711.
>>
>> Signed-off-by: James Almer <jamrial@gmail.com>
>> ---
>>   libavformat/mov.c | 13 ++++++++++---
>>   1 file changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/libavformat/mov.c b/libavformat/mov.c
>> index e7aa8d1833..5463f36770 100644
>> --- a/libavformat/mov.c
>> +++ b/libavformat/mov.c
>> @@ -6140,8 +6140,10 @@ static int mov_read_smdm(MOVContext *c, AVIOContext *pb, MOVAtom atom)
>>           av_log(c->fc, AV_LOG_WARNING, "Unsupported Mastering Display Metadata box version %d\n", version);
>>           return 0;
>>       }
>> -    if (sc->mastering)
>> -        return AVERROR_INVALIDDATA;
>> +    if (sc->mastering) {
>> +        av_log(c->fc, AV_LOG_WARNING, "Ignoring duplicate Mastering Display Metadata\n");
> 
> If this is expected (and maybe even encouraged/required by some spec),
> then why is this a warning?

I don't know if it's expected. I'd expect VP9 streams would not come 
with mdvc and CoLL boxes at all, but apparently Youtube ones now do 
(Guess they are phasing out webm-dash and so now VP9 is served on mp4). 
I just copied the existing behavior from clli and CoLL.

> 
>> +        return 0;
>> +    }
>>   
>>       avio_skip(pb, 3); /* flags */
>>   
>> @@ -6178,11 +6180,16 @@ static int mov_read_mdcv(MOVContext *c, AVIOContext *pb, MOVAtom atom)
>>   
>>       sc = c->fc->streams[c->fc->nb_streams - 1]->priv_data;
>>   
>> -    if (atom.size < 24 || sc->mastering) {
>> +    if (atom.size < 24) {
>>           av_log(c->fc, AV_LOG_ERROR, "Invalid Mastering Display Color Volume box\n");
>>           return AVERROR_INVALIDDATA;
>>       }
>>   
>> +    if (sc->mastering) {
>> +        av_log(c->fc, AV_LOG_WARNING, "Ignoring duplicate Mastering Display Color Volume\n");
>> +        return 0;
>> +    }
>> +
>>       sc->mastering = av_mastering_display_metadata_alloc();
>>       if (!sc->mastering)
>>           return AVERROR(ENOMEM);
> 
> _______________________________________________
> 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".
_______________________________________________
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".

      reply	other threads:[~2024-03-27  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  0:11 James Almer
2024-03-27  0:13 ` Andreas Rheinhardt
2024-03-27  0:16   ` James Almer [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=8dad9db1-6b77-4a3b-8918-fae08577adbe@gmail.com \
    --to=jamrial@gmail.com \
    --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