Take your photography to the next level and beyond...

  • NEWS
  • REVIEWS
  • INSPIRATION
  • COMMUNITY
  • COMPETITIONS

Why not join for free today?

Join for Free

Your total photography experience starts here


Anyone know what's going on here?


Jaff e2
6 7 1
22 Feb 2013 3:20PM
Hi all.

Here we have the same shot done in RAW. One converted in ACR and one converted with DPP. No processing applied by me other than web resizing done in Photoshop CS3. For some reason the ACR produces what looks like a corrupted image but the image can't be corrupted because it appears normal in FastStone and is normal when converted with DPP. I even opened the converted DPP file (be it JPEG or TIFF) into ACR from within photoshop and it stayed normal.

All of the shots I took of these fountains (Canon 50D + 70-200mm f2.8 IS II) came out in a similar fashion but shots I took before and after the fountain shots open up into ACR completely normal. Any ideas why this has happened? img-9581photoshop-acr.jpg

img-9581dpp.jpg

Join ePHOTOzine for free and remove these adverts.

22 Feb 2013 3:38PM
looks like the blue channel is overly clipped, not corrupt. I could be wrong.
mikehit e2
5 7.1k 11 United Kingdom
22 Feb 2013 3:50PM
I woudl agree with clipped blue channel.
It does not surprise me at all that DPP handles it better than ACR - in some extreme cases Canon's knowledge of how their hardware works will show an advantage.
GlennH 9 1.9k 1 France
22 Feb 2013 7:29PM
The blue could easily be oversaturation (i.e. extremely clipped blue channel), but maybe the cyan is a woeful attempt at highlight recovery? Difficult to know without the opportunity to try and replicate it.
22 Feb 2013 7:55PM
Saw a similar example on another forum but the poster made the Raw file available. When I looked at the Raw file in LR, I found that the blue was out of gamut but adjusting the WB soon fixed this and got rid of the clipping. Although I do not normally use DPP myself, I believe that many believe that it is better than ACR because they may not be aware that (at least for most recent Canon DSLR's) the setting in the camera (settings for JPEG, contrast, WB , sharpness, colour balance, picture style etc.) are use as the default initial settings by DPP. So a lot of processing is applied by default. For LR or ACR this is not the case you need to select the settings yourself (or use a preset). I would not criticise the DPP approach as most photographers might appreciate having a default based on camera settings. However, I like to be in full control so prefer the more neutral approach of LR/ACR.

Dave
23 Feb 2013 10:21AM
Having just re-read my comment above, I just wish to make clear one point. Although DPP may start with default settings from the camera, you are free to change those settings in DPP as you would in other Raw converters.

Dave
Jaff e2
6 7 1
23 Feb 2013 1:03PM
So are you saying what has caused this then is that some of the colours in the shots I took are just too blue, green, purple or whatever for ACR to recognise them and it has attempted to autmotically recover them in some way where as DPP has not done any automatic image adjustment. The numbers do run pretty big like well into the 200's and in some cases upto 255 which would support the clipping suggestion.
23 Feb 2013 4:23PM
It is difficult to be certain but in a similar very blue image it was a case of out of gamut colours which would be true whether using ACR or DPP. If you were using Lightroom 4.3, it has a excellent soft proofing facility which allows easy analysis of out of gamut problems. Very strong colours may actually be out of gamut for your monitor not just printer. However, I am sure your image can be easily processed in both ACR and DPP just by using the right settings.

Dave
GlennH 9 1.9k 1 France
23 Feb 2013 6:27PM
To me it looks like pure over-saturation in the blue channel, but the cyan is a bit funkier than that! There's very little RGB data in that part of the image, with blue and green channels both clipped, and it would take a radical move to turn the red channel to solid cyan. Like Dave, I tend to think it's purely down to some wayward settings, or a poor camera profile perhaps - zeroing to default settings I'd imagine would clear this up.

Sign In

You must be a member to leave a comment.

ePHOTOzine, the web's friendliest photography community.

Join For Free

Upload photos, chat with photographers, win prizes and much more.