Mirage RIP?

[Richard.Wills]

Thanks Marcin, using Perceptual.

Make sure to use Perceptual as Rendering Intent

Use Border option to make leading edge before print

I tend to get the rip to add borders when necessary, and gang up batches of prints, so this would only work for individual images images where border has been added to the print file.

Sounds like a bug with Black Point Compensation? Never used Remote Desktop, but I can't fathom why it wouldn't.

I can't lacate BPC options in Mirage, but have started the profiling process. Profiler 3.8.6 on and i1pro2 running latest mac os seems be running fine.

Remote desktop between two macs is most definitely not giving me a colour accurate display!

[Lessbones]

Black Point Compensation is only relevant if you're using a colorimetric rendering intent (like Relative Colorimetric, which there's no good reason you shouldn't use if you want to, unless Mirage lacks BPC for it...).  With Perceptual you shouldn't have blocked up blacks, since it is, as the name implies, a perceptual matching algorithm, BPC is essentially built in.  In Mirage the setting is probably wherever you choose "perceptual" -- you likely have an option for "Relative Colorimetric" and one for "Relative Colorimetric with BPC" maybe instead of a checkbox like photoshop uses.  I'm sure it's in there, but if your problem is happening while using Perceptual then it points more towards the profiles themselves, or some other mix up in settings.  Either way, since you can make your own profiles... make your own profiles, they'll be better.

As far as remote desktop software is concerned, I would never expect to get accurate color--  you're essentially sending video thru a live h264 encoder (or whatever other codec is being used by the particular software you're using) so you're susceptible to all sorts of weirdness that can occur with video encoding/decoding, and likely the dreaded quicktime gamma bug as well, if you're using ARD.

[digitaldog]

Black Point Compensation is only relevant if you're using a colorimetric rendering intent (like Relative Colorimetric, which there's no good reason you shouldn't use if you want to, unless Mirage lacks BPC for it...).  With Perceptual you shouldn't have blocked up blacks, since it is, as the name implies, a perceptual matching algorithm, BPC is essentially built in.

Essentially, yes, although depending on the profile, BPC can still be used; it isn't impossible that BPC will not aid the conversion. Outlined 2 decades ago by Adobe in their white paper that introduces this:

6. 2. Rendering intent
Typically, BPC is performed for conversions using the Relative Colorimetric intent. BPC is not available for conversions using Absolute Colorimetric intent.
Color conversion using Perceptual intent already maps source white to destination white and source black to destination black. Because this mapping preserves the relationships of the shades, it is unlikely that a whole shadow section will be mapped to the same black value. Therefore, BPC should not be necessary. BPC is available, however, for this rendering intent, to be used with malformed profiles. For a given picture, the user can decide whether using BPC improves the color conversion and can select it or deselect it accordingly.

As originally conceived, BPC is an improved version of the Relative Colorimetric RI. It is possible, however, to generalize the concept so that it applies to Perceptual and Saturation RIs as well. This can be done through a small change in the procedure for estimating the black point.

[Kyle Jackson]

Essentially, yes, although depending on the profile, BPC can still be used; it isn't impossible that BPC will not aid the conversion. Outlined 2 decades ago by Adobe in their white paper that introduces this:

I forgot about that little nugget, thanks for the reminder. (Off-topic, it might explain a "funny" I had in GamutVision some time ago where I accidentally toggled BPC with Perceptual and was surprised it rendered a different gamut volume -- I was expecting no effect.)