PERFORMANCE ON M2 TERRIBLE !!!! – FIX PLEASE!
THE PERFORMANCE OF CAPTURE ONE ON BRAND NEW MAC M2 MAX IS APPALLING!!!! I HAVE MAXED OUT MACBOOK PRO AND THE PROGRAM IS WORKING LIKE ON WINDOS 95!!!
YOU GUYS NEED TO DO SOMETHING ABOUT IT, IT'S UNBELIEVABLE HOW BAD IT IS ON 6 GRAND 96GB RAM MACBINE MACHINE.
THANKS
-
More than screenshots are needed. Logs will give a huge indicator as to what's going on under the hood, so please include those.
I certainly didn't mean to dismiss this issue Erik V – I just want to make sure the feedback and findings are going to the right place. Because it seems like it's an issue in the community, but hasn't yet made it to the top of our issues in support.
As you rightly said, we are all on the same team. I've been working at Capture One/Phase One long enough to know how to get things solved and how to push things up the priority list ;)
0 -
Jeezus. You guys aren't paying the users enough moeny to run us around in circles so you can figure out an obvious problem.
Explain problem on Capture One Community group
Told to submit a ticket
Submit a ticket.
we didn't get it.
Submit another ticket.
Not good enough
submit another ticket
Still not good enough...-2 -
I just cancelled my subscription which is the only way to deal with this at this point. it's a shame you can't even admit you haven't optimized the software for Apple Silicon after 3 years. My plan expires at the end of the year. if you plan on fixing this issue then I will renew in January. If not, I'll use another tethering platform.
0 -
FWIW Craig Stodola's screen shot a few hours ago is more than enough information to work with.
It shows the computer wasn't been taxed by other processes and it shows that only a few of the available cores were being used, with the others effectively sleeping.
It's not that C1 Pro on an Apple Studio M2 Max or Ultra doesn't work – no one is saying that. It's just that with all the cores and RAM available (in my case 64GB), it should fly. It doesn't. Same throughput as my 2018 Intel i7 Mac Mini.
Nowhere left to hide Phase One! Fix this. Now.
1 -
John Arborio - The Capture One development and marketing teams are in denial. There's zero point going forward with C1. Art Is Right's benchmarks 100% validate what I and many other users are experiencing with this software, and the lack of Apple Silicone optimization. YAY! There's more AI features. I do my heavy duty retouching work in Affinity Photo if needed, which cost me all of $25 five years ago.
I need C1 to tether, edit, convert, and export RAW files as efficiently as possible. Exporting is a total dog now.
Andrew Nemeth - Rather than hearing, "we're on it", they're making us jump through needless hoops, and dodging the problem. They're not going to fix this. I'm done with C1 at this point. My next RAW editing upgrade will be LR. My M1 Max will feel like a new workstation compared to C1.
Really wish Apple would explore photo editing again, and bring out a new version of Aperture...0 -
How to interpret Craig's graph depends on what is being exported. I may have missed the export specs: size of file, format, number of layers, other edits. Is the sample uniform? How should we replicate it?
Should the load be evenly distributed between cores or does the load saturate a core and then spill over to the next core?
Is the CPU load low because Capture One is not using the CPU due to bottlenecks in the code related to an inefficient iterative process or because these process are not being parsed into the maximum number of threads?
-1 -
I tried to standardize the testing a bit. My results are different than Craig's, but I am not sure how to interpret. I am running Capture One 16.2.6.7 on a M2 Mac Studio Ultra with 24 cores and 126 GB RAM. My RAW files are on an external Thunderbolt NVME SSD. I exported 560 R5 45MPx edited images, many cropped into TIF 16 bit uncompressed and separately the same files into JPG 80% files.
Below is the screen grab after about 80% of the TIFFs were exported and is representative of the overall process. The export time was 7min 17 sec.
Below is the screen grab after about 80% of the JPEGs were exported and is representative of the overall process. The export time was 8min 20 sec.
To me, it looks like all of the cores are being used, albeit in what looks like a spillover pattern with the lower numbers cores handling more of the load, but not as saturated as in Craig's test. The times are faster, but not hugely so than in Craig's test, but if due to the additional cores, it would seem to indicate that the cores are being used. How efficiently they are used is beyond my ability to say.
So, what is the meaning of the difference and how would this compare to the same export with LightRoom? What coding characteristics explain it?
0 -
Addendum: The JPG timings and screen shot were actually for exporting to JPEG and TIFF in one export. I forgot to uncheck TIFF, which explains why the JPEG export appeared to be longer than the TIFF. The correct screenshot for JPEG export is below and the time was 4 min and 44 sec for 560 images.
-1 -
I'm running 16.2.6.7
1000 Nikon Z6 II 24MP files
Exposure, denoise, WB, highlight adjustments - zero layers
All files stored and exported to an external NMVe drive.
Go back and read what Art Is Right is doing and compare C1 to LR. Kind of done repeating the same thing over and over. It's relative and repeatable.-2 -
Yes, LR is at least twice as fast on exporting JPEGs as the M2 Ultra. I do not have the knowledge to interpret exactly what the graphs are telling us regarding the effective use of the PCores. My hope is that Capture One engineers will look at these and have an ah ha moment.
0 -
I tried again today. 3 second delay when moving the exposure slider on a 200 mb raw.
1 -
craig stodola Where have you been asked to create 3 separate support tickets and where did somebody say "we didn't get it"?
I can see that you haven't actually submitted any support requests, at least from this profile. How are you getting in touch with us and is it perhaps with a different email address/profile?
2 -
I did sent a support request based on this thread. You've asked this group to send tickets multiple times.
Whether or you not received them is another thing...
And if you can see the support tickets, you should also be able to tell the developers the issues we're having with Capture One.
If you can't see my support ticket ...add "support ticket submissions" to the docket of things to fix...-3 -
craig stodola I have full access to the support system and you haven't got in touch with us from the account you're using at the moment.
Anyway, the sentiment stands for anybody else experiencing this behavior. Get in touch with us here: https://support.captureone.com/hc/en-us/requests/new
Be sure to send logs and the system information so that we can build up strong knowledge of which devices, operating systems etc. are being used.0 -
John Arborio We're particularly interested if you've noticed the sliders slowing down.
Please see my comments above. I can also make a support request on your behalf if you'd prefer.
1 -
It slowing down. Never working smoothly. On several machines. If it was one machine I would troubleshoot. But new installs on screaming fast M1 M2 machines should work. It never does. Go ahead if you want to send a support ticket hit this is obviously a flaw in the software. Did you stop development for Apple Silicone? I don’t get it.
-2 -
Created the logs and submitted the ticket just now. Wonder what the next excuse for not addressing this problem will be?
BTW, here is a link to an "ArtIsRight" Youtube video where he tests the Silicon Macs and notices there doesn't appear to be any optimisation:
Scroll ahead to the 13 minute mark where he makes his point.
We're not imagining this. The new Silicon Macs are powerful machines. FCP, Affinity Photo and (I hear) Lightroom all roar on them. Not C1 Pro though. Fix. This. Now.
1 -
Lightroom Classic screams on all Apple Silicon Macs. Instant response from adjustment sliders.
1 -
"Anyway, the sentiment stands for anybody else experiencing this behavior. Get in touch with us here: https://support.captureone.com/hc/en-us/requests/new"
I clicked that link from the last page. Filled everything out and submitted a support ticket.
If you're saying you didn't get it, that's likely part of the problem.0 -
I just submitted a request with screen recording of slider adjustment lag. I don't expect any resolution since nobody will admit it is a problem but since it's a holiday week I have time.
0 -
From Art Is Right testing...
Art is exporting the same 1000 45MP files for both his LR and C1 testing.
vs. the current Lightroom CC...
***please note three underlined sets of letters compared to Capture One's...
I could export 4 LR 1000K image jobs in the time it takes C1 to export a single 1000K job.
Linky:
https://www.youtube.com/watch?v=okGahg98kL8
Note: I don't have a significant slider issue with my latest OS update. It's worlds better than what it was a year ago. It's not on par with my old 2019 i7-8 core iMac. ...My 2019 iMac was infinitely worse than what I experienced with my old 8-core 7820x and the Sapphire Nitro+ RX 580 in terms of slider smoothness. That PC build was buttery smooth... Exporting on that 7820x and the Nitro+ RX 580 was about 10 minutes faster than my M1 Max Mac Studio - same size 24MP files, D750 then vs Z6 II now, same editing style.0 -
"I just submitted a request with screen recording of slider adjustment lag. "
I hope they get it...0 -
I’ve been in photography for 40+ years and not once have I exported a 1000 photo batch*.
* - other than a test I did recently.
0 -
....ok.
0 -
@craig Just thinking out loud. How often do you have export jobs this large?
-1 -
Not every wedding I shoot - but this year it was 6 times. I generally try to keep the files lower than 800, but I rarely turn in less than 800 anymore. So out of 20-25 weddings per year, I'm finishing 800-1000 images. But if there are larger groups of sequences I want to keep, then generally, the number is higher.
1 -
So by these metrics (assuming they’re accurate, testing properly optimized in all cases, etc), you’re talking about < 5 min per day assuming you export 800 photos every day, but more like once every 2 weeks?
Standard disclaimer. Not affiliated with Capture One. I don’t work for them. I don't speak for them.
-1 -
Yeah! What you said. One 5 minute export... that's it. I'm done for the week. Or, you know, multiple weddings to sort, edit, and export, post, with family and graduation sessions mixed in throughout the fall and early winter, as people want their files before Christmas. Then it's on to wedding album season...
Edit: I don't pretend my way is the only way to work. I don't pretend that if I process 1000 files for a wedding, everyone else does. I also don't pretend that everyone else should work the same way as I do. I don't pretend everyone is slammed with work 365 days per year. I'm not slammed with work all year round. My season runs from June through mid November. And September-December is my busiest time of the year.
I don't pretend people don't have family life responsibilities outside of photography, and all they have all day everyday to work-work-work-work-work.
I do know there are numerous people who edit files for other wedding photographers, and they have multiple clients, and the fall season is also their crazy season, and they're working with both LR and C1.
Standard disclaimer - Stop projecting your photography ideology on to everyone else.-1 -
You’re welcome to repost that without the personal insult.
I was replying directly to the numbers you gave me.
-1 -
Your first comment was:
"in 40+ years, you've never exported 1000"
Follow by:
"So by these metrics (assuming they’re accurate, testing properly optimized in all cases, etc), you’re talking about < 5 min per day assuming you export 800 photos every day, but more like once every 2 weeks?"
Passive Aggressive much?1
Please sign in to leave a comment.
Comments
94 comments