On Tue, Nov 6, 2018 at 11:56 PM Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > > Since the patch doesn't change default muxing behaviour, it could > be committed for the time being, please mention ticket #7347. > Maybe print a warning if not reading the additional information > can be an issue. > > Carl Eugen
I will post a v2 in a moment which contains all of the AVC and HEVC identifiers specified in that Dolby specification and which are registered at the MPEG-4 registration authority (they have two AVC and two HEVC ones). After looking at the relevant specs: * These custom registered identifiers should only be utilized when the stream cannot be played as-is by a standards-compliant AVC/HEVC player. In other words, no color metadata is (supposed) to be left in the video stream, and a custom DOVIConfigurationBox is required to be parsed in order for the application to be able to interpret the actual contents of the stream (YCbCr vs ICtCp('ish), HDR or SDR, base layer or enhancement layer etc). * These sample entries all contain the standardized configuration box, which means that they should always be decode'able. Thus I am for adding these identifiers to the demuxer, even if the actual content cannot be interpreted without additional parsing. Jan _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel