On Dec 18, 2014, at 6:24 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote: > When the encoding space has a very large gamut (i.e. L*a*b*, ProPhoto, > BruceRGB to some degree, etc.), then you almost certainly don't want your > image to be rendered to fill that space, since you will be making it look > terrible, and throws away the actual look of the image. There's another danger of using large working spaces. If you're fiddling around with the various knobs in an image editing application, you may well be tempted to fiddle them in such a way that gives the image lots of "pop" on the screen...and, in so doing, expand the encoded gamut waaaaay beyond not only what your printer can print but also what you're actually seeing on the display. And, unless you explicitly check for that, you'll never know...and you'll also never know why you always get strange artifacts any time you try to do anything with the image other than look at it in the original editing application. Yes, I type from experience.... b&
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
