Originally posted by attack11 well that's mostly common knowledge.
Well, I'm a color management consultant by profession and I've never heard the notion that AdobeRGB is "unsupported" by certain printers. If by "unsupported" you mean that a printer will assume sRGB as it's default color space when sending it un-color managed data, there might be some validity there but, again, I can demonstrate that a printer's color space is quite a bit larger than sRGB and even AdobeRGB is certain color regions.
Quote: i'm curious what monitor you have, is it an nec or eizo?
why aren't you using prophoto if the color space matters to your prints?
EIZO CG211.....and I actually DO use ProPhotoRGB when I'm rendering DNGs....but I wasn't about to push that "religion" onto someone who is a relative newbie to color management and ICC profiles. ProPhoto can actually do more harm than good if you don't have at least a basic understanding of the principles of color management.
Interestingly, my EIZO CG211 is essentially an sRGB display, albeit a pretty good one. But I don't see that as a major limitation as it's not really what I use as a "reference" in terms of accuracy. For me, the print is *the thing* because I know that it's likely more accurate than my display and it has a wider gamut than my display....and I can always use the *numbers* in the file to tell me if things are clipping rather than relying solely on the display (the "numbers thing" goes back to my CMYK days). It seems silly (to me) to restrict my entire imaging workflow to the color space (sRGB display) that nobody but myself will ever likely view my images on. On the other hand, lots of folks will see the PRINTS I produce and I want to take advantage of my "printing space" as much as possible. And if you don't think there's a difference between a print made using the full color space/gamut that the print system is capable of vs. a print restricted to sRGB, you're wrong. It's easily visable to viewers tuned in to seeing these differences.
As far as ProPhotoRGB vs. other working spaces, I have my issues as well with this space and I think the choice or reasons for using AdobeRGB, or even sRGB, over ProPhoto are legitimate ones. I've even had friendly arguments with colleagues over ProPhoto vs. AdobeRGB where I was arguing for NOT using ProPhoto. For me, what it came down to is that I'd rather have the END of my imaging workflow be the restricting factor and not the BEGINNING (the rendering space). I've analyzed enough images to know that, while it's extremely rare than an image will "push" the envelope of the ProPhoto color space, I've also seen enough images where AdobeRGB would've resulted in clipping, that I decided ProPhoto is the safest bet IF you want to try and grab everything your photographic system has to offer. Personally, I'd rather have the option of rendering into a color space of my choice that is slightly larger than AdobeRGB but not the monstrosity color space of ProPhoto (my own preference is a working space profile called "eciRGBv2")....but since Adobe in their infinite wisdom doesn't allow one to (easily) render RAW files into the space of the users choice, we're stuck with few choices, basically sRGB, AdobeRGB or ProPhotoRGB.
This is a very interesting discussion to me since I rarely hear color management discussed in any kind of depth in photography forums even though it is arguably one of the most critical elements in the workflow. If it's all about the images we produce, then color management clearly has it's place in this discussion.
Regards,
Terry