Memory consumption + CE masks + Open CL problem
Hi,
while C1 8 was very well behaved on my machine (Retina MacBook Pro 13" 2014, El capitan), I'm experiencing a number of issues with C1 9 :
1) I'm seeing rather high memory consumption, even when not batch building previews. The following picture is with C1, Lightroom and Apple Photos all opened on the same file (a 5DS R raw file). LR and Photos behave normally as they usually would (and I can't help but notice how efficient Photos is), but C1 9 consumes a ton of memory, and a lot more than C1 8 would with the same file (a little less than LR usually).
http://img11.hostingpics.net/pics/708051C19memoryproblems.jpg
Update 1 : I've seen in the windows forum that apparently there is a leak with Canon files. I don't know if it applies to the mac as well, but as far as I'm concerned the memory consumption issue happens even when not manipulating Canon raw files - but I do have Canon files in my catalog.
Update 2 : as far as I'm concerned 9.0.1 makes memory consumption more stable over time. But at least as reported by Activity Monitor, I still find it a bit high.
2) When I turn OpenCL "display" (not "processing") on auto, a very strange behaviour happens. When adjusting settings, sometimes, with some variants, either the whole picture turns fully black when dragging sliders (and returns when releasing the slider), or, the masked area shows no change when dragging sliders while the unmasked area looks less contrasty. In both cases releasing the slider gives me the intended output, but it's during dragging that this weird behaviour happens. Turning OpenCL "display" off solves the issue. I didn't experience it with C1 8.
Update : Still there with 9.0.1. In addition I've now got a variant of a file that systematically triggers the viewer's blackout, but I don't know yet what in that variant, and not the others, triggers this phenomenon.
3) When closing C1, all masks created via the colour editor are deleted. The layer remains, but the mask no longer exists.
Update : I haven't noticed that problem anymore since I wrote this post.
There are also a few other bugs I've noticed :
4) Sometimes, I can't seem to be able to select a adjustment picker tool when clicking on the appropriate icon in the tool UI. I need to use the toolbar instead. This also happened with C1 8 and the color editor picker, but now also happens with C1 9 in the curve tool.
Update : still there with 9.0.1 (but that also was a C1 8 bug anyway).
5) Perhaps this is by design : the toolbar takes on a darker shade of grey when Capture One isn't in the foreground. I don't care that much about it though 😄.
Update : according to Phase One, this is by design and happens when the app is in the background. One of the problems though it's that it's quite buggy. For example, when opening the application, even of CO is in the foreground, the toolbar remains dark, until I resize CO's window.
Have you noticed something similar ? Do you think I could have improperly set up my computer and that this would be the cause of the issues I'm noticing ?
while C1 8 was very well behaved on my machine (Retina MacBook Pro 13" 2014, El capitan), I'm experiencing a number of issues with C1 9 :
1) I'm seeing rather high memory consumption, even when not batch building previews. The following picture is with C1, Lightroom and Apple Photos all opened on the same file (a 5DS R raw file). LR and Photos behave normally as they usually would (and I can't help but notice how efficient Photos is), but C1 9 consumes a ton of memory, and a lot more than C1 8 would with the same file (a little less than LR usually).
http://img11.hostingpics.net/pics/708051C19memoryproblems.jpg
Update 1 : I've seen in the windows forum that apparently there is a leak with Canon files. I don't know if it applies to the mac as well, but as far as I'm concerned the memory consumption issue happens even when not manipulating Canon raw files - but I do have Canon files in my catalog.
Update 2 : as far as I'm concerned 9.0.1 makes memory consumption more stable over time. But at least as reported by Activity Monitor, I still find it a bit high.
2) When I turn OpenCL "display" (not "processing") on auto, a very strange behaviour happens. When adjusting settings, sometimes, with some variants, either the whole picture turns fully black when dragging sliders (and returns when releasing the slider), or, the masked area shows no change when dragging sliders while the unmasked area looks less contrasty. In both cases releasing the slider gives me the intended output, but it's during dragging that this weird behaviour happens. Turning OpenCL "display" off solves the issue. I didn't experience it with C1 8.
Update : Still there with 9.0.1. In addition I've now got a variant of a file that systematically triggers the viewer's blackout, but I don't know yet what in that variant, and not the others, triggers this phenomenon.
3) When closing C1, all masks created via the colour editor are deleted. The layer remains, but the mask no longer exists.
Update : I haven't noticed that problem anymore since I wrote this post.
There are also a few other bugs I've noticed :
4) Sometimes, I can't seem to be able to select a adjustment picker tool when clicking on the appropriate icon in the tool UI. I need to use the toolbar instead. This also happened with C1 8 and the color editor picker, but now also happens with C1 9 in the curve tool.
Update : still there with 9.0.1 (but that also was a C1 8 bug anyway).
5) Perhaps this is by design : the toolbar takes on a darker shade of grey when Capture One isn't in the foreground. I don't care that much about it though 😄.
Update : according to Phase One, this is by design and happens when the app is in the background. One of the problems though it's that it's quite buggy. For example, when opening the application, even of CO is in the foreground, the toolbar remains dark, until I resize CO's window.
Have you noticed something similar ? Do you think I could have improperly set up my computer and that this would be the cause of the issues I'm noticing ?
0
-
I have had to turn off OpenCL for Display as it makes bursting very laggy.
my machine is an iMac5K late 2015 with 8GB ram and 4Ghz processor and 4GB GPU0 -
Update :
since I don't use Capture One as a catalog, I uninstalled the software and deleted my previous catalog (in which I only have temporary files, so no big deal). After this, the OpenCL problem is gone.
But I still have an absolutely massive memory consumption which is wrecking havoc on my computer, and the local picker tool problem persists.0 -
Update 2 :
My OpenCL problem is gone, but now I have an even bigger one : when leaving C1, all masks created via the colour editor tool disappear. Another user in a French forum has the exact same problem.0 -
Update 3 : for some reason the OpenCL problem is back. I'm 100% positive it was gone after a fresh re-install, but now it's back. I haven't changed anything in the preference pane.
The mask disappearance problem is still there, as well as the excessive memory consumption issue.0 -
Hi -
New user to Capture One Pro and just testing the latest Mac version (9.0.0.110) to determine if this will meet my migration needs from Aperture. My needs are not as great as many of you, but I have 18,000 images to migrate from Aperture and do quite a bit of Sports photography work and need a solid workflow tool.
I opened a very modest Session with 421 images from a Canon 7D Mk I. I am running on a MBP Retina with 16 GB and a large SSD. After editing 2 photos as part of using a tutorial I let the application sit on an otherwise unused system. After 5-6 hours of sitting, I resumed, only to find the application so slow as to be unusable for any edits / updates. I was testing with Local Adjustments, perhaps that is one of the keys to the issue I encountered.
I checked memory usage and found that with no other applications running and only the one test Session open, the memory usage for Capture One Pro 9 was 25.92 GB! The system was paging quite a bit.
I shut down the application and then reopened. The same Session was opened (only thing I have!) and memory usage was a more modest 4.94 GB. Things are very speedy again.
I then created a single Local Adjustment Layer on one photo and checked memory usage again. Now memory usage had increased from 4.94 GB to 6.21 GB. I added another layer and usage when to 6.48 GB.
I tried the same thing on a new pic and usage went from 6.48 GB to 6.64 GB.
I'm not the experts that many of you are, but I wanted to provide info on my results on a Mac.
I am running El Capitan 10.11.1 (new update available but not applied).
Need to find solution for workflow since El Capitan broke Aperture for me (OnScreen Profiling causes a white haze on all photos (can be eliminated by turning on On Screen Profile, but then I lose the benefits of it).0 -
Make sure you enter your issues with PhaseOne support. That's the only way you are guaranteed to get these issues on someone's radar.
BTW, I've noticed performance is horrible on my 6-Core Mac Pro with Dual D500 GPUs and 32GB of RAM... this machine should absolutely rock any imaging software, but C1 brings my $5K computer humbly to it's knees. I really wish PhaseOne would focus the next few months on just bug fixes and performance.0 -
This post might be interesting:
When I posted it I assumed the problem was all due to my using OpenCL on my Mac Mini. Since the Mini does not have a separate video card and its associated extra memory, I thought this warning applied only to the Mini. Perhaps that is wrong and there is a general problem.0 -
HAs anyone been seeing the same memory usage with the latest 9.01 release?
I was testing with it today and saw some serious memory usage still
When I opened Capture One Pro 9.01 with no Session or Catalog active, memory usage was 2.44 GB.
When I opened Capture One Pro 9.01 with a Session and a photo selected, memory usage was 3.06 GB.
After editing 3 pictures in the session, memory usage was 5.6 GB. I was doing other things and this tool place over 30 minutes or so.
I restarted and did it again, but faster. I made the same type of edits on 5 pictures in a new editing session (meaning working on the pictures, not creating a new Session in Capture One Pro) and checked memory usage, I was only at 3.06 GB (seems like a magic number).
After then letting it sit for 10 minutes and doing nothing, memory usage was now 3.44 GB.
Couple of minutes later, still no edits, usage was 3.49 GB.
After that it kept climbing a bit.
That's what I am seeing.0 -
On viewtopic.php?f=61&t=21647 I have reported high memory usage and other users have seen similar behavior. Using some of the new keyword features is effectively impossible using a large catalog. According to posts on the windows forum, also the windows version still seem to have memory issues with 9.0.1. 0 -
As far as I'm concerned since 9.0.1 memory usage is more stable. It doesn't seem to go up and down at random like it used to. It never really exceeds 6 Gb "memory" (as indicated by Activity Monitor) and 3.5 Gb "real memory".
I still find it rather high and wouldn't mind seeing it reduced a little further.
The OpenCL problem is still there. On one of my variants (and not the others of the same file), it's systematically there at all time - therefore reproducible. But I don't know what in this precise variant triggers the viewer blackout during adjustments, and I'm not even sure it's something in particular, perhaps a combination of adjustments.
Otherwise the rendering speed in quite impressive as far as I'm concerned, particularly when using a lot of layers, compared to LR that seems to quickly crumble under the weight of a similar number of local adjustments.0 -
[quote="NN634739876592987355UL" wrote:
But I don't know what in this precise variant triggers the viewer blackout during adjustments, and I'm not even sure it's something in particular, perhaps a combination of adjustments.
I have been forced to turn OpenCL off on my Mini for both Display and Processing in 9. I would like to turn it back on, but then I (intermittently) get screen blackouts when adjusting and/or image blackouts when processing. No problem with OpenCL turned off [or in version 8 with OpenCL turned on], but it is a bit annoying having to do that.0 -
Capture One 9 is using 9,62 GB of my 12 GB memory, 3,51 GB in compressed memory, and 170 threads. It works fine on my machine but I must admit I find these figures way too HIGH... 0 -
Remembering these memory issues from CO8, I still gave the CO9 trial a try. So far, so good for me. I haven't noticed the excessive usage that others have described in various threads. But I also shoot Nikon and one issue seems particularly related to Canon RAW files. I have not turned on OpenCL either, since I've had issues with it in CO8 and so far, it's been doing fine without it. Fine in the sense of, it's still guzzling up about 8GB of memory which is way too much what it should be, but at least it's staying in that range and doesn't go any higher during longer usage... 0 -
To resolve all OpenCL issues (esp. if upgrading from older version or replacing video card/hardware) open "/Users/Shared/Capture One/ImageCore" and remove contents.
Required file(s) will be generated on the next program start and you can safely enable OpenCL for display and enjoy no glitches.0
Post ist für Kommentare geschlossen.
Kommentare
14 Kommentare