On Sat, Jun 10, 2017 at 5:40 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Fri, Jun 9, 2017 at 11:27 PM, Vittorio Giovara > <vittorio.giov...@gmail.com> wrote: >> Signed-off-by: Vittorio Giovara <vittorio.giov...@gmail.com> >> --- >> libavcodec/hevc_sei.c | 9 +++++++++ >> libavcodec/hevc_sei.h | 7 +++++++ >> libavcodec/hevcdec.c | 5 +++++ >> 3 files changed, 21 insertions(+) >> >> diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c >> index 153d211b4b..0a5d4440bf 100644 >> --- a/libavcodec/hevc_sei.c >> +++ b/libavcodec/hevc_sei.c >> @@ -86,6 +86,13 @@ static int >> decode_nal_sei_display_orientation(HEVCSEIDisplayOrientation *s, GetB >> return 0; >> } > > Unrelated to the patch itself, but whats the use of those and why is > that value not coded in the main bitstream?
For backward compatibility in HLG HDR systems: older devices that cannot interpret the `arib-std-b67` transfer will get the "compatible" transfer (usually bt709 or bt2020) from the VUI, while newer devices that can interpret HDR will read the SEI and use its value instead. -- Vittorio _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
