On Fri, Dec 07, 2018 at 07:34:43PM +0200, Jan Ekström wrote: > On Wed, Dec 5, 2018 at 7:13 PM Jan Ekström <jee...@gmail.com> wrote: > > > > On Mon, Dec 3, 2018 at 3:19 AM Jan Ekström <jee...@gmail.com> wrote: > > > > > > From: Rodger Combs <rodger.co...@gmail.com> > > > > > > These are registered identifiers at the MPEG-4 RA, which are > > > defined as to be utilized for Dolby Vision AVC/HEVC streams that > > > are not correctly presentable by standards-compliant AVC/HEVC players. > > > > > > According to the Dolby Vision specification for ISOBMFF, these sample > > > entry codes are specified to have the standard AVC or HEVC decoder > > > configuration box in addition to the Dolby custom DOVIConfigurationBox. > > > This is what enables us to decode the streams without custom parsing. > > > > > > For correct presentation information from the DOVIConfigurationBox > > > is required (YCbCr or modified ICtCP, SDR or HDR, base or enhancement > > > layer). > > > --- > > > > Gentle Ping? > > > > Jan > > Ping^2? > > And if nobody really cares, I will reverse the comments on the AVC > entries (since I seem to have gotten them the wrong way around when > adding the comments and commit message late at night) and apply the > set tomorrow morning. These additional identifiers and the comment > should not be affecting existing FATE samples.
probably ok, if tested and it works thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are best at talking, realize last or never when they are wrong.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
