Positive Feedback
Assuming that Capture One staff is monitoring this forum I just wanted to take the opportunity and provide some positive feedback. I am running Capture One Pro on a 2021 M1 Macbook Pro. During summer and fall 2023 I got the impression that C1 Pro became slower and slower, despite a quite powerful device with lots of RAM. In January 2024 I seriously considered switching to Adobe because I couldn't stand the lagging any longer. Then came the February release 16.3.5.10 and everything went back to normal, at least for me. No crashes and a snappy response, well done. Please keep it that way.
On a sidenote I just wanted to mention that I during the 14-day test period of Adobe had the opportunity to explore Lightrooms AI masking capabilities. My experience is that C1 does a better job in correctly identifying and masking objects reducing the need for adjustments. Strange that Adobe in comparison doesn't perform better...
-
Good to hear that there are improvements for some users.
Here, Capture One still becomes unresponsive when I switch between tool tabs. Also on a 2021 Macbook Pro (M1 Max 64GB).
0 -
Nice! I just came to the forum to provide similar feedback. I work in a large studio environment with many photo bays going at the same time shooting product. Ever since the first AI update to Capture One there have been so many issues with crashing. The latest update seams to have fixed most of the instability on our M1 Mac Studio computers. And now that site licenses are coming back it's almost like it's running as well as it did a year ago but now with cool ai features.
Still have had freezes on older intel based iMac Pros and then the worst bug of all that has existed for over the last 6 years still exists where you move a folder of eips to another location and watch the metadata change.
0 -
The main crashing was definitely an issue related to the preference plist. Not sure if it was an issue of not handling preference data from older versions properly or the newer versions were creating their own problem in the plist. If we nuked the plist things would work again. Our issue is that we have a lot of photographers that use the computers and we need to be able to automate all of Capture One's preferences. Capture One only has the ability to applescript some of them and many others are stored only in that plist. We can't keep nuking the file and setting up the preferences from scratch all of the time.
0
Post is closed for comments.
Comments
3 comments