Slow processing 16” MBP
-
Yes, indeed. On my MacBook 16 8 Core 2,3 GHz with Radeon Pro 5500M with 8GB everything is super laggy as soon as I use capture one on my external 4k display (Asus PA 329c) connected via USB-C. Lightroom is much faster an not laggy at all.
On the integrated display it is better than on the external display but still laggy and horrible compared to Lightroom.
In the preferences of capture one hardware acceleration both are set to auto. It says hardware acceleration is active. However, in the activity monitor under the tab "Energy" it says that capture one is not using the graphics card. For Lightroom it says that it does use the graphics card.
I have reinstalled capture one having deleted the defaults before - no change. A better performance than Lightroom was one of the reasons for switching and now that.
So far I have not seen any effort on phase one's part to help.
1 -
Using a MacBook Pro 16" 2.3GHz 8 Core i9 - 16GB RAM - AMD Radeon Pro 5500M 4GB RAM and the wheel at top of screen does a lot of spinning with painting a mask or applying a change lagging well behind. Does not make impossible but is a bore to keep waiting!
PRH
1 -
Yes absolutely. I also deleted the ImageCore folder in order to reset the render cache. Nothing changed.
BTW on the activity Monitor displaying the graphics card usage it actually shows minimal usage of the discrete graphics card. But compared to photoshop or Lightroom it is nothing...
For example using photoshop while on battery Mac OS switches to the discrete graphics card, for capture one it does not.i would like a refund
0 -
I have emailed Support to get a response before I renew my subscription!
PRH
0 -
Nothing back from Capture One as yet but following Armin's thought on checking Activity Monitor I found that the AMD Radeon was not being used at all.
Going to System Preferences / Energy Saver I found (top left) that 'Automatic Graphics Switching' was checked. I unchecked this and now Capture One is running as expected on the MBP and the Activity Monitor reports the AMD discrete is bearing the brunt or the processing.
Looks like a Apple problem rather than Capture One.
PRH
0 -
A little more testing;
1. Problem is specific to Capture One, other Apps use discrete card as expected.
2. Unchecking and then checking again and Capture One uses discrete card as expected. Restart Mac with option checked and back to slow processing with only Intel graphics being used.
It would be reasonable to suggest that Capture One has an issue with this setting?
For the foreseeable I shall leave the setting unchecked and hope that Capture One can offer an explanation!
PRH
0 -
Has this been solved now? I'm interested if C1 on MBP is performing well or if I should stay with Windows only.
0 -
I figured out a while back what seemed to be causing the issue on my end. In the ‘process recipe’ tool window if you click on the ‘file’ tab then uncheck “create thumbnails on save” next to file icon, for some reason that was doubling my processing time. Not sure why it would take so long to create a tiny thumbnail for the file icon but it does. My 16 inch MacBook Pro has been screaming fast with processing every sense unchecking that box, make sure to do it for every process recipe. All other functionality is very speedy. For speed example on my 16” 2.3ghz 8-core i9, 16GB memory, Radeon Pro 5500 4GB it takes 52sec to process 50 Sony A7R3 (42mp) files to full res 8bit TIFFS.
0 -
For me I think I found a solution or rather the problem. While I was working on the MacBook alone C1 was working fine. The problem only occurred when I was working using external 4K Monitors (Asus PA 329c and now Benq SW 321c). On my external displays I used scaled resolution under "System Preferences -> Displays -> (The external Display) -> Resolution" in order to get a better icon size etc. I did not set the setting to "standard for this monitor" but rather a scaled resolution in between the largest and smallest. This seemed to have caused the problem. Apple even warns right underneath the settings that scaled resolutions may impact performance. So whenever I work with C1 in my external display I have to either use the smallest or the biggest scaled resolution as with these settings also Apples warning disappear. It is not very convenient but at least it works.
I will also try Tobin Bennetts solution to improve performance even more.
In the end it seems like it is also an Apple problem not necessarily entirely C1. Although I still think C1 doesn't make proper use of the graphics card as outlined in previous comments. Main reasoning is that Lightroom works perfectly smooth when using filters and masks even with a scaled resolution on an external display.
0 -
Thanks Tobin, thanks Armin.
I have some strange observations when healing layers are defined (on my Windows workstation).
Outprocessing seems to ignore the graphics card when images have a healing layer.
As if C1 doesn't want to pass images with a healing layer to the graphics card. Not only the healing layer is processed on the CPU, but the gfx card seems completely free from any major load.
Or C1 knows that passing such images is not worth the effort, because my gfx card is only a little faster than the CPU (4.5 minutes vs. 8.5 minutes for 100 Z7 files, if no layers are defined). In the beginning of the batch, and every 15th image or so, the CPU gets idle for a few seconds and the gfx card takes some load, then the load is switched back to the CPU. Maybe C1 tests out if the gfx card is faster once in a while.
Anyways, thanks, it seems the MBP is a very good performer.
0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare