Adobe Rgb

raythefab

Suspended / Banned
Messages
2,145
Edit My Images
Yes
I have been getting a few wishy washy photo's lately, then ive just noticed my camera was set to abobe rgb instead of RGB would this account for the poor looking images on my computer thank you ...Ray:)
 
you're far better off sticking with sRGB throughout
check your photoshop settings too!
 
but apart from photoshop, when i look at a photo in my picture's would they look weak
 
Yes, AdobeRGB allows for more saturated colours than sRGB and if you view them in a program that isn't colour managed the saturation will be display wrong.
 
Adobe 98 gives a much wider range of colours than sRGB, so it's a bit like the RAW/jpeg argument - why through away colours when you don't have to?

The internet & most commercial printers can't actually display/print the full gamut of Adobe 98, so it's best to convert to sRGB for those - or if that's the only thing you'll do with those images, then shoot them in such too

But most here probably have an inkjet at home? Good inkjets can print more colours than the sRGB file holds, hence shoot in the wider colour gamut first and throw away colour when not suited to the medium

Make sense?
 
AdobeRGB doesn't have more colours, it has greater saturation mainly in the magenta/green extremes and that creates a whole bunch of other problems.

To use the more saturated colours you have to lose tonality in 8bit space. As you're now trying to get extra data into the same space something has to give.

Why not use 16bit? Well apart from the limits that has in image editing unless you're printer driver supports 16bit it will end up as 8bit anyway so you still lose the tonality. Some of the high canon printers now support direct 16bit printing and there is dedicated app available with it's own drivers for high end inkjets but it's pricey, about $2000 if memory serves.

The trick with colour management is to consider the size of the colour space on the final output device and then use a working space that is as close to the same size as possible. That will get you as much saturation and tonality as you can use without wasting any data on values you can't output. For 99% of us that means 8bit sRGB. Using AdobeRGB because it's bigger you are likely to be throwing away more data than you are gaining when you compare the saturated magenta/green to the banding it introduces.

Lot's of info here: http://www.cambridgeincolour.com/tutorials/sRGB-AdobeRGB1998.htm especially the chart on printer gamuts
 
Hi pxl8

I'm confused now...
AdobeRGB doesn't have more colours
from your opening statement

We see a big difference in how each printer uses the additional colors provided by Adobe RGB 1998

My advice is to use Adobe RGB 1998 if you normally work with 16-bit images, and sRGB if you normally work with 8-bit images. Even if you may not always use the extra colors, you never want to eliminate them as a possibility for those images which require them.

both above are from the link you provided

Isn't your link confirming exactly what I said? :thinking:

As I read your link it says to me - sRGB has less colours, and is appropriate to shoot in IF you know you'll never need the full range that Adobe 98 would have captured
 
Isn't your link confirming exactly what I said? :thinking:

The key is the 8bit or 16bit output. True 16bit prints are not cheap or easy to come by. High-end inkjets might have a larger gamut that sRGB but the driver converts to 8bit so you either lose the extra saturation (relative colormetric conversion) from the larger colour space or get banding (perceptual conversion) at the output stage. 8bit doesn't provide enough room for the data a larger colour space can hold so you have to lose data somewhere.

AdobeRGB has more "colours" but unless you stick to 16bit with a properly colour managed workflow you won't get more "colours" and, in fact, will probably be worse off.
 
Have you tried both yourself as a test?

My understanding came from reading stuff a while back and from listening to Pros who 'seemed' to know all about it - making a good case for sRGB being a :nono:

What I haven't done (and odd this for me) is I haven't actually tried it, so over the next week or two, when I have time, I'll have a wee project of testing studio/outdoors on both settings and check the results from my i9950 and Loxley - should be interesting - so thanks for rattling my cage on this one :thumbs:
 
I did some tests a while back and couldn't tell one print from the other but that's hardly surprising as the output device was sRGB and the image didn't need the extra values of the larger space. What it did was confirm that sRGB met my needs in a real world scenario. If the day ever comes where the output device is 16bit AdobeRGB capable and the image uses the larger space I'll test again.
 
Back
Top