Urgent issue with color cast on processed images
I've been using Capture One for a couple months now and just ran into a large issue. On certain images (but I don't think all), the processed version has a magenta color cast in the shadows (compared to what I see in the viewer), enough of a cast to make it unusable to me. It's most noticeable on high ISO images with lots of shadows, but I think it's showing up on others too, just harder to see.
These are RAW photos from a Canon 6D. Capture One 8.1. Macbook Pro Retina (Mid June 2012). Mac OS X 10.10.1 but I've also tried it on a new install of 10.9 and got the same result. I've tried every option of processing and exporting- JPG, TIFF, sRBG, AdobeRGB, etc... they all show it. It's not the proofing profile, tried that too. And OpenCL, auto or off it doesn't change anything.
Anybody else have issues with this? I just spent a month editing a wedding and now half the photos look horrible and I can't get them exported in anyway that's usable.
Here is an example, note on the lower image the magenta/blue cast on the black jacket:
Thanks!
These are RAW photos from a Canon 6D. Capture One 8.1. Macbook Pro Retina (Mid June 2012). Mac OS X 10.10.1 but I've also tried it on a new install of 10.9 and got the same result. I've tried every option of processing and exporting- JPG, TIFF, sRBG, AdobeRGB, etc... they all show it. It's not the proofing profile, tried that too. And OpenCL, auto or off it doesn't change anything.
Anybody else have issues with this? I just spent a month editing a wedding and now half the photos look horrible and I can't get them exported in anyway that's usable.
Here is an example, note on the lower image the magenta/blue cast on the black jacket:
Thanks!
0
-
Not sure if this is your problem but I had similar colour cast problems. This was caused by double colour management. That is managing the colour profile in Capture one and still having colour management activated on my printer. The double management gave pictures a magenta colour cast. 0 -
My guess from the screenshot is that you are seeing a preview rendered from a sample of an image with high noise.
An abundance of noise, when averaged and viewed at "Fit" will look slightly different then the true 1:1 color seen at 100%.
Best practice is to view the image at 100% to understand the true render.
A workaround for high noise images would be to set your Preview Size in Capture One to something very small. This forces Capture One to make a new preview for any view of the image when viewed on a larger resolution screen. This will drastically decrease performance but will increase the render accuracy of the viewer images which is never really an issue unless, such as this circumstance, your image is quite noisy due to high ISO and/or poor camera noise suppression.0 -
Thanks, that was it.
I don't know if this a the right place to make recommendations, but no other software I've used had this issue so it'd be nice if a change was made to the way it works. I like to set the color of the photo when I can see the whole thing, not viewing at 100%, so this is going to make me mess around with the preview sizes all the time. (I'm an event shooter and end up with lots of high ISO images). Thanks!0 -
An understandable request.
However we need to make decisions for the software's priority. Speed Performance and qualityneed to be balanced.
As such, there are options as I have described to provide one over the other. You can adjust the software to meet your needs.
It's important to keep in mind that although you may not see this in any other software, there is no other software that does quite what we do. There are similar softwares like Lightroom, but the render performance in Lightroom is quite slow and that decision is made for you. We do our best to provide a balance that fits 90+% of our users but in cases such as yours, alternatives are available.
Hopefully we can improve this in the future but for the time being the options provided to alter this conflict is what we can provide.0
Post is closed for comments.
Comments
4 comments