Ckw From UK - England, joined Aug 2010, 659 posts, RR: 17 Reply 1, posted (10 years 6 months 2 weeks 2 days 23 hours ago) and read 3613 times:
The problem here is that AdobeRGB can look desaturated when viewed as standard RGB (ie. web) - particularly reds seem to suffer - I also encountered this when I switched to Capture One.
2 possible solutions: when you import into PS, goto Image-Mode-ConvertTo Profile and select sRGB before doing any editing. This is probably the best solution if you are preparing just for the web.
Alternatively, you can work in Adobe, but use View-Proof Setup to select monitor RGB (web colours) and then View-Proof Preview to see what your image will look like on the web, and make any necessary adjustments based on this.
UngoMongo From Denmark, joined Aug 2001, 146 posts, RR: 1 Reply 4, posted (10 years 6 months 2 weeks 2 days 12 hours ago) and read 3437 times:
I read, that Adobe RGB has a higher color space than sRGB and therefore I sat the Adobe RGB as the working color space. But I can see, I won't get any benefits of converting. But I think, it's strange, that the pictures get under-saturated, if you chose to convert.
Ckw From UK - England, joined Aug 2010, 659 posts, RR: 17 Reply 5, posted (10 years 6 months 2 weeks 2 days 12 hours ago) and read 3445 times:
Strictly speaking, Abobe has a broader gamut - ie. it can handle a wider range of colours (there are colour spaces which are even boader) BUT to benefit from this you have to use software capable of processing that gamut through to the finished product - use PS to send the image to a properly set up printer, and you'll see the advantage. But if you send that extra colour to a device which can't handle it - eg. a web browser, that extra colour is just thrown away.
If, however, you convert to sRGB within PS (rather than just save the file) you'll find that PS re-maps the colour info so that there should be little if any visible difference on the screen.