Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Mac Studio and sluggish C1

Comments

11 comments

  • Michael Zeldin

    Just curious about your observations.  Did you carry out selects and try some editing while the import was proceeding? It is my understanding that generation of the previews has not been "optimized" yet to make use of the M1 chip by Capture One.

    0
  • Fred Greaves

    Ahh excellent question. I should have added that to my original post. I did wait for the previews to be generated before I started making selects and using editing tools. 

     

    0
  • Eddie

    Have you tried running it with the monitor at native 5K? I saw something recently about scaling down display res on macOS is more taxing than at native res.

    On a side note, how does the C1 UI scale at 5K/4K? I'm looking to get a 32" 4K monitor, just not sure as I need the UI to fill the screen.

    0
  • Permanently deleted user

    My new Mac Studio (M1 Max 32 core GPU, 64GB Ram, 2tb SSD) arrived last night and started playing around with it on C1 this morning with the LG 27" Ultrafine 5k (set to 4k) and am disappointed so far by the performance of C1.

    I know this doesn't help you, but in his last live edit, Paul Reiffer seemed very happy with his Studio - and he owns a top spec Mac Pro.

    That said, in response to a question, he did express the view that C1 wasn't using the full potential of the M1.

     

    0
  • Fred Greaves

    I’m definitely happy with the Mac Studio and its performance. I’m just disappointed at how sluggish C1 is even with what is now a higher end Mac with the M1.

    0
  • Lotuso10

    Paul Reiffer is using a maxed out M1Ultra - is this what it takes to be "happy"? Is anyone on this forum using a 2560 x 1440 monitor with Mac Studio (M1 Max 32 core GPU, 64GB Ram, 2tb SSD)?

    0
  • Permanently deleted user

    I’m definitely happy with the Mac Studio and its performance. I’m just disappointed at how sluggish C1 is even with what is now a higher end Mac with the M1.

    Indeed. In this video, it was suggested that neither C1 nor Adobe are trying very hard to optimise their products for Apple silicon.

    Of course, this doesn't impact on those of us using steam-driven iMacs.  😆

     

     

    0
  • Fred Greaves

    From my non-scientific analysis, it actually seems like Photoshop and Lightroom are faster and very responsive. Now I have not been a working Lightroom user for quite a few years, having migrated fully over to C1,  but editing the same R5 files in Lightroom is much faster and without lag, even at 5k, interestingly enough. 

    I just hope C1 gets on board with optimizing the M1 performance... and I hope they are quicker than they have been about profiling the Canon RF 70-200 2.8... a lens released two years ago and we are still waiting...

    As far as the UI on different screens, it all looks fine. The lower the resolution you use on the screen, the larger the image is (good for looking at detail) but also the larger the tools are on the side, which means more scrolling up and down to make corrections, which just takes time. 

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    Comparing Lightroom Classic and Capture One performance/speed (on a MacBook Pro M1 Max 64 GB), the most obvious difference I've noticed is with database/catalogue handling. Searching/filtering in Capture One is unbelievably slow compared to Lightroom. When searching for a file name in Lightroom, the result comes up almost instantaneously, whereas in Capture One it takes 7-8 seconds, during which time Capture One becomes unresponsive. (This is with a CO catalogue containing just below 45k images/variants, and a LR catalogue containing more than 48k images/variants.)

    0
  • David Mantripp

    It is true that C1 catalog performance is slower than Lr, but then again in C1 you don’t have to constantly switch between stupid Develop and Library modes.  Personally I’ll take a performance hit over a straightjacket User Experience designed by engineers for engineers. 

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    "in C1 you don’t have to constantly switch between stupid Develop and Library modes"

    I've never found this to be a problem; with shortcuts switching is instantaneous.

    0

Post is closed for comments.