Capture One Pro 5.0.2 will not render pure white correctly
I'm hoping that someone will be able to shed some light on this rather strange issue.
I'm using Capture One Pro 5.0.2 on Windows 7 x64 and have noticed a problem with the way that C1 Pro renders pure white: basically the maximum RGB numbers that C1 Pro will show is 254 254 254. I have confirmed this problem with both Canon CR2 files and Nikon NEF files.
Even stranger is that if I create a blank white document in Photoshop and then open in C1 Pro , the RGB readings are 252 252 252.
Further to this, on close inspection of the images, there appears to be some form of pixelated noise in all pure white areas, which is possibly contributing to the RGB readings. On processing, this noise stays with the files and can be seen in the output files when viewed in other programs.
I have opened the raw files in ACR and there are no problems with pure white areas of images being anything but 255 255 255, so I know that it is an issue with the way that C1 Pro is rendering the files.
I'm getting frustrated with the problem as I can't see any logical explanation for it. I've been through the process of uninstalling C1 Pro and deleting all program folders and settings, but without success. Has anyone else ever experienced this issue or does anyone know what might be causing the problem?
Any help would be greatly appreciated.
Many thanks
Liam
I'm using Capture One Pro 5.0.2 on Windows 7 x64 and have noticed a problem with the way that C1 Pro renders pure white: basically the maximum RGB numbers that C1 Pro will show is 254 254 254. I have confirmed this problem with both Canon CR2 files and Nikon NEF files.
Even stranger is that if I create a blank white document in Photoshop and then open in C1 Pro , the RGB readings are 252 252 252.
Further to this, on close inspection of the images, there appears to be some form of pixelated noise in all pure white areas, which is possibly contributing to the RGB readings. On processing, this noise stays with the files and can be seen in the output files when viewed in other programs.
I have opened the raw files in ACR and there are no problems with pure white areas of images being anything but 255 255 255, so I know that it is an issue with the way that C1 Pro is rendering the files.
I'm getting frustrated with the problem as I can't see any logical explanation for it. I've been through the process of uninstalling C1 Pro and deleting all program folders and settings, but without success. Has anyone else ever experienced this issue or does anyone know what might be causing the problem?
Any help would be greatly appreciated.
Many thanks
Liam
0
-
Liam,
You have a support case and we are working on providing definitive answers for you. Please provide RAW files and follow up with the supporter.0 -
Waiting for a solution too. Running W7 Pro 64bit and C1 5.0.2 0 -
Janne,
It may be beneficial for you to create a support case too, the more details we have the better we can determine the cause of the issue.0 -
It seems very replicable, Drew - I've just quickly created a 255/255/255 tif, opened it in C1 5 (v5.0.2), and sure enough, I'm getting 252/252/252 as well.
I'm on Win XP, SP2, 32 bit.0 -
Keith,
That's fantastic, hopefully it's easy to solve on your machine or easy to address in the software. Create a support case and provide the details we need, we can move forward from there.
However, seeing as I just created my own 255 tiff in Photoshop and am getting the same values in Capture One (Windows XP) there may be something more at play here. Perhaps the monitor profile? Also, since Capture One is a RAW editing software and processed files aren't exactly it's intended format, there may be a simple error from certain files (just a theory until we can look closer).
Also, a friendly reminder that the system requirements for Capture One 5.0.2 and XP is Service Pack 3.
http://xchange.phaseone.com/HOME/Conten ... 6dc6de4b590 -
Naaah, no support case from me, Drew - for me it's not a "problem" at all, and C1 5 is great on my machine even with SP 2. I just posted to indicate that there is something going on, and that it's easy to duplicate.
I could download SP3, but I'm a "don't fix what isn't broken" kinda guy by choice..! If I do start getting C1 problems, I'll install SP 3 before I bother you, I promise..!
😉
Best of luck with this one.0 -
Maybe Liam could raise a support case and report back here? The systems are close enough, Win7, CS4 and current version of C1. The support case froze on me. 0 -
I created a support case a when I first noticed the problem and the C1 team have confirmed that there is an issue with C1 Pro on Windows 7. Not sure if Vista is affected in same way. Originally thought XP was not affected, following feedback from C1 team, but Keith's post makes me think otherwise.
Support have passed details of the problem on to the testing team now, so hopefully a fix will be found shortly.
A way to clearly see the problem in files (a suggestion from the C1 team) is to open a C1 processed file in your image editing program, open a Levels adjustment dialogue and move the black point slider all the way to the right of the histogram so that it is over the white point slider. Having done this, if you look at any supposedly pure white areas of the image, you will see the problem clearly (view at 100%).
Having carried out some basic testing, I believe that the same issue affects all file types (i.e. RAW, TIF, JPEG) when processed by C1 Pro - just look at the result of processing a blank white TIF through C1 using the levels adjustment method above to view the file.
Hopefully we'll have a progress update soon.
Liam0 -
Perhaps this issue was not identified in time for the development team to resolve it for the release of version 5.1, but I am still disappointed to see that it has not been fixed in the latest release. I am keen to get back to using C1 Pro! 0 -
I have just downloaded C1 Pro 5.1.2 and see that this issue persists.
I do not understand why the developers have not fixed this problem yet as it is a confirmed bug on Windows 7 machines. Is no one else affected by this issue?
Very disappointed to say the least...0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare