Should you normalize RGB values by 255 or 256?
1–10 of 156 posts
Re: Should you normalize RGB values by 255 or 256?
#2Re: Should you normalize RGB values by 255 or 256?
#3Re: Should you normalize RGB values by 255 or 256?
#4RGB values represent luminances against some adapted state, and a "zero" in a daylit scene is not "zero luminance" - it's just about 0.001x as bright as the brightest point - it's millions of photons, way more than zero. In a sense our eyes experience contrast on a sliding scale, and there is no absolute zero in the system. For example, broadcast systems historically used 16-235 as their luminance range for SDR. I think any argument that says "we must have zero" is going to have a bias, but I don't think zero is needed for most things.
Re: Should you normalize RGB values by 255 or 256?
#5Re: Should you normalize RGB values by 255 or 256?
#6If you have a ruler and it goes to 12 inches, you should normalize by the length L and not by 13, the number of points on the ruler.
Re: Should you normalize RGB values by 255 or 256?
#7If you have a ruler and it goes to 12 inches, you should normalize by the length L and not by 13, the number of points on the ruler.
Re: Should you normalize RGB values by 255 or 256?
#8I'll argue for the +0.5 solution. First, I don't like half-sized intervals at the edges, and second, a 255-based representation is typically a SDR (not HDR) image. RGB values represent luminances against some adapted state, and a "zero" in a daylit scene is not "zero luminance" - it's just about 0.001x as bright as the brightest point - it's millions of photons, way more than zero. In a sense our eyes experience cont…
Re: Should you normalize RGB values by 255 or 256?
#9Re: Should you normalize RGB values by 255 or 256?
#10The HTML/CSS is bad that lets it completely overflow the right edge of the page instead of wrapping.
I re-read this post three times in total confusion before I figured out the most important piece was off-screen entirely.