Update and complete L11 metadata

[quietvoid]

The latest patent on L11 metadata defines the block more precisely:

// byte 0
content_type           u(4)
content_sub_type       u(4)

// byte 1
white_point            u(4)
reference_mode_flag    u(1)
reserved               u(3)

// byte 2
sharpness              u(2)
noise_reduction        u(2)
mpeg_noise_reduction   u(2)
frame_rate_conversion  u(2)

// byte 3
brightness             u(2)
color                  u(2)
reserved1              u(2)
reserved2              u(2)

However I'm not sure that the existing implementations actually behave correctly according to these changes.

For example, increasing the intended whitepoint never becomes warmer, always colder.
While it's specified that 0 is default (no changes) and 4 is now D65.

[saindriches]

Current byte 0 and byte 1 implementations should be correct. The byte 2 is called Content adjustment in latest verifier. Some Android devices supporting Dolby Vision recording set this byte to 8, however we don't know the meaning of it in actual implementations. The byte 3 should be still reserved.

[quietvoid]

Right.
Both content type and white point don't match the new patent in the verifier.

The Content adjustment summary isn't really useful.
Not sure it's worth doing anything before some devices actually recognize byte 2.

[Nomis101]

There is now a knowledge base article about Content Type Metadata (L11).
https://professionalsupport.dolby.com/s/article/Dolby-Vision-IQ-Content-Type-Metadata-L11?language=en_US

[quietvoid]

I guess it clarifies that the whitepoint at 0 is correct for D65.

[Nomis101]

Nice. And just interesting to know, according to this spreadsheet there are a few applications that do support L11:
https://app.smartsheet.com/b/publish?EQBCT=e7cb9987b9a44b35b7bac4fba2a754a8

[quietvoid]

There seems to be some more defined parts for L11 in the Dolby verifier.