notches on the L* axis
2007-12-06 by eappert
Hello, I am confused about how file data of equal brightness values are translated to the target profile. I assumed that the file data range of 255 brightness levels would have to be translated through the 100 L* distinctions in the proifle connexion space. Yet I can see brightness distinctions on the screen from RGB 1 to RGB 9 which should all translate to L*1 . When I first noticed this I thought it was possible BPC was using the RGB data to remap the brightness higher, but I notice the same the thing much farther up the curve. My monitor regesters a distinction between RGB 72 and RGB 73 ( L* 30) which is maintained after converting to a target space. For example in us swop coated v2 66%, 60% 58% 42% and 66% 59% 58% 41%, which both translate as L*30. I have just taken the experiment all the way to the print to remove any file to monitor anomalies. I printed a chart in a 2.2 RVB space of all 255 levels contained in blocks of L*. So for example in the L* 1 patch there were inner patches containing RGB values from 1 to 13, the L*54 patch containing RGB 128 & 129, etc. I printed out the chart on the widest range output I have (Epson 3800 on Museo silver rag) using an eye one colour profile. When the print was coming out of the printer I breathed a sigh of relief because, from a distance and under normal light all L* patches appear uniform. However when I bring the print up very close under powerful light, some L*patches seem to contain very, very faint ghostly appearances of the inner patches. Either the data got through to the control signals of my printer or they are the results of badly digested bits of beef. This phenomenon seriously challenges my understanding of colour management Any help out of the rabbit hole would be greatly appreciated. Eugene Appert.