While trying to debug some weird repeating evenly-spaced ripple I’m seeing in my i1Pro2 measurements from the 256 step i1Profiler target (I’ll provide more in a separate thread once I’ve isolated what is going on), I went in to Photoshop just to verify the patches in the TIF file. I’ve found 6 patches that don’t give me correct RGB (R=G=B) values as read by the Eyedropper tool. This has nothing to do with the ripple I’m trying to diagnose, but it seems possible that “false” Falses could result. In any case, I’d want all the patches to be correct before using the target for any kind of calibration.
Here’s what I read from the file in Photoshop:
Patch ID 256 = 0,0,0 (OK)
Patch ID 255 = 0,0,0 (should read 1,1,1)
Patch ID 254 = 1,1,1 (should read 2,2,2)
Patch ID 253 = 1,1,1 (should read 3,3,3)
Patch ID 252 = 3,3,3 (should read 4,4,4)
Patch ID 251 = 4,4,4 (should read 5,5,5)
Patch ID 242 = 13,13,13 (should read 14,14,14)
I checked randomly over the rest of the target and did not find any other anomalies. It seems odd that five of these patches are clustered right below DMax and the sixth is an outlier at Patch ID 242.
I notice that the target is set for 720ppi, presumably to match QTR’s processing. Was the target subjected to any resizing or other interpolation? Just wondering how these errors would have been introduced, assuming that at some point all the patches were correct.
Your i1Profiler Workflow file is fine: If I load your workflow, then save the target to a new TIF file from i1Profiler, that new TIF file reads as expected (though i1Profiler outputs an 8-bit Untagged RGB file with lower resolution vs. your 16-bit Untagged Gray file @ 720ppi).