Support for New Apple M1 Chip?

Comments

54 comments

  • Emile Gregoire

    You can try to drag in other stuff as much as you like, but this thread was about M1 support. I stated Adobe is supporting that for its direct C1 competitor somewhere next year - you said not true. Except it is true. But hey, apology accepted. Cheers.

    0
    Comment actions Permalink
  • CSP

    hm, you are right LrCC is not a competitor and although LR classic runs without issues on rosetta (adobe official) c1 is ahead of them.....   lets talk again when they have delivered, a bug free, smooth running version.  oh forgot bug free is a oxymoron when it comes to c1. 

    -1
    Comment actions Permalink
  • Antoni Rybaczyk

    @CSP never had your issues. Also, C1 seems to run on Rosetta2 as reported by other users in this feed. Why so negative about C1? Just use other software and chill in bliss.

    0
    Comment actions Permalink
  • Rosemary M

    This is an interesting thread!

    I'm currently stuck in an Adobe subscription and mainly use Lightroom. I'm not a huge fan of the look of my Fuji RAW files in LR and it runs very slowly on my 2015 MacBook Pro 8GB RAM.

    I've briefly tried Capture One Express and much preferred the look of my Fuji files. I've yet to try the full version of Capture One so not sure how it would run on my current MacBook. 

    I'm tempted to upgrade to the new MacBook Pro with M1 chip next year and curious to know how Capture One will perform. I'm planning to buy the software as I ideally don't want to be stuck in a subscription model.

    If I upgrade the OS on my MacBook will I also need to pay to upgrade Capture One every time?

    0
    Comment actions Permalink
  • Emile Gregoire

    @R M

    It depends. Most of the time, Capture One will simply work on a new OS, so there's no evident need to pay for an upgrade. However, a new OS is usually not officially supported, so if you run into problems, you're on your own.

    It seems that, for the first time if memory serves me right, they're actually going to support a new OS on the current and previous version; in this case Big Sur on CO20. If that means they'll support all the dot updates of Big Sur on CO20 as well, remains to be seen. Should that be the case, you could upgrade once every two years and still enjoy support. It's a big 'if' however; I hardly expect them to keep on updating CO20. Note also that Big Sur was a fact before CO21 happened, so that might be a factor too.

    0
    Comment actions Permalink
  • Rosemary M

    Hi @Emile
    Thanks for your helpful reply.
    I’ll need to have a think about that as usually I upgrade my OS. I hadn’t considered it and just assumed whatever version I had (e.g. Capture One 21) would work for years across the different OS upgrades.
    Maybe I should go back to considering the subscription model for Capture One 🤔 I was hoping to avoid that.

    0
    Comment actions Permalink
  • Andy H

    I just got my M1 MacBook Pro 13" with 16Gb memory.  Capture One 21 just doesn't work reliably at all.  Frequent freezes, slow performance, crashes etc. Every other editing program I have (Lr, Ps, DxO PL4, Nik, Exposure X5) are perfectly usable, although most of them not yet fully optimized.

    2
    Comment actions Permalink
  • Rosemary M

    @Andy H Useful to know! A shame it isn’t working though. Hope they offer support for the M1 chip very soon. 

    0
    Comment actions Permalink
  • Brett Brock

    Andy,

    Try going into the “Applications” tab in the Finder, and right-click the C1 app, select “Get Info” and then check “Open using Rosetta” box to make sure it runs with Rosetta and doesn't try running directly on the M1 SOC. Rosetta 2 will configure C1 to run in the M1 environment. I have a MacBook Air M1 8gb and a Mini M1 8gb and C1 v20 flies compared to my Intel MacBook Pro and Intel iMac Pro machines. Good luck to you on getting things squared away.

    2
    Comment actions Permalink
  • Andy H

    @Brett.  Thanks. Yes, my version of C1 (v21) is running under Rosetta 2 and it still runs very inconsistently.  I was able to edit a dozen or so photos with no issues, then the next time it froze before I'd even got through 2.  I also find it will not quit properly, I'm constantly having to Force Quit when I'm done.  I reverted back to v20 and had largely similar issues.  I'm wondering if the Big Sur/M1 combo is the issue - I don't think C1 are officially supporting either at the moment. It's a shame because when it works for an edit, it's very fast and responsive.

    0
    Comment actions Permalink
  • Tim B.

    No news here?

    0
    Comment actions Permalink
  • Andy H

    I've downloaded the latest 14.0.1 (v21) update that apparently addressed the Big Sur compatibility issue and it still runs unreliably on my M1 MacBook Pro.  Therefore, with that variable out of the way, I can only conclude that there is something in the C1 coding that Rosetta 2 cannot currently bridge.  I look forward to the next update that will hopefully give us the native compatibility that we already have with some other products.

    0
    Comment actions Permalink
  • Brett Brock

    I’m running v20 build#13.1.3.9 on a Mac Mini M1 (or on a Mac Air M1 traveling) and Big Sur v11.0.1

    I’m certainly NOT going to do any updates as mine are running well between the two machines. Obviously a serious issue for those who have work to get done. If others could chime in what build#/OS version works or does not work that might help the C1 team figure it out. And yes, a native code update for M1 and Big Sur would be very welcome indeed for those struggling.

    0
    Comment actions Permalink
  • Fabrice Fiorucci

    Hello,

    Just received my Macbook Pro M1 16GB when C1 will get aligned with M1 Processor ?

    Do you have any news from Capture One ?

    0
    Comment actions Permalink
  • Andy H

    No news other than it’s planned. I don’t have an inside track into C1 to understand when this will happen. In my experience, C1 continues to be unreliable running through Rosetta 2, so I’m still using it on my old 2015 Mac.

    0
    Comment actions Permalink
  • Fabrice Fiorucci

    Thank you Andy for the update.

    I just treated a shoot with my brand new MBP M1 without issue.
    I did not feel any difference in term of performance compared to my MBP13 i5 (2018)
    I did not have any bug so far, C1 quit properly after work. So I cross my fingers.

    What I like with the couple MBP M1/C1 compared to the previous MBP I5/C1 is the silence, Awesome battery life cycle and the "esc" real touch. The performance difference in C1 with Rosetta looks like the same.

    I feel the perf difference only when I export my C1 album for slideshow in FCP.

    0
    Comment actions Permalink
  • Hartmut Barger

    Thanks Fabrice. Do you use C1-20 or C1-21?
    I'm getting my MBP soon and I'm using V21 on an iMac i5. Of course I hope for an update soon.

    0
    Comment actions Permalink
  • Christian Schmieder

    Hello to everyone here,

    I have a general question, maybe off topic, but:

    As far as I know (maybe I missed something?), there is no Monitor Calibration Software (EIZO Color Navigator, X-rite Profiler, Calman, basiccolor, SpyderX) that works at the moment on M1 machines (there a workarounds but I don't trust them).

    My question is, how can one develop his images on uncalibrated monitors (also external, 2nd monitors)?

    You try to use C1 on M1 machines, that at the moment isn't working without any hassle and complaining about Phase One / Capture One, maybe you even try to fulfill jobs with it (👍), but ignoring the topic fully, that there is no proper working calibration solution on the market for M1 based Macs at the moment!.

    Don't you calibrate your monitors at all, seriously?

    How can one try to use C1 (or any other image software) on M1 Macs, when the absolute basics of Color Management / Color Calibration aren't fulfilled or even be possible on these machines?

    Maybe I'm missing something completely or I do not understand anything about this matter at all.

    But please help me out, I can't understand what the use of this discussion is about.

    Shouldn't there be at first a proper Color Management be possible with M1 Macs before even considering complaining about a non or just partly functional C1?

    I'm personally waiting for a working and accurate color management solution, before I even consider buying a new M1 mac.

    All the best, Chris 

     

     

    -1
    Comment actions Permalink
  • CSP

    @christian

    good point and you are absolute right !  on the other side most user would probably not see much of a difference between a calibrated display compared to one which uses the default apple profile anyway...

    0
    Comment actions Permalink
  • Henrik Helmers

    Having to run under emulation is bad enough, but the constant freezing on M1 Macs is a deal breaker. The M1 performance is excellent, it should be perfect for editing on the go.

    0
    Comment actions Permalink
  • David Roy

    Hopefully the delay in getting native M support is due to a nice rewrite of the obsolete OpenGL code to Metal and that this has also spurred them into building a native iPad app. I would even be interested in a non feature complete version like Adobe is doing with Photoshop so they can release it in bits and bobs as it is ready.

    0
    Comment actions Permalink
  • CSP

    ...maybe the delay comes because they did not tell the truth 4 month ago and it takes them much longer even to make it run without issues on rosetta  ;-)  

    0
    Comment actions Permalink
  • David Roy

    The latest is it'll be another four months. If I had known I would have waited for Capture One 22 instead fo buying 21 on the good faith they would have a early/Q1 M1 update. 

    0
    Comment actions Permalink
  • David Roy

    Looks like the M1 version is coming in May https://blog.thomasfitzgeraldphotography.com/blog/2021/4/capture-one-for-m1-macs-coming-in-may

    And the original FaceBook link for those that still use FaceBook in 2021:

    https://www.facebook.com/captureonepro

    0
    Comment actions Permalink

Please sign in to leave a comment.