Some other containers for AV1, in particular ivf, use a different
capitalization of the AV1 codec tag. When these files are remuxed
into mp4, they result in invalid files.
This patch normalizes the tag by forcing its lookup in
ff_codec_movvideo_tags.
---
libavformat/movenc.c | 3 ++-
1 file chang
On 08/13/2018 03:30 PM, Carl Eugen Hoyos wrote:
> Why isn't av1 added like the existing codecs?
That would generate invalid AV1 files if -strict -1 or -2 specified (and
currently AV1 mov writing is behind -2). Actually, I'm not sure why the
other codecs are behind the compliance flag either - I'm
On 08/13/2018 03:47 PM, Carl Eugen Hoyos wrote:
> 2018-08-14 0:36 GMT+02:00, Thomas Daede :
>> On 08/13/2018 03:30 PM, Carl Eugen Hoyos wrote:
>>> Why isn't av1 added like the existing codecs?
>>
>> That would generate invalid AV1 files if -strict -1 or -2 specif
On 08/14/2018 11:09 AM, James Almer wrote:
> This will get ISOBMFF and Matroska up to date with the revised AV1 Codec
> Configuration Box spec.
> For now keep propagating raw OBUs as extradata until all libavcodec modules
> are adapted to handle AV1CodecConfigurationRecordv1 formatted extradata.
>
On 08/16/2018 02:22 PM, James Almer wrote:
> This will get ISOBMFF and Matroska up to date with the revised AV1 Codec
> Configuration Box spec.
> For now keep propagating raw OBUs as extradata until all libavcodec modules
> are adapted to handle AV1CodecConfigurationRecordv1 formatted extradata.
>
