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
When viewing images encoded at 10-bits, the numeric readout for the pixel at the current cursor location is clipped to a maximum of 255. It it therefore not possible to accurately assess the numeric value for HDR pixels, as they all clip to the SDR white value.
The text was updated successfully, but these errors were encountered:
The ARGB value displayed is the color value mapped from 8-bit or 16-bit color to [0, 255] instead of clipping into [0, 255]. Therefore, 255 actually means the maximum color value which is 255 in 8-bit color, 1024 in 10-bit color or 65535 in 16-bit color.
There are 2 more issues based-on your question:
We may design an alternative way to display color value instead of mapping it into [0, 255].
Currently we don't support displaying HDR image. It is still a technical limitation that we need to take more time to investigate.
Ah, yes, it does run the range rather than clip. However, not very useful for checking encoding quality as the number's are not accurate. Addressing #1 would be helpful.
When viewing images encoded at 10-bits, the numeric readout for the pixel at the current cursor location is clipped to a maximum of 255. It it therefore not possible to accurately assess the numeric value for HDR pixels, as they all clip to the SDR white value.
The text was updated successfully, but these errors were encountered: