Skip to main content
Participant
January 31, 2021
Answered

Color problems when converting from Adobe RGB to ProPhoto RGB

  • January 31, 2021
  • 2 replies
  • 1273 views

I have a RAW file which I open in Photoshop (v22.1.1) through Camera RAW (v13.1). If I have the Photoshop working space set to Adobe RGB the image looks fine. But if I convert the image to ProPhoto RGB in Phosothop, clearly visible banding occurs in what should be a smooth blue gradient.

 

Is it normal that this can happen? I thought the ProPhoto color space fully encompassed the Adobe color space?

I run Photoshop on Windows 10.

 

 

This topic has been closed for replies.
Correct answer D Fosse

Interesting... does this imply that when editing images for web publishing, it is in practice better to use Adobe RGB than ProPhoto as working space after initial RAW conversion in order to avoid artefacts? If I'm not mistaken, when targeting high-end printers ProPhoto would be better since printers can have wider gamut range than monitors?


The answer to that is to use the most appropriate color space for your needs.

 

ProPhoto has exactly one advantage: the huge gamut. But as with everything else in life, it comes at a price. The price is the compression of middle values, which is where you are most of the time. Subtle adjustments are difficult, because each numerical step covers a much larger distance in actual color.

 

I use ProPhoto when I need to. But I prefer Adobe RGB. It's much easier and more pleasant to work with.

 

Also keep in mind that editing in ProPhoto just postpones a problem you have to deal with sooner or later: gamut clipping when converting for some output or other. You don't want gamut clipping, or not a lot of it at any rate. It usually looks pretty bad. And if you simply convert a ProPhoto file to sRGB or an average print profile, you're probably going to get a lot of clipping. It's simply easier to deal with at an earlier stage.

 

In other words, working in ProPhoto can increase the risk of a poor output result.

 

Yes, I hear the argument all the time that some high end printers can print some colors outside Adobe RGB. While technically true, my response to that is - so what. Good color isn't about maximum saturation, it's about color relationships. Those printable non-Adobe RGB colors are a small range of already extremely saturated colors, and in a very limited hue range. To me, that's an insignificant consideration weighed against the other inconveniences and shortcomings of ProPhoto.

 

 

2 replies

Stephen Marsh
Community Expert
Community Expert
January 31, 2021

Why render from ACR to Adobe RGB, then convert to ProPhoto in Photoshop, when you can render direct to ProPhoto from ACR?

Participant
February 1, 2021

Right, that's what I normally do, sorry I wasn't clear in the original post. I actually first noticed the color issue after opening the image in Photoshop from Lightroom (the developed RAW looked ok in Lightroom, and I had Lightroom set to 16bit ProPhoto export to Photohsop). Trying to pinpoint the problem, I then opened the original RAW in ACR in Photoshop and rendered it to Adobe RGB in Photoshop, after which it looked ok in Photoshop. But if I manually converted it from Adobe RGB to ProPhoto in Photoshop, the banding occurred. Finally, if opening the original RAW in ACR in Photoshop and rendering it directly to ProPhoto in Photoshop, the banding also occurred.

D Fosse
Community Expert
Community Expert
January 31, 2021

It's in your display system, which works at 8 bit color depth.

 

ProPhoto is much more vulnerable to this because it's so large that the "useful" values in the middle are vey compressed.

Participant
January 31, 2021

Thanks!

D Fosse
Community Expert
Community Expert
January 31, 2021

As a general rule of thumb, ProPhoto will amplify any latent problems.

 

It happens when 16 bit data are converted into 8 bit data for the display pipeline. Initial banding here rapidly gets amplified in several places from video card to the display panel itself.