what is see is not what i get - RESOLVED
hi,
i've been using CO7 on mac now for about 6 months and am very happy with the results, esp. in comparison with LR. however today i figured that the output does not match the screen display exactly. i tried all versions of JPG/TIFF, bit depth and colour profiles - however the results look always not as crisp and sharp as in the CO display.
left side: CO 7.2.2, right side: PS CC 2014. i could reproduce the same in other viewers like built in preview or pixelmator.
does anyone experience the same? thanks for your feedback,
regards,
tim
PS: probably needless to say, but yes, both are 100% crops from a 12MP (3Ds) sensor.
http://punktrot.de//scratch/leftCO_rightPS.png
http://punktrot.de//scratch/settings.png
i've been using CO7 on mac now for about 6 months and am very happy with the results, esp. in comparison with LR. however today i figured that the output does not match the screen display exactly. i tried all versions of JPG/TIFF, bit depth and colour profiles - however the results look always not as crisp and sharp as in the CO display.
left side: CO 7.2.2, right side: PS CC 2014. i could reproduce the same in other viewers like built in preview or pixelmator.
does anyone experience the same? thanks for your feedback,
regards,
tim
PS: probably needless to say, but yes, both are 100% crops from a 12MP (3Ds) sensor.
http://punktrot.de//scratch/leftCO_rightPS.png
http://punktrot.de//scratch/settings.png
0
-
What software is your monitor profiled in? 0 -
hi jim,
the monitor is profiled with Datacolor Spyder Elite 4. the profile is accordingly set in the applications. i'm happy with colour rendition though.
thanks,
tim0 -
For the sake of testing do you see a difference with a default profile? 0 -
i did not find any difference other than shifted colours. sharpness/microcontrast still is significantly different in the processed version vs. the CO display... were you able to reproduce such differences on your end? (sharpening was applied globally amount 250; 0,5 radius; threshold 0.😎 0 -
Is Sharpening enabled or disabled in the Adjustments tab? 0 -
sharpening is applied on processing. the option to "disable sharpening" in the output tab is NOT checked. i also tried processing with and without sharpening to make sure the checkbox is working fine. unfortunately all is well with the checkbox... 0 -
hi jim, any more news on the topic? could you reproduce the issue? would anyone else be so kind and do a short test? i need to be able to trust the CO display...
thanks,
tim0 -
If the things I have suggested did not work then fire over a support case with RAW file (packed as EIP) and we will try to reproduce with your specific file.
As it is I have no issues locally with my own set up.0 -
would love to do so, however there is no EIP option for me in CO7... pls. advise. 0 -
i continued testing today and found
- the issue shows consistently with any of my files (.nef)
- only using recipes there is a consistent deviation to the CO display in regards to sharpness, no matter the file type or bit depth
- when using the "export" function for variants the rendered file is 100% perfectly resembling the CO display.
to me this clearly indicates this annoying issue to sit "within" CO.
left side: processed output using recipe, right side: export variants with exact same settings.
http://punktrot.de/scratch/recipe_vs_exportvariant.png
http://punktrot.de/scratch/test2.png0 -
[quote="NN635290382058771250UL" wrote:
would love to do so, however there is no EIP option for me in CO7... pls. advise.
You can pack an image to EIP (from File menu) when you are running a session. From a catalog this feature is not available.0 -
Each recipe has an option to disable sharpening. This skips the processing step in the pipeline, however the preview retains the sharpening settings. Is this enabled for your recipe? 0 -
hi jim,
the sharpening option has already been discussed and clarified. pls. see my statement above:
"sharpening is applied on processing. the option to "disable sharpening" in the output tab is NOT checked. i also tried processing with and without sharpening to make sure the checkbox is working fine. unfortunately all is well with the checkbox..."
the results are as expected.
thanks,
tim0 -
hi,
the proposal from PO support to play around with the OpenCL hardware acceleration did the trick. when OpenCL for processing is set to "auto" i got differences, when set to "never" the outpout was bitperfect 100%. the settings for display did not affect the output and at least for me can be kept at "auto".
i'm happy this issue got resolved - howevever there is something wrong behind the curtains... PO support claims its a local issue - and it is probably related to my very specific config. lesson learned: openCL seetings are turned OFF by default - obviously for a reason.
thanks to the PO support team for premium support and response times.
tim0 -
hi,
just to follow up on this issue with some more clarification let me paste the original hint from support:
Another thing you can test is to find the users systemdisk/shared/Capture One/image core/ folder and look for the ICOCL.bin file (a precached OpenCL file) that you can delete so Capture One can rebuild it the next time it launches.
it turned out that deleting that particular cache file and having it rebuild fixed the issue with OpenCL support set to auto for display and processing. (seemingly the export variant option does not rely on it, but the recipe driven processing does). current assumption is that the cache was corrupted based on a recent upgrade or my specific setup (external monitor on macbook air 13). support confirmed there is an acknowedged issue in this regards which is awaiting a fix from apple side. latest/later versions of mavericks should not show this behaviour.
ever since deleting the cache file i did not have any issues.
thanks,
tim0
Post is closed for comments.
Comments
15 comments