Your Canon software is reading proprietary image data that is not available outside of that software. It is converting your images according to the parameters established by Canon. ACR, on the other hand, does not read that information. It is your responsibility to use the calibration settings to create settings that are appropriate for your shooting style and for your specific camera. This is called "calibration". Once you have made these adjustments so that they are giving you acceptable results, you should save those as your Camera Raw defaults. Then ACR will use those settings in Bridge and in ACR, and you should be able to get consistent results
Thanks for the reply. I knew that Adobe doesn't have access to the Canon codec (for example, in my workflow I know I have to reset Exposure Bias in ACR as setting it in my camera doesn't translate).
I shoot in mixed lighting environments - red, blue, green, yellow, white spotlights (some LED and some bulb) with and without haze - all without flash. I can set a custom white balance to correct for the varied light, but that's another one of the features that like EV doesn't seem to be readable by ACR. I currently have 8 ACR defaults set up to map to the various lighting/ISO settings - I haven't been able to come up with one general calibration so I can't set that as the default.
I'd never had to calibrate the channel interpretation before - been using ACR/Photoshop CS2 and CS3 since it came out in May and through November it worked great. I was hoping that there was some obvious setting I set wrong.
I'm going to try removing ACR 4.3.1 and go back to the previous version ACR 4.2 - the files came in fine with that version.
I rechecked my non-Adobe software (ImageBrowser, DPP, Preview) and discovered that they were color managed and the settings weren't the same as ACR. Bridge/ACR were/are interpreting the RAW files correctly. I've set all ColorSync profiles and CMM options so that they're the same.
I did discover an interesting workaround though and why I'd not run into the oversaturated red before. Prior to December I hadn't used Bridge to preview CR2 files or edit metadata, I'd opened Photoshop and run Web Gallery on the folder with my CR2 files to create thumbnails and generate JPEGs for images I'd chosen outside Creative Suite. I've gone back to using that to generate proof images (that aren't color managed) so that people can select the images they want and I can then post-process those images in ACR using calibration presets. NOTE: When I preview CR2 images and then run Web Gallery the images are color managed and have the oversaturated red. If I purge Bridge cache and Photoshop cache and run Web Gallery again the images appear without the oversaturated red.
i'm also having a problem with over saturation of color in photohsop CS3. when i preview a jpeg image (shot with my nikon d70) using 'windows picture and fax viewer', the saturations is normal, but when i open that image in photoshop it's over saturated; particularly reds. i haven't always had this problem, and it's incredibly frustrating.
I see that this is a super old post, but I am having the same issues with .CR2 (Canon 20D) and .ARW (Sony Alpha A55) files in Adobe Bridge CS5. I have never needed to do anything special before, and I had no problems when shooting .JPG with my older Panasonic DMC-FZ28 camera. Even the files shot in .JPG with the Sony Alpha A55 have this oversaturation issue, especially with reds. I'm not sure how to fix this problem? Help please!