sRGB v Adobe RGB

[stylo]

Hi all, I have read many of the great tutorials but remain puzzled by one area - If my output is going to be either the web, or printer (mine or a print shop) am I creating potential problems by using Adobe RGB? I ask as I believe the output modes I am most likely to use only properly support sRGB so if I spend time editing images etc with the wider gamut of Adobe I then have to convert to sRGB for the web or to print. What is the advantage in using Adobe RGB in the middle of all this?

Thanks for the enlightenment
Adam

[McQ]

If the only intended use of these photos is for devices that can only utilize the gamut of sRGB, then there is really no advantage to using Adobe RGB during the editing process. However, if you think you might try printing somewhere else at some point in the future, then sometimes it's worth having your images saved in a wide gamut like Adobe RGB. After all, it is easy to convert an image from a large to a smaller gamut, but once this is done you cannot realistically go back.

[stylo]

Hi & thanks.

OK, that's kind of what I was hoping - I'm getting there....

If you're critical of the quality of your printing and your printer (& most external print shops as I understand it) only support sRGB (or I suppose CMYK for mags and the like) aren't you creating problems by having to do the sRGB conversion at the output stage and *hoping* the conversion provides a pleasing result, else you either get a poor print or spend time and money on different conversions etc? So although you'd have the future possibility for better printing if you can get greater than sRGB, you may have a fair bit of hassle here and now due to the conversion and out of gamut colout handling???

Or, is it that the *potenital* issues at the conversion stage are not really that bad and 99% of the time a default transition from Adobe RGB to sRGB will be fine?

Maybe I'm missing something else - my thinking has been caused by trying to simplify my processing and get predictable results. But if my monitor and printer don't provde good sRGB support then I'm going to have the potential issues even using sRGB. Currently using a Pixma Pro9000 and a Dell HC24 monitor - must look into their claimed sRGB support.

Thanks again
Adam

[McQ]

Originally Posted by stylo

Or, is it that the *potential* issues at the conversion stage are not really that bad and 99% of the time a default transition from Adobe RGB to sRGB will be fine?

Yes, that's been more or less my experience. The average photo will not experience significant problems on conversion, and even if it does, often switching between relative colorimetric and perceptual conversion (or vice versa) can reasonably sort things out.

Originally Posted by stylo

Maybe I'm missing something else - my thinking has been caused by trying to simplify my processing and get predictable results. But if my monitor and printer don't provde good sRGB support then I'm going to have the potential issues even using sRGB. Currently using a Pixma Pro9000 and a Dell HC24 monitor - must look into their claimed sRGB support.

Nearly all monitors can encompass sRGB; it's just whether you have a good color profile and whether it can precisely allocate bits anywhere throughout sRGB that can be the problem. There' a lot more on this on this site's tutorial on sRGB versus Adobe RGB 1998. The "high end inkjet" gamut shown in the interactive comparison plots should be a reasonably accurate estimate of your printer, since the printer used on that page is the Canon iP9900.

[Colin Southern]

I think that there's a wee bit of "Excessive / Compulsive Disorder" in every photographer. When presented with choices like sRGB and Adobe RGB we're tempted to gravitate towards the bigger colourspace because we feel that it's just that little bit closer to perfection.

In reality though the bigger the colourspace, the greater the opportunity to create something that can give you no end of headaches. I recall a particular image that I was working on in L*A*B colour (a colour space much larger than either sRGB or Adobe RGB) - I had certain bright reds looking great on the screen, but portions of them always printed out closer to orange - making the whole image look a bit of a mess - and I was tearing out what hair I had left trying to figure out why; in the end (or course) I had created colours that could be neither displayed on my monitor, nor printed on my printer - but what compounded the issue was my monitor profile had translated them into something displayable on the screen - and that's what I was adjusting the image around (kinda like the blind leading the blind). When I finally wised up and turned on the out-of-gamut warning (when soft-proofing) I was met with a grey sea of "warning". From this point I was able to tweak the colours until the warnings disappeared - and "hey presto" everything printed just fine after that.

The lesson I learned in the end was "the bigger the colourspace, the more trouble you can get yourself into" - that's not to say we shouldn't use bigger colourspaces - just be careful; if you capture an image in aRGB (or RAW) and print it on a printer that has a wider gamut than sRGB then you'll almost certainly be printing additional colours that sRGB would have rendered into something else - but whether or not you can even notice these additional colours is another matter entirely.

Personally, I shoot RAW - manipulate & print in either ProPhoto or LAB colourspaces - and only convert to sRGB if I have to put the image on the web or have it printed at a lab - but to be honest, I'm probably not gaining a lot.

Hope this helps.

Cheers,

Colin - photo.net/photos/colinsouthern