On Mon, Apr 13, 2020 at 10:26 AM Michael Bradshaw
wrote:
> Attached patch is updated to do that.
>
Pushed to master, but with a change to use AV_LOG_VERBOSE logging (to be
consistent with the clli atom).
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpe
On Wed, Apr 1, 2020 at 1:18 PM Carl Eugen Hoyos wrote:
> Same here: If this helps, it should not be optional imo.
Based on Jan's email I'm fine with removing the flag and just writing this
atom by default. Attached patch is updated to do that.
0001-avformat-movenc-write-the-mdcv-atom-by-defau
Am Di., 31. März 2020 um 19:00 Uhr schrieb Michael Bradshaw
:
>
> The mdcv atom isn't in ISO/IEC 14496-12:2015 so the flag is marked as
> experimental and the mdcv atom is not written by default.
>
> The mdcv atom is referenced by e.g., [1][2] and is already parsed in FFmpeg
> in mov.c.
>
> Once IS
Attached is an updated patch that resolves merge conflicts against the
latest master.
0001-avformat-movenc-add-write_mdcv-flag-to-write-mdcv-at.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailm
The mdcv atom isn't in ISO/IEC 14496-12:2015 so the flag is marked as
experimental and the mdcv atom is not written by default.
The mdcv atom is referenced by e.g., [1][2] and is already parsed in FFmpeg
in mov.c.
Once ISO/IEC 14496-12 standardizes the mdcv atom (which I assume it will?)
then we
