Capture One 20 slow with extensive healing or cloning
I'm on a six core i5-8600K @3.60GHz, 32GB Ram and a NVIDIA Quadro P400 Grapics Card. Just did a job with extensive use of the new healing tool, sometimes cloning. I worked with sessions on files from my Nikon D850 on a Samsung 970 EVO SSD.
With just a few healing or cloning spots everything went ok and all was snappy. But if the healing and cloning grew extensive I reached a point on every file, where the work grew into pain. The software was thinking and thinking and I had to wait long times to go on with my editing. In some cases I set up a second heal layer for further retouching, but only until it went slow again.
Any ideas out there? Could it be the graphics card that is too slow for healing and cloning?
-
It may be worth getting your task manager up when trying these things, as it will give you a good idea if there is particular pressure on your computer resources.
I can say that I have had pictures with maybe 50 dust spots that needed fixing, don't ask, that what I get for not cleaning my sensor for a very long time, but I did not have any particular performance issues. Having daid that I have an i7, with 64gb and a ti1660, so not like for like hardware for comparison. I suppose what I am saying is that it could be a resource issue...
How many repairs/clones did you do?
0 -
I did look at at the task manger, but only Capture One showed a heavy consumtion of computer resources. All other tasks were ok and I had about 16 GB of RAM left.
I dont't think that the lag with the healing and retouching is related to my i5 cpu, because there is not much difference between my i5 and a i7. The only thing a i7 does better is hyperthreading, this is not available on my i5 and I have to go with the six cores it delivers. Never had a problem of this kind with Photoshop or any other software. Regarding Lightroom there is no speed increase in Capture One, Lightroom too is a slouch in healing and retouching.
I dind'nt exactly count the number of rapairs and clones, maybe I should do next time. I assume that it started to get slow with about 30 or more repairs. And if I created a new repair layer the "first" repairs on that layer were easily applied. Switching to a repai layer with heavy retouching brought the problem up again. Sometimes I even closed Capture One and started it again to get bach to work.
My assumption that it could be the graphics card is that I never had a fast card (I'm not a gamer). I bought the Quadro P400 for it's availability of getting 30 bits with Photoshop. The P400 has only 2 GB of RAM, maybe this could be the bottleneck.
Maybe some Caputer One official can comment about, if the graphics card could be the cause?
0 -
@Jürgen
This is mainly a User to User forum with some input and admin from the front line support staff.
I think if you want a comment about performance your best option would be to use the "Submit a request" option and create a Support Case for a personal response.
C1 might like to have the details of you system to compare it to other similar configurations they may have information about. Also they are very likely to ask for the log files in order to check for performance related messages.
I think if you are undertaking that many repairs and using multiple layers you are definitely deep into Photoshop territory. Since it seems that you have PS and are proficient in using it is there a reason for keeping the repairs in C1 rather than using PS?
0 -
@SFA
Thank you very much for your clarification, I wasn't aware of that. My apologies.
One reason for keeping the repairs in C1 was that it worked astoninglishy well compared to the heal brush in Photoshop. But the main reason is my desire to keep all editing in one place, if possible. To switch between apps isn't really comfortable, even if C1 can hand over files to PS. I dit that, of course, but came to situations where my customer asked for adjustments that were better done on the original RAW file than on the TIFF variant with the retouching. Furthermore, if there is a feature offered, I like to use it if it is supposed to add to my workflow. And regarding C1's marketing ("This new tool is every retoucher’s dream", https://learn.captureone.com/blog-posts/this-new-tool-is-every-retouchers-dreamhealing-brush-update/) this dream went into the wrong direction for me...
0 -
@Jürgen
Well that's a great rationale Jürgen.
Probably the best and most complete reasoning I have ever read in the forum.
I agree with your points although the observation about the heal brush compared to PS was a surprise. That said I have no experience of PS especially in recent times.
Depending on the sort of things your healing and cloning is doing - probably especially healing - the system could be trying to perform a lot of work and that sort of activity will tend to reach limitations that have a clear effect on performance.
There may be workflows that can optimise the results. Or hardware settings. Or other recommendations that would help. I would expect the C1 team to have some sort of previous experience that may help.
Of course some users may also have some real world experience they can share using similar configurations and workflow - but they may not be regular visitors here and their operation and hardware may not be directly comparable.
Hopefully some will see this thread but I would also hope that contacting C1 Support and working through them will find an improvement and maybe lead on to the developers finding additional ways to enhance performance for requirements like yours.
The log files may give some clues but I would suspect that there is a good chance that for this sort of process recording reading the log file entries usefully may require a technical understanding of the way the processes are intended to work and where any probable limitations may be expected.
0 -
@Jürgen
I decided to make a very quick and completely random experiment.
Slow down was observed after about 20 healin actions. A couple of corrections were applied but not visible as healing activities (no circles and arrows) just as I was approaching that number.
Adding more heals saw a message window appear with a "processing progress" bar. I stopped at about 30 by which point the process speed reduction seemed to have stabilised.
Although slower by 30 than at the start it was perhaps 1 or 2 seconds per "heal" and on balance I did not think that was too bad for what I was doing but I could imagine that for some activities that might seem to be unacceptably long.
0 -
Hi Jürgen,
we could talk in German too but others would not understand. ;)
On same reasons I do retouching on most images in Capture One too. Up to three layer (nescessary when points are to near to an other go get seperated points). Even when only one layer (dust) and many (far more than thirty) healing spots I have no loss of performance.
I am working with an Intel i7-9700K an 32GN RAM, my graphic card is a GTX-970 with 4GB RAM.
Kind regards Ernst
0
Post is closed for comments.
Comments
7 comments