On Sat, Jan 16, 2016 at 04:19:38PM -0800, Neil Birkbeck wrote: > Adding mastering display metadata struct to avutil. The mastering display > metadata contains information > about the mastering display color volume (SMPTE 2086:2014). > > This info comes from HEVC in the SEI_TYPE_MASTERING_DISPLAY_INFO and is soon > to be included in MKV: > https://mailarchive.ietf.org/arch/search/?email_list=cellar&gbt=1&index=sZyfPTM-QY69P-0omfOIiTN622o > so it is similar to SEI FPA / stereo_mode in MKV and as such this patch > follows how AVStereo3D is implemented. > > I'll add support to HEVC in a follow-up (and MKV when spec is approved). > > Signed-off-by: Neil Birkbeck <neil.birkb...@gmail.com> > --- > libavutil/Makefile | 2 + > libavutil/frame.h | 7 ++- > libavutil/mastering_display_metadata.c | 43 +++++++++++++++++ > libavutil/mastering_display_metadata.h | 87 > ++++++++++++++++++++++++++++++++++ > libavutil/version.h | 2 +- > 5 files changed, 139 insertions(+), 2 deletions(-) > create mode 100644 libavutil/mastering_display_metadata.c > create mode 100644 libavutil/mastering_display_metadata.h > > diff --git a/libavutil/Makefile b/libavutil/Makefile > index bf8c713..65b2d25 100644 > --- a/libavutil/Makefile > +++ b/libavutil/Makefile > @@ -38,6 +38,7 @@ HEADERS = adler32.h > \ > log.h \ > macros.h \ > mathematics.h \ > + mastering_display_metadata.h \ > md5.h \ > mem.h \ > motion_vector.h \ > @@ -115,6 +116,7 @@ OBJS = adler32.o > \ > log.o \ > log2_tab.o \ > mathematics.o \ > + mastering_display_metadata.o \ > md5.o \ > mem.o \ > murmur3.o \ > diff --git a/libavutil/frame.h b/libavutil/frame.h > index 9c6061a..308355b 100644 > --- a/libavutil/frame.h > +++ b/libavutil/frame.h > @@ -106,12 +106,17 @@ enum AVFrameSideDataType { > * @endcode > */ > AV_FRAME_DATA_SKIP_SAMPLES, > - > /** > * This side data must be associated with an audio frame and corresponds > to > * enum AVAudioServiceType defined in avcodec.h. > */ > AV_FRAME_DATA_AUDIO_SERVICE_TYPE,
> + /**
> + * Mastering display metadata associated with a video frame. The payload
> is
> + * an AVMasteringDisplayMetadata type and contains information about the
> + * mastering display color volume.
> + */
> + AV_FRAME_DATA_MASTERING_DISPLAY_METADATA
will this always stay the same or could it require to be extended in
the future ?
if future extensions may occur then it should be documented how that
would work. Would fields be added to the end of the struct ?
If so how would this be detected ?
C does not gurantee the sizeof to change for the addition of fields
for example these 2 are both 8bytes on x86-64
typedef struct X { int a; char b; }X;
typedef struct Y { int a; char b; char c; }Y;
defining the meaning of the sidedata byte per byte avoids the problem
of detectability it also makes the function endian and ABI independant
and would allow passing it bytewise between computers, no idea how
much thats a real world use case though
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
