Skip to main content

Will Capture One run on my M1/M2 Mac?

Comments

91 comments

  • Marcus Böhm

    Thank you for the nice video, funnily enough it was now on the second try without Open GL the same speed as yours. I am confused :-)

    0
  • Maarten Heijkoop

    C21 on my MBA works ok, sometimes beachballs @ unexpected moments, loading images @ startup is mostly time consuming, colorpicker doesn't work properly, sometimes it does, sometimes not, very strange. My Starry Landscape Stacker software is compiled for the M1 processor, why isn't C21??? According to Ralph, SLS developer, it's not a big deal

    0
  • Simon Spring

     Don't like Adobe and LR, Skylum is in it's babysleep, Darktables Gui does not have the UX-Factor for me...

    It is simple: Will give it a test, if it runs natively (no rosetta) on M1 - and will stick with LR, that supports M1.

    What about that steep price increase recently? prefinance development?

    The longer I read here and the more I think, the lesser I like the idea of tessting it at all.

    0
  • Marcus Böhm

    I have C20 and the new features of C21 are not worth an update to me at the moment and I will not be forced to update by the price increase. I'm not spending money on "maybe an update will come in the future", not at all. Either Capture One delivers or there is no money. A beta test version would be fine with me, at least then I'd know they were working on it, but like this? No. Very strange business behavior. There are other things I can buy beforehand that are more important for my photos. At the moment there's not much photography going on anyway, so I can wait patiently.

    -1
  • ROBERT DICKS

    Major regrets loading C21 on my new Macbook. Could not even get it to load past the beach ball. Horrible. Going back to 20.

    0
  • Dominique Trinh

    Using C21 with the M1 MBA. I'm having trouble with exporting and healing layer adjustments not being applied. Also having issues with the color editor and picking colors. You have to click it a couple times and switch back and forth from other tools to get it to work. Very strange behavior. Very annoying.

    1
  • Maarten Heijkoop

    When you download the latest version the colorpicking is solved, unfortunately the healing and cloning is still a nasty problem

     

    0
  • Marcus Böhm

    As greedy as I have seen the company lately, they will not release an update for C1 20 or from 13.1.3 anymore.

    0
  • Vlad Lucian Nistor

    @Lily Is there any date planned for the ARM-based Macs? It's been couple of months since the release of the new Macs but there is nothing, no news, no updates related to this topic. I think people are interested in this topic and the team should be more vocal about this subject.

    2
  • Tolga Yurdaer

    I just upgraded to mac mini m1 (16gb ram 512gb ssd). Using c1 21 (14.02) don't have any problem yet. And tethering shooting is very fast, even the focus tool is stunning fast. Shooting with Canon 5ds.

    0
  • Serge Daleiden

    Got my first M1 MacBookAir yesterday. Installed C1 right away and tested tethering mainly. Works perfectly with my EOS R5. Also seems faster than on my MBPro that I had before. No other issues discovered yet.

    0
  • eames k

    I recently emailed Capture One to find out when an update would be available. I got a very thorough and helpful reply.

    Hi Eames,

    We continually strive to make Capture One accessible on the newest hardware and operating systems and we are currently working with Apple to secure the best performance and compatibility for the new ARM-based Mac computers.
    Native ARM support will be released in an update to Capture One 21 in 2021.

    In the meantime, Capture One will run on ARM-based Mac computers using Apple’s Rosetta 2 emulation platform. Although with some limitations. This issue will be addressed in future upcoming releases, but so far this setup is not supported by Capture One and should be run by users at their own risk.

    In the meantime, if it's is critical to your workflow we discourage you from using it until we release the updated version of Capture One for ARM-based Macs.

    0
  • milo milo

    Cool, but in my opinion Metal API support is more crucial, because arm users are still small amount.

    0
  • Benjamin Kim

    C1P 20 with M1 Mac works fine but I really waiting for the native version. But It's not clear whether they will support it within early 2021 or later. 

     

    Also, OpenGL is outdated especailly for Mac as they ditched and created Metal API. I have no idea how long do we have to wait for Metal API to be supported. I really feel C1P is not using all of the power.

    1
  • milo milo

    @Benjamin Kim

    I totally agree. We loose 20-30% of performance, Macs ain't cheap and work is harder to get.

    Metal API was introduced with OS X Yosemite in 2014, and C1 team still thinks it doesn't exist, ridiculous.

    If you think most users are Windows based, You are sooo wrong.  Go full on MacOS or leave it.

     

    Milosz

    0
  • Louis Sousa

    The program is unusable on my new MacBook M1.  Beachball city.   Runs perfectly on Lightroom and DXO.  I much prefer using C-One so hopefully the upgrade will come soon.  Until then, the program sits in the drawer.

    1
  • ROBERT DICKS

    Agreed. Unusable on my new Macbook M1. 

    0
  • Jonathan Gardner

    @Milo & @Louis

    Do you happen to run any window snapping software like Magnet? I was having issues with another application. Same behavior, beachballs with every click. As soon as I shut down/uninstalled Magnet, no more issues at all.

    FWIW, I am not having issues with C1 anymore on my M1 after update to 14.0.2.49. I also uninstalled Magnet.

    0
  • milo milo

    I did some testing.

    Export of 20 raws to JPG 100%; 300ppi; 80%, from EOS R took half the time on Windows version than on MAC OS. 34sec vs. 54...

    Same machine: Ryzen 5 2600, 16gb ram,SSD, RX580 8GB, it's Hackintosh.

    I think it's due to lack of OpenCL updates on Mac.

    I also found out that export on integrated GPUs (MBP 13' 2015) is faster when Hardware acceleration is off.

    I had to share it ;)

     

    Milo

    0
  • Marcus Böhm

    Now you would have to do a test on the M1 Mac under Rosetta.

    0
  • milo milo

    @Marcus Böhm

    That would be interesting ;)

    What I tried to show is that we loose performance due to lack of MetalAPI, if you add Rosetta emulation, it must be severe performance lose :(

    I think C1 tries to use one program for both platforms with OpenCL, that hits macs, which in my opinion are most of users.

    I love C1 and I want it to be better, but they are always behind technically :(

     

    M.

    0
  • Maarten Heijkoop

    C21 runs fine on my MBA M1 when OpenCl is set to "never" in the C21-preferences. Occasional beachball at startup, not sure why

     

    0
  • Dennis van Mierlo

    @Maarten Heijkoop

    Capture One 21 (14.0.2) was crashing/freezing on my Mac Mini M1 (16GB 1TB MacOS 11.2.2) when closing. Every time I had to force quit C1. When I tried your suggesting, setting both display and processing Hardware Acceleration (Use OpenCL for) to Never seems to help. Capture One closes normally now.

    Thank you for sharing!

    Lot’s of greetings, Dennis 🇳🇱

    0
  • Dennis van Mierlo

    On my M1 I see in the system.log (Console app) I see errors related to OPenGL that occur when having this hardware acceleration option enabled.

    Capture One 21[24313]: getattrlist failed for /System/Library/Frameworks/OpenGL.framework/Resources//GLRendererFloat.bundle/GLRendererFloat: #2: No such file or directory

     

    0
  • Benjamin Kim

    How long do we have to wait? It's almost Q2 and yet Capture One Pro still doesn't support Apple Silicon! I thought it was very clear that they promised to support it in early 2021. 

    2
  • milo milo

    @Lily
    Hello? any info for customers? 😀

    0
  • Darryl Young

    It's now March and there's been no further information on what's going on with the M1 version of Capture One. I upgraded last year based on the "early 2021" statement regarding an updated version being released. I get that things take time, and that's fine, but it's frustrating to not be getting at least semi-regular updates on what's going on.

    0
  • Maryna Sopilniak

    Hi Benjamin Kim,

    Thank you for your comment.

    There is no information about this issue at the moment, but I surely transfer your request to our Product Management team for further consideration.

    0
  • Maryna Sopilniak

    Hi Darryl,

    Thank you for the comment.

    Currently we have no information on future implementations.

    However, as soon as we get any updates from the Product Management team we will post it straight away.

    0
  • milo milo

    @Maryna

    Did You read only the last comment?

    Get real guys, you behave like PR team of Soviet Russia...

     

    Milo

    0

Please sign in to leave a comment.