> If I want to render this video on screen, say a SDR screen, or my
> player is just not HDR capable (yet), what transfer do I use? The
> value avcodec gives me has not much meaning in that case (because I
> can't deal with HLG yet), and the original "legacy" value meant to be
> used in these cases
On Tue, Aug 8, 2017 at 4:52 PM, Vittorio Giovara
wrote:
>> Following their logic, what if I can't deal with HLG yet, and I want
>> the original transfer?
>> Maybe it should be exported somehow, or have an option to not use the
>> alternate one, or something?
>>
>> One of the key points of HLG is c
> Following their logic, what if I can't deal with HLG yet, and I want
> the original transfer?
> Maybe it should be exported somehow, or have an option to not use the
> alternate one, or something?
>
> One of the key points of HLG is compatibility with non-HDR systems, so
> if the bitstream alread
On Tue, Aug 8, 2017 at 4:36 PM, Vittorio Giovara
wrote:
> The use of this SEI is 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 ca
The use of this SEI is 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.
Sig
