File /Preview /Image handling
I just love Capture One and have been using it for years, but I have one gripe: it appears to have very poorly designed file /preview /image handling software. When importing images it seems to hog the cpu totally, and takes forever to complete an import and generate previews. Another very irritating thing since version 20 is the fact that during editing (after a bit of editing time) the active preview picks up artefacts (rectangles from previous images or rectangles with lines or patterns), or when I edit an image with a 3rd party software like DeNoise, the temp file created is corrupt and contains artefacts when it is displayed in DeNoise. When this happens, it will do it every time I try and the only way to rectify it is to shut down and restart Capture One. Does anyone have a work-around for this? All my software is latest version on a machine with i7 (8th gen), 32GB Corsair DDR4 RAM, GeForce GTX 1050tx graphics card.
-
Alan,
the appearance of artefacts is most often something to do with the use of the available GPU facilities.
This in turn is most often the result of some sort of mismatch between Windows, the GPU driver software and C1.
You can easily check this (you may have done so already) by turning off Hardware Acceleration in the Preferences.
The latest and greatest drivers for the GPUs are usually, but not always, the best option. However, before heading out on that sometimes long path of possibilities it would be best to know whether setting HW acceleration to "None" appears to resolve your problem.
Does your system successfully work with the built-in Intel software-based GPU as well as the GTX? (By that I mean are both devices identified and do they then both end up with the "kernels" built successfully to allow them to be involved in the processing process?
As for importing, I think C1, as with most software, will attempt to time share CPU time (and memory, etc.)
Importing is something of a linear process and if the Activity window pops up you should see the numbers being reported giving some idea of how the import is progressing, how the preview build is going and anything else that might be going on.
That C1 grabs as much CPU resource as it can use suggests that the system can feed things to it quite swiftly which seems like a positive result.
However, the ultimate performance for what is likely to be a data-intensive activity in terms of transfer between "disks" and through the system devices, memory, etc., is influenced by many other factors. All one can do is try to use the Windows diagnostic tools to see whether things look "reasonable". Or, using some facilities that some hardware manufacturers now seem to offer, get the system to report on itself regarding how what bottlenecks it has and how it can be improved.
Bear in mind the import and preview processes are separate, preview generation following on from a successful import, and somewhat dependent on what you asking the process to do in terms of processing. Also where the files and previews, etc. are to be stored will have an effect.
You do not have to wait for an import to finish before you start editing. So even if importing a very large number of images things should be reasonably productive. It is possible that working with a session (as I do) will be speedier than adding things to a large, pre-existing catalog.
0 -
Thanks for that. When I write software that is cpu intense such as image processing and analysis, I always time the loops so that there is a bit of breathing space for the CPU without having to allocate specific threads for each process, and I have noticed that many commercial software apps just give everything to the cpu without any thought about timing, which fouls up the software in use. It seems that C1 is quite intense when using the GPU, so I think I'll try a new GPU with more working RAM and clock-speed. Thanks again.
0
Post is closed for comments.
Comments
2 comments