On Wed, Apr 1, 2020 at 6:04 AM Derek Buitenhuis <derek.buitenh...@gmail.com> wrote:
> Would it make sense to allow it by default for QTFF only, since it is > properly > defined in it? OR would that perhaps be a little confusing from a user > perspective? > Do you know where it's properly defined for QTFF? The only references that I've been able to find about this atom are in the two links in my original email, which isn't satisfactory to me personally. I asked one of the authors of the AV1-ISOBMFF spec, and they said it has > been > standardized in MIAF (23000-22), and should make their way back to > 14496-12 in > the next edition. One idea is to allow it for AV1 by default, but, as > above, it > is perhaps too confusing from a user perspective to do that. > I'm not necessarily opposed to that but I have a (slight) preference for not doing that for the reasons of confusion you mentioned. Aside: Is there an value in also supporting the mdcv box (in general)? Yes, definitely, and I've sent out a patch to do that[1]. Admittedly there's a merge conflict between these two patches because I did them separately but that's simple enough to solve manually. [1]: http://ffmpeg.org/pipermail/ffmpeg-devel/2020-March/259418.html _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
