Capture One 21 performance issues on 16" macbook pro
I see a number of performance issues here, followed by people saying it isn't an issue on their identical hardware, but I have seen any solid solutions. I've opened a request but now response yet, so I thought I would try here. I've been advocate of Capture One for years, but I now I'm stuck and kind of wondering what my next move is.
MacBook pro (16-inch 2019)
2.3 GHz 8-Core Intel Core i9
16GB
AMD Radeon Pro 5500M 4 GB
I had the problem on BigSure and updated to Monterey but the problem persisted.
The performance issue manifests while browsing images and while editing.
When browsing I will see a slow 2 step refresh on each image. The image appears, I get a CO spinner, the image blanks, the image reappears, the images snaps into focus. I usually don't have a tab with a histogram in view (I use the Library panel when browsing), but if I watch a tool panel with a histogram I see the the image blank, the histogram appears, the image appears, and eventually the red line showing the histogram location of the cursor of the cursor in the image. This started with a session on an external drive. I moved the session to the local SSD and the performance is still very slow. I tried a catalog on the local SSD, with the same result. I tried a catalog on the SSD with referenced images on an external drive (drive disconnected so using previews) and still have the issue.
The problem also exists when editing an image. There is a large delay between moving the exposure slider (for example) and the update showing on the image. It's probably not a full two seconds, but I can count 1, 2 for each move of a slider.
I deleted capture one and reinstalled.
I made sure that hardware acceleration is enabled in capture one. I also tried with hardware acceleration disabled and the result was the same.
I have tried with automatic switching enabled and disabled for the mac.
I deleted ~/Library/Application Support/Capture One/ImageCore and let it rebuild
I turned on the focus mask briefly to see if it disappeared as a slider moved. The sequence I see is slide, CO spinner, focus mask vanishes, image disappears, image reappears, focus mask reappears, spinner continues for another second or two. This happens slow enough that I can count each transition out loud.
My images are a combination of fuji x-trans and older canon raw. The images I'm viewing in this session are RAW images from a fuji XT-1
I have been using CO for many years and I have never had this problem before, but at this point I cannot find a fix.
-
Good to see Im not the only one having this horrible lags since Capture One 21 in the same macbook pro you have. In fact, the last Capture One version which worked perfect perfectly smooth was Capture One 12 in my opinion.
When you are having all this lags and slow performances from CO, are you connected to the AC with the power or just using the laptop battery ? Because in my case the performance is even worse when using battery. But if you are connected to some external display with less native resolution as my Eizo CS2420 (1920x1200) then the performance is much better than using only the macbook display.
No official solution from CO, with CO22 I've heared it's the same problem. And I don't know if the reason is just Capture One developers are 100% focused on Apple M1's and forgot to optimize intel based laptops.
I work professionally everyday with CO and Im even considering selling this Macbook Pro 16" from 2019 and buying a much cheaper M1 Pro 14"....
0 -
I'm just using the LCD on the laptop right now, so no external monitor to add to the puzzle. I'm also using a power supply as I assumed CO would suck the life out of a batter in no time.
I went back to some older canon RAW images and they do render faster then the .raf files from my Fujifilm XT-1. Unfortunately this just reminded me how fast CO could run and how absolutely terrible it is for my current images. So new laptop, change camera systems or use LR. Lr seems like a compromise and who wants to compromise after investing the time and effort in creating images. Switching camera systems has crossed my mind, my that is a big deal.But, upgrading a 2019 MBP just to run the new CO, which worked fine in the past, is really irritating.
Thanks for commenting, it does help to know I'm not the only one having this challenge.
0 -
As Javier mentioned, resolution could be an issue. Try to lower your screen resolution to 2K and see if that makes a difference. I have seen a number of posts where the built-in GPU was just too weak to push 4K or 5K. Depending on the application and graphics engine used, performance could vary on a large resolution.
I personally have seen quite a bit of performance improvements when I downgraded from a 4K to a 2K monitor, both in Luminar and C1.
1 -
I'm using the laptop LCD with a native resolution of 3072x1920, which is just under 4k. I had an external dell monitor that is 2560 x 1440, so I gave it a try. Oddly enough, the performance is significantly better on that external monitor, even though the resolution isn't a lot lower. Maybe the 3072x1920 resolution is "confusing" capture one and it cannot decide what resolution it needs to load? My previous laptop, which had less power, but seemed faster for capture one, was a 15" Retina display at 2880 x 1800.
Using an external monitor may be a workaround for my situation, but it still seems like something is off here. That other application, the one that is usually way slower that capture one, is faster on this hardware and that just shouldn't be true.
Thanks for the input Eric and Javier!
0 -
Hi David,
Maybe the demosaic algorithm for the x-trans sensor still doesn't utilize the GPU but rather the CPU, but I didn't follow this closely as I never owned one:
https://support.captureone.com/hc/en-us/community/posts/360012390138-OpenCL-and-Fuji
And the no. of pixels of your external monitor actually is a lot lower 3,686,400 vs. 5,898,240 which is 62.5%.
0 -
Thanks BeO, for both the math assistance and the link about the GPU not being used x-trans files. If I consider the increased number of pixels with my 16" MBP and the fact the x-trans does not benefit from the GPU, the performance issues start to become explainable. It seems crazy that the solution to my problem is to use a lower resolution external monitor for editing and retouching.
0 -
"Thanks BeO, for both the math assistance and the link about the GPU not being used x-trans files. If I consider the increased number of pixels with my 16" MBP and the fact the x-trans does not benefit from the GPU, the performance issues start to become explainable. It seems crazy that the solution to my problem is to use a lower resolution external monitor for editing and retouching."
Yes, it super stupid but that's the only solution I know too :-/ Well, and of course selling the intel Macbook Pro 16" and buy a new M1 Pro 14" or 16"...
I guess Capture One developers wont work more around optimizing performance for Intel macs already...
0 -
It seems crazy that the solution to my problem is to use a lower resolution external monitor for editing and retouching.
If you change the resolution of your built-in display, does that not help as much? It's possible that downscaling might have some performance implications. Natively lower resolution would definitely be better.
0 -
Buy egpu with 12gb+ radeon card or run the aplication in low resolution mode. C1 is badly optimized and devs are saying its bcs of poor gpu…
0 -
Well, if they finally implemented Metal on the Mac and DirectX on Windows, I would think this would solve a lot of those performance issues. Of course, that takes twice the development resources but at some point they will have to bite that bullet.
0 -
David, i am in similar situation with my MBP2018. Curious if you found any solution with your setup? I keep testing ..
0
Post is closed for comments.
Comments
11 comments