2017-12-01 20:08 GMT+01:00 Neil Birkbeck <neil.birkb...@gmail.com>:
> On Thu, Nov 30, 2017 at 9:52 AM, Michael Niedermayer wrote:

>> > For that sample, I feel like it may be incorrectly tagged as pc/full.
>> is it stored in the file or taken from:
>> ff_generate_avci_extradata()
>> maybe theres a bug in the AVCIntra handling
> It seems avci100_1080i_extradata may be the one that is signalling full
> range for the AVCI100.mov sample. I tested changing the range flag:
> -        0x3c, 0x60, 0x20, 0x20, 0x28, 0x00, 0x00, 0x03,
> +        0x3c, 0x20, 0x20, 0x20, 0x28, 0x00, 0x00, 0x03,

If you believe it is safe (or a bug), please change it.

> There is an unused ACLR atom in the mov that also appears to
> signal full range (parsing of that atom is skipped for h264)

I believe the extra-data should not be overwritten.

Carl Eugen
ffmpeg-devel mailing list

Reply via email to