Search results

Without being able to see the measurement data and know what the profile making workflow is (i.e. the options used to create the profile), I really can't say. The aim generally is to create the darkest black point possible. But the main limitation may be the neutrality of the lowest L* value...

You need to choose the device space that is correct for the printer/workflow you are using. You can't profile any other way. If you have a choice between an RGB and CMYK workflow, then you need to decide whether you want to take control over the separation and ink limits (which takes more time...

I'd be interested to know why that is. Could you email me the ArgyllCMS .ti3 file as well as the X-Rite .txt file of the measurement data, so I can take a look at it ?

ArgyllCMS perceptual profiles are intended to be created for a specific source colorspace. If you do that, you certainly wouldn't select BPC, since this may well mess up the overall mapping. (see https://www.argyllcms.com/doc/Scenarios.html#PP5 ). RBG has no black channel. You can't control the...

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...

Note that the ArgyllCMS driver doesn't update this. (I thought it prudent not to mess with the instrument EEProm).

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.

If you don't want any full spread patches, use -f0 to override the default of 836.

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...

Because you specified 955 monochrome patches, and 2 full spread patches (957 - 955).

I've made a demo video to go with the V1.1 release of ColorMeter that people might find interesting: 2 Minute Overview + Guided Tour Video

Because Google Play licensing doesn't have a mechanism for that.