There's a couple of problems with just assuming that the extremes of a device range will give you the extremes of the color. One is that it's an assumption, nothing guarantees such behavior. It's quite possible that some device may produce a lighter black for RGB = 0 than some other RGB values...
BPC is nothing to do with ArgyllCMS, it's strictly a CMM thing.
The type of black that is created (in CMYK profiles) is up to you - you set it with your choice of black generation when you create the profile.
If you are referring to RGB profiles then the profile has no control over the black...
It's not like the instrument has some mechanical hours counter in it. It relies on the driver software to count usage time and update the non-voltile memory in the instrument. And as I explained, it seemed safer not to write to the instrument EEPROM, given that the format is complex and not...
The Munki doesn't have a UV filter but it uses a LED light source, which doesn't emit any UV, so hence gets little OBS/FWA response. So no UV filter, but yes equivalent to having a UV filter.
Repeatability of the Munki is superior to the I1Pro, because the LED light source is more stable than...
Sorry, I don't really understand what you mean. By default i1 and Munki strips are optimized so that ArgyllCMS can automatically recognise the direction the strip is read in. ArgyllCMS doesn't currently support the iSis.
According to the targen verbose output, there should be heaps of contrast between the patches and colored spacers (nearly 60 Delta E), so it's strange that you had problems. You could try increasing the space width slightly, using the printtarg -A option, i.e. "-A 1.5".
Another thing to try is...