Originally Posted by TrevorS
I think you mean "Studio RGB 16-235", not "component RGB".
The presence or absence alone of BTB doesn't cause any problems at all with loss of detail in blacks or whites, but "black crush" definitely causes loss of detail in blacks. White crush defefinitely causes loss of detail in the extended whites. I don't believe it's certain that black crush and white crush always materialize together.
Trevor, thanks for the correction on the first point, but as to the second, what I was trying to get across is that the absence of BTB/WTW in a 0-255 means that 0 is the absolute black and 255 is absolute white, i.e. PC level. Now you have the crush problem if your DVI is 16 to 235 because it's interpreting 16 as absolute black and 235 as absolute white...when they aren't! That makes a dark gray into absolute black, and anything actually darker can get no blacker than that, thus lost detail.
On the other hand, if the 0-255 does contain the BTB and WTW, then 0-15 is the btb, 236-255 is the wtw, absolute black and white maps to 16 and 235 respectively on each end of the DVI connection, exactly as you hope. Thereafter, whether the display actually permits the viewing of the btb/wtw becomes irrelevant. Nothing is crushed or clipped and you've got the full range.
The salient point is that BTB and WTW needs to be represented within the 8 bit DVI output byte, or else the 16 gets remapped to 0 and the 235 gets remapped to 255.
So again, the point is that the presence or absence of btb/wtw doesn't matter for the display, but it does matter if the absence of btb/wtw within the byte causes 16 to get remapped to 0 and 235 remapped to 255.