You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content types seem to have been updated in the public Dolby docs after the patent was filed, but the white point table may still be the real one. I haven't found anything that counters it. It defines 0 as "Default" and codes 1-15 as 4500 + 500 x code (with D65 at code 4), instead of the linear Kelvin ramp in editor.md today. Or is there a reason you don't use it?
I was also wondering if fig. 4C might explain the byte2=8 from #381. It says bits 2-3 there are "noise reduction", which would decode as NR=2 on a phone capture.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi quietvoid, I was curious if you had already checked this patent. It includes the L11 byte layout (fig. 4A-4D), the white point table (fig. 8), and the content types + sub-types (fig. 7):
https://patentimages.storage.googleapis.com/bc/bc/b9/154447e495a376/US11743550.pdf
The content types seem to have been updated in the public Dolby docs after the patent was filed, but the white point table may still be the real one. I haven't found anything that counters it. It defines 0 as "Default" and codes 1-15 as 4500 + 500 x code (with D65 at code 4), instead of the linear Kelvin ramp in editor.md today. Or is there a reason you don't use it?
I was also wondering if fig. 4C might explain the byte2=8 from #381. It says bits 2-3 there are "noise reduction", which would decode as NR=2 on a phone capture.
Thanks!
All reactions