Very slow when making adjustments...
Hey guys,
So I know there are a number of threads about CO9 running slow, but I wanted to add my experience in also, in case someone has some ideas..
I've noticed recently (I can't tell when it started though!), that Capture One iPro 9 is running really really slowly when I'm making local adjustments to an image. I tend to put the mask on, so i can see where I'm 'painting'. I can drag my brush along the image, then wait anything between 5-15 seconds for the mask to catch up before I can do anything else. I can't even toggle off the brush until it's finished its last action.
I've tried a number of things:
Checked that OpenCL was enabled for both options
Checked that my preview size matched the screen size
Removed Filters tool (I read on the forums this could be causing the issue!)
Removed non-essential tools from each section, just in case
Created a new catalog with one image in
None of that made any difference. I did try the same image in Lightroom, to see if the issue was Capture One, or my Mac, but LR was absolutely fine, so something is definitely going on with Capture One.
Does anyone have any wisdom on this? Thanks in advance.
So I know there are a number of threads about CO9 running slow, but I wanted to add my experience in also, in case someone has some ideas..
I've noticed recently (I can't tell when it started though!), that Capture One iPro 9 is running really really slowly when I'm making local adjustments to an image. I tend to put the mask on, so i can see where I'm 'painting'. I can drag my brush along the image, then wait anything between 5-15 seconds for the mask to catch up before I can do anything else. I can't even toggle off the brush until it's finished its last action.
I've tried a number of things:
Checked that OpenCL was enabled for both options
Checked that my preview size matched the screen size
Removed Filters tool (I read on the forums this could be causing the issue!)
Removed non-essential tools from each section, just in case
Created a new catalog with one image in
None of that made any difference. I did try the same image in Lightroom, to see if the issue was Capture One, or my Mac, but LR was absolutely fine, so something is definitely going on with Capture One.
Does anyone have any wisdom on this? Thanks in advance.
0
-
What machine are you running CO on ? 0 -
I'm using a mid-2014 MacBook Pro - 2.2gz Core i7, with 16GB DDR3 Ram. Really, I wonder if it's something to do with the latest update, as previous versions *seem* to have been better, and everything is fine with Lightroom 0 -
I've seen it through several versions of CO on a mid2009 MBP 2.8GHz DualCore 8GB and a mid2014 MBPr 2.8GHz i7 16GB. It occurs randomly, every once in a while, and is not reproducible.
CO is drawing the mask circle by circle onto the screen, slowly walking the path the cursor went. It can take 15 to 20 seconds on long walks. And the very next day, CO flies drawing the mask.
No idea how to get into that mode, or out of it without restarting.
Regards,
Hans0 -
I also wonder whether Capture One should be using so much memory at 3.36GB / 1.84GB Compressed? Seems high to me? 0 -
[quote="HansB" wrote:
I've seen it through several versions of CO on a mid2009 MBP 2.8GHz DualCore 8GB and a mid2014 MBPr 2.8GHz i7 16GB. It occurs randomly, every once in a while, and is not reproducible.
CO is drawing the mask circle by circle onto the screen, slowly walking the path the cursor went. It can take 15 to 20 seconds on long walks. And the very next day, CO flies drawing the mask.
No idea how to get into that mode, or out of it without restarting.
Regards,
Hans
Please contact Support. 20 seconds is obviously way too long for mask drawing.0 -
[quote="mikebeecham" wrote:
I also wonder whether Capture One should be using so much memory at 3.36GB / 1.84GB Compressed? Seems high to me?
That is a perfectly normal usage-level.0 -
[quote="Christian Gruner" wrote:
[quote="HansB" wrote:
I've seen it through several versions of CO on a mid2009 MBP 2.8GHz DualCore 8GB and a mid2014 MBPr 2.8GHz i7 16GB. It occurs randomly, every once in a while, and is not reproducible.
CO is drawing the mask circle by circle onto the screen, slowly walking the path the cursor went. It can take 15 to 20 seconds on long walks. And the very next day, CO flies drawing the mask.
No idea how to get into that mode, or out of it without restarting.
Regards,
Hans
Please contact Support. 20 seconds is obviously way too long for mask drawing.
Thanks, Christian. I will do so.
Regards,
Hans0 -
Christian,
When that gets figured out for you, would you mind posting what you found to be the cause. Mine isn't 15-20 seconds, but still unacceptably slow. I didn't use to be this way...0 -
I filed a support case for slow mask drawing today. I'm still looking for a way to reproduce it, and I'll provide a screen recording next time it happens.
Regards,
Hans0 -
Hans,
I have this problem consistently with some images (EOS 5DSR RAW) when I'm drawing complex masks. Simple ones are fine, but when I try to follow intricate shapes, C1 9.2.1 seems to freeze and (via iStat Menus) I see that there's a lot of CPU activity and an incredibly HUGE amount of disk activity. Page/swap stuff? This happens on 2 Macs running 10.11.6. One (Mac Pro has 32 GB of RAM and the other (MacBook Pro) has 16 GB. Capture One's hardly using any RAM on either of these, which really surprises me. C1 doesn't seem to make very good use of available memory, but it sure is hitting my SSDs up hard.0 -
Hi Nature Isme,
I have this problem just every once in a while, with 10MPix 1Dm3 as well as with 18MPix 1DX images, and even when just masking an almost straight horizon on a sunset image. Removing the layer, drawing again, same problem, over and over. After restarting, same image, same mask (as good as I can draw it), and no problem. I can't imagine why. Usually only Finder and CO are open.
I don't remember seeing anything special in iStat, but I'll check that again the next time it happens.
Memory usage has improved with CO-9. It now allocates memory dynamically with the images viewed. But I'd say it could still be smarter in releasing and reusing memory. For example, CO's memory footprint (with currently no session open) still grows and grows when opening and closing sessions sequentially.
Regards,
Hans0 -
Long shot...
I've had this as well some time ago, very badly, and I found a very odd scenario in which it occured.
I had a number of images in a catalog from the same shoot and some were OK to handle, others would send the CPU through the roof. It turned out that the 'heavy' images were the ones on which I painted the adjustment layers masks with an old Wacom Bamboo tablet; they also had some cropping (almost every image was cropped). On those images, when moving the mouse over the image, C1 showed a spinner where normally the RGB readout is. Oddly enough, when I selected the crop tool, the CPU went back to 0; but selecting the pointer made the CPU go up to 100 again. I then cleared the cropping, and everything went back to normal. I redid the crops, and from then it stayed normal.
Oddly enough, many images in the same catalog, also cropped, did not have this problem. Those images had their mask painted on with the mouse.
I must say that I wasn't able to get into a similar state thereafter. I tried every combination of layers, cropping before and after,. etc, but C1 kept on behaving OK. Sometimes a bit sluggish, but never like that again. All this was on a Macbook Pro mid 2010.
Give it a shot, try resetting the crop and maybe, who knows, the image is 'repaired'...
Cheers,
Peter.
P.S. I did report this in March 2016.0 -
i hope they get this sorted soon. At this point, I'd much rather take the lesser RAW capability of Lightroom, and be able to make adjustments, than stick with Capture One and spend more time trying to get it work correctly. 0 -
OK...so I've discovered what is causing such a lag when making adjustments, and it's all to do with the Manufacturer's profile within Lens Correction.
When I set it to 'Generic', everything works really quickly. Mask on, brushing, and Capture One is really really quick. The moment I put it back to Manufacturer Profile, it slows right down again.
Ordinarily I wouldn't mind, but since Fuji bake their distortion settings into the raw file, turning the profile to 'Generic' means that I get really bad barrelling on the image.
Not sure if anyone has experienced this, but if so do you have any pearls of wisdom which will help?
Thanks0 -
[quote="mikebeecham" wrote:
OK...so I've discovered what is causing such a lag when making adjustments, and it's all to do with the Manufacturer's profile within Lens Correction.
When I set it to 'Generic', everything works really quickly. Mask on, brushing, and Capture One is really really quick. The moment I put it back to Manufacturer Profile, it slows right down again.
Ordinarily I wouldn't mind, but since Fuji bake their distortion settings into the raw file, turning the profile to 'Generic' means that I get really bad barrelling on the image.
Not sure if anyone has experienced this, but if so do you have any pearls of wisdom which will help?
Thanks
There are many factors that slow down C1 to the point of crawling. Sometimes is the lens profile, other times ( often) is a style you added. From what I understand there are still parts of the code that do not take advantage of CL and so if a profile or a style uses them, the whole program slows down. Perhaps some one from PO might want to comment on this... 😂 yea right. Learn how to live with it0 -
[quote="alececco" wrote:
[quote="mikebeecham" wrote:
OK...so I've discovered what is causing such a lag when making adjustments, and it's all to do with the Manufacturer's profile within Lens Correction.
When I set it to 'Generic', everything works really quickly. Mask on, brushing, and Capture One is really really quick. The moment I put it back to Manufacturer Profile, it slows right down again.
Ordinarily I wouldn't mind, but since Fuji bake their distortion settings into the raw file, turning the profile to 'Generic' means that I get really bad barrelling on the image.
Not sure if anyone has experienced this, but if so do you have any pearls of wisdom which will help?
Thanks
There are many factors that slow down C1 to the point of crawling. Sometimes is the lens profile, other times ( often) is a style you added. From what I understand there are still parts of the code that do not take advantage of CL and so if a profile or a style uses them, the whole program slows down. Perhaps some one from PO might want to comment on this... 😂 yea right. Learn how to live with it
Well, one thing I can't do is learn to live with it. We're talking significant slowdown. Not just a minor decrease in speed, but a slowdown which results in a long period of waiting for Capture One to 'catch up' with what I'm doing. For the price you pay for the software, that kind of waiting around is simply unacceptable, With regards to the different factors affecting performance...I totally agree with you. In my case, however, it's the lens profile setting that is causing my slowdown.
Cheers0 -
[quote="alececco" wrote:
[quote="mikebeecham" wrote:
OK...so I've discovered what is causing such a lag when making adjustments, and it's all to do with the Manufacturer's profile within Lens Correction.
When I set it to 'Generic', everything works really quickly. Mask on, brushing, and Capture One is really really quick. The moment I put it back to Manufacturer Profile, it slows right down again.
Ordinarily I wouldn't mind, but since Fuji bake their distortion settings into the raw file, turning the profile to 'Generic' means that I get really bad barrelling on the image.
Not sure if anyone has experienced this, but if so do you have any pearls of wisdom which will help?
Thanks
There are many factors that slow down C1 to the point of crawling. Sometimes is the lens profile, other times ( often) is a style you added. From what I understand there are still parts of the code that do not take advantage of CL and so if a profile or a style uses them, the whole program slows down. Perhaps some one from PO might want to comment on this... 😂 yea right. Learn how to live with it
OpenCL is not a "fix" for everything to do with speed.
If allows the potential for load sharing where parallel processing is both viable and will, on balance, benefit from the extra work involved with splitting processed apart, processing and then putting them back together again.
Not all process will benefit form attempted parallel processing even if we can assume that all implementations of OpenCL are equal in the third party hardware and software areas.
Grant0 -
OK, so I have more information regarding the slowness of making adjustments.
When I take photos using my Fuji X100, everything works as normal. When I use my Fuji X-T1, either coupled with my 35mm F2 or 27mm F2.8 lens, I noticed the slowdown.
Is there an issue with the profile of the camera here, or the lenses? The lens is a fixed lens on the X100, so seems to be classed as maybe a 'Generic Fuji Profile'?
Not sure...I wonder if there is anyone from PhaseOne around the forums who might be able to comment on this, or shed light on the issue?0 -
[quote="mikebeecham" wrote:
OK, so I have more information regarding the slowness of making adjustments.
When I take photos using my Fuji X100, everything works as normal. When I use my Fuji X-T1, either coupled with my 35mm F2 or 27mm F2.8 lens, I noticed the slowdown.
Is there an issue with the profile of the camera here, or the lenses? The lens is a fixed lens on the X100, so seems to be classed as maybe a 'Generic Fuji Profile'?
Not sure...I wonder if there is anyone from PhaseOne around the forums who might be able to comment on this, or shed light on the issue?
There is a very logical explanation for this:
X100 is Bayer-based, thus it can use OpenCL
X-T1 is Xtrans-based, which cannot use OpenCL. That makes it slower to adjust and process, as it then uses the CPU instead.0 -
Thanks for the update...
So, even more curious, I've just bought the new Fuji 23mm F2 lens and, from what I can see, I don't have the same issues with local adjustments that I do on the 35mm F2..or at least it's definitely not as bad. Could there be an issue with the lens profile in Capture One perhaps?0 -
FWIW, I have the same problem. With an initial adjustment layer edit on a RAW file, there's a brief lag, which I can live with. However, if I 'edit with' in Photoshop and then save and return to CO and attempt to make another adjustment layer edit, the delay is to the point where I no longer bother with it. All my adjustment layer edits have to be and are done on the original RAW file/variant, or not at all.
Hopefully, the next iteration will have a more robust process engine.0
投稿コメントは受け付けていません。
コメント
21件のコメント