M1 Mini, Fuji, Extremely Laggy Performance on simple edits
I am running into extremely laggy performance when editing my files. This is specific to seeing the results of a change. For instance, Making a simple clarity adjustment on a file, no other changes takes a count of 6 before I see the results of moving the slider. This is consistent across many of the sliders/adjustments, and it makes the editing flow painful to approaching unusable.
Config:
Maxxed out M1 Mac Mini
Latest Big Sur
Capture 1 21 version 14.1 fresh install, first time on this new machine.
Fuji X-T3 uncompressed RAF files
In contrast, editing the same files on an Intel 15" MacBook Pro using Capture 1 does not have this issue with the same files, same drive, etc...
Suggestions?
Thanks,
Doug
-
I think you will continue to see these issues (and others) with the M1 chipset until CaptureOne redo their software to make use of the M1 architecture.
Right now, there is software running on your Mac that is allowing C1 to run on the M1 chip, so that is slowing stuff down. It may be better to use your MacBook until C1 updates their software.
0 -
I'm using the exact same setup except with XPro3 and 50R RAF files. It flies. Faster than my 2019 MBP 15 inch with more RAM.
I suspect it's something other than purely the software combo.
0 -
Doug, I see you mention “same drive” so I assume you’re using an external drive? Might that be the culprit? What happens when you transfer a bunch of files to your Mini’s SSD?
1 -
Thanks for the replies so far.
I doubt it's the external drive I am using. It's a high speed SSD and works fine with my Intel MBP. Unless there is a system specific slowdown for that drive with the M1 Mac that isn't there for my MBP, I'm guessing it's not that. However, to be complete, it's easy enough to try and see.
The fact that Mike does not see the issue is interesting. If it were just the 50R files that are plenty fast, then I would suspect a difference between XTrans and Bayer processing causing the issue. However he mentioned an XPro3 which is also XTrans. So that kinda rules out XTrans processing on the M1 as being the likely culprit. However, to be thorough again, I can test it against some Panasonic files from my wife's camera.
The issue really seems to be in the processing of the display image when a change occurs. I haven't tried any heavy edits with multiple layers yet to see if that affects the perf.
Doug
0 -
Doug, it baffles me to no end that some people run into problems on machines with the same specs as others without problems. It see it happening all the time here on the forum. Good luck with troubleshooting. Fingers crossed you find the root cause. Keep us posted.
0 -
Hello Doug have you made any progress with this? I've just begun to use my setup with GFX100s files. It continues to fly with very little lag - each RAF is over 200MB. Initial zooming of a RAF shows some minor lag - <1 second. After that it's pretty seamless.
Two questions: Do you have plenty of spare disk space on the system disk? It seems that the M1 Macs make heavy use of swap space according to some denizens of the 'net. Secondly, and a long shot, what is your monitor setup? I'm using a BenQ SW271 connected with HDMI. This should make no difference at all but it may be worth checking. Odd things happen with new hardware.
Regards
Mike0 -
How about tethering/Fuji? I should stick with my Intel MBP, right?
0 -
Skip, I have no problems tethering with a GFX100s and a 5 metre tether tools USB cable. Small lag as each file loads, but no slower and probably quicker than a Phase digital back.
0 -
I was also going to ask about your monitor. I'm running Capture One 20 on a M1 Macbook Pro 16gb and notice a slow down when connected to a 4K monitor with a scaled resolution of 2560x1440. If I'm using the laptop screen I don't see noticeable slowness.
0 -
Sorry for disappearing for a while here. Lots going on...
My monitor is a LG Ultrafine, 27 inch 5k. Same one I had on the MacBook Pro with no issues.
I have tried working on my internal SSD, but the problems seen to persist.
It feels like graphics acceleration is not being taken advantage of, but that’s a guess.
JPEGs may be faster. I have to test that more.
There has always been a lag for the initial render of an XTrans RAF for me, but after that, scrubbing a slider yielded very quick results. Now, I can wait seconds to see the results of moving a slider. This is why I’m keying on graphics. MY MBP has a dedicated graphics chip.
I have a different display I could try just to see if that has an effect.
Import is plenty speedy. No issues there.
Perhaps there is a way to play with the previews to see if that is having an effect.
So far, my troubleshooting has been pretty scattershot. I will try and be more scientific about it.
Doug
0 -
Yeah, X-T3 and 50S files run slower for me on the big monitor for me. I think you're right that when running Capture One through Rosetta it doesn't take full advantage of graphics acceleration. Hoping it's better when they release an ARM64 build.
0 -
I thought the GPU performance of the Mac M1 mini was limited? is that a contributing factor?
0 -
GPU performance should be top notch. They put some pretty beefy integrated graphics (8 cores I believe). All the native tests show excellent performance.
0 -
I hit a breakthrough and possibly found the source of the bug. I switched cables on my monitor from thunderbolt to USB-C. This down rezzed the display because usb-c doesn’t support 5k on the LG Ultrafine display. And lo and behold, the performance issues went away.
Then I went back to the thunderbolt cable, and it defaulted to one higher resolution again, and the perf issues returned.
Then I went into the display prefs and down rezzed the display via software (so, still with the thunderbolt cable), and again, the perf issues went away.
By the numbers, 2560x1440 or higher in display settings, and the perf is progressively worse when upping the scaling.
2048x1152, and the perf was completely acceptable.
Not sure how to report this bug, but it is either a buffering issue or how they are playing with graphics within Rosetta.
For the record, the higher scaling did not have this issue on my Intel MBP which has dedicated graphics on board.
0 -
That's a win of sorts Doug. I'm pleased that you have at least an interim solution to the performance, if not the monitor resolution.
On the subject of GPU performance, I've been using Activity monitor to understand the loads on tasks such as batch processing large numbers of images. What's interesting is that the CPU load hovers around 290% - so by my reading it's using nearly the full load of 3 cores. However the GPU load shows 93% but the graphical representation shows the load on the GPU as basically maxed out. It would appear that even though there are 8 GPU cores we're not seeing maximum load as 800% but as 100%.
Assuming that's true the GPU runs nearly maxed out most of the time on those sorts of tasks. Maybe it will be a limiting factor.
0 -
Or Activity Monitor might have a bug :-).
1 -
Maybe ;)
0 -
I just noticed this statement in the release notes for Capture One 14.1.1:
4k / 5k monitors
Due to the significant additional calculation overhead, systems using 4k/5k monitors will require additional resources in addition to the above- recommended spec (both in GPU and CPU power). For a professional experience, we recommend at least doubling the specification above for these configurations.
Specs don't talk about Apple Silicon but nevertheless.
0 -
Well, it’s a maxed out mini, but so is my intel MBP. I haven’t tried the latest Capture One on the MBP with the 5k display, though.
0 -
Has there been any update on this with new versions of Capture One? I'm having the same issue (Same Monitor, M1 Mac Mini, Capture One 22), but downsizing the resolution is not resolving the issue at all.
0
Post is closed for comments.
Comments
20 comments