Another display garbage with Update 13.1.3.13
Hi altogether!
In addition to https://support.captureone.com/hc/en-us/community/posts/360013722838--WIndows-10-2004-C1-13-1-3-13-introduces-new-bugs-in-windows-management there is another display issue may be caused by GPU usage with latest update which i never had seen before. It is "only" a display problem, does not affect exporting the images with which i can see this problems. The following happened (in my case) only when using healing in a bigger area (means not just to get a speck of dust away. And i can see it only in enlarged view with mask "disabled" (not to be seen in red):
Here with heeling masks (two different images, masks in red):
Here with masked "disabled" (same images):
The black area(s) in the first image do only appear in the first image, the second is "only" way to bright in the enlarges view.
Both images will show correctly when not in enlarged view immediately. (Images are not from me, i just have to do the work as photographer wishes.) Not all on all images i can see this behavior, only a few are affected. As theese two are original JEPGs i thought i could have found the cause – wrong: Even from JPEGs only a few show this display error.
As I wanted to check the (before the last update) disabled GPU options, because this can always make troubles, i was astonished: Both GPU options where enabled to "Auto". Does updates do this? As I set them to disabled, nothing changed. New start of Capture One. No change.
Ever seen this problem? Seems to be a problem with GPU (Nvidia 970GTX) too? Any ideas?
Kind regards
Ernst
-
Ernst, since a few days, I experience similar problems.
Did you in the meantime find a solution?
On my end, the heal-layer seems the only item that I can pinpoint as a cause. Hardware acceleration, type of file, camera-profile, GPU-drivers, PC-restart, etc do not seem to solve anything.
-
No, I have no idea and no solution til now. And I am tired creating support tickets and get answers like "Send us an video!" when documented very clearly by screenshots.
> Both GPU options where enabled to "Auto". Does updates do this?
Could be as with one of the most recent updates some issues with OpenCL where fixed. But I do not know really.
Kind regards Ernst
-
Hi Ernst, on my pc / C1, the problem occurs with Hardware acceleration on and off.
I tested the following other variables on images where the issue occurs:
- with heal-layer enabled but not selected - problem occurs
- with heal layer enabled and selected, but not showing mask - problem occurs
- with heal layer enabled and selected, and showing mask, zooming acts as intended
- with heal layer disabled, problem does not occurThe following variables do not seem to have any effect:
- enabling/disabling hardware accelerationd
- type of file (both DNG and TIFFs are affected)
- camera-profile (occurs on files from different cameras, and on files without camera-info embedded)
- closing/restarting C1 has no effect
- restarting PC has no effect
- updating graphic drivers had no effect
- the hardware is the same the whole year, so a sudden incompatibility would be odd.But it would be interesting to know what PC you are running? I have a Ryzen 7 3700X, 32GB RAM, Geforce 1650 4GB.
-
Hi Jaques,
thank you so much for testing. The issue has come with update 13.1.3.13 and was not before. I think we can do not much to fix it.
My PC ist with Z390 chipset, Intel i7-9700K (not overclocked), 32 GB RAM, Geforce GTX 970 (not the best for C1 but was a long time before Capture One).
Kind regards Ernst
-
Hi Ernst, thanks for the details.
It seems we run very different systems, so that makes a hardware cause less likely.
Iteresting that you mention the issue occurred only after the upgrade to 13.1.3.13. On my system the problem first occurred before I upgraded to 13.1.3.13. I hoped that upgrading would solve it, but it did not.
Now waiting for feedback from C1 support.
-
Hi Jaques!
I don't think it has to do with hardware, more with OS Settings and the software itself which is a Mac software without much interest in Windows.
For me the issue(s) appeared after updating. It could have been there before and I didn't mention it at that time.
I hope you will get an useful feedback. Please let me know.
Please sign in to leave a comment.
Comments
7 comments