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. ⚠️

C1 16.3.0.76 crashing Mac Studio

Comments

14 comments

  • Tore Edvinsen

    yes i have the same problem, have C1 23 Pro version and i can't update to the new version 16.5.

    i have sendt a reqvest to Capture one about it, but no answer yet.

     

    0
  • Brian Jordan

    Have you deleted the app and reinstalled? I’m having no issues here and I’m on Mac Silicone and running the latest version of the OS (not including the update from yesterday).

    -1
  • Fred Greaves

    Yes, I have tried reinstalling it. The issue persists.

    I also got the following suggestion from C1 Support, but it still crashes every time even after running the terminal script.

    "Can you please try and clean all the registry and preferences files from your computer?

    Run the following command in the Terminal app (in the /Applications/Utilities/ folder) and hit return:
    defaults delete com.captureone.captureone16

    You cannot merely delete this file from Finder because it is cached, so only use the command above. Capture One must be closed, and you should wait several seconds for the command to take effect."

     

     

    0
  • Brian Jordan

    So I assume you did that? If so and you’re still having issues, reply to the support ticket email and they will continue helping you. This is definitely an issue with something, some install configuration, some hardware conflict, some something specific to your computer. Support will likely need log files to help you further but replying to that support email is your avenue forward. Good luck. Post back here when it’s resolved, please. Maybe help someone else who might experience similar.

    -1
  • Fred Greaves

    Brian,

    If you read my post, I wrote that it still crashes after running the terminal script they sent me, so, yes, I did it. I also responded to support letting them know that.

    I am posting here just so that anyone else that is experiencing the same issues can realize that they are not alone in this and can hopefully benefit from the steps I have already taken. C1 Support already has log files, as well as screen recordings showing the problem.

     

    1
  • Brian Jordan

    Good deal. I didn’t understand that from your post and wanted to make sure you’d circled back to them. I’m interested to hear the outcome. Question: can you spin up a new user and install Capture One 16.3 under that user. Safe boot to that user before install. All other users logged out. Nothing running in the background. Nothing external except keyboard, mouse, display attached. That should give you the cleanest slate possible without significant tinkering. Might be worth the time to try.

     

    edit: I’d also rerun this after the safe boot: Run the following command in the Terminal app (in the /Applications/Utilities/ folder) and hit return:
    defaults delete com.captureone.captureone16

    -1
  • Brian Jordan

    Full disclosure: I’m not affiliated with Capture One. I’m just a been-around-the-block user with a mod tag trying to help out.

    -1
  • Brian Jones

    Thanks for posting Fred. I'm also experiencing the same crash at launch. I don't have the bandwidth to troubleshoot at the moment. I'll check back for your solution.

    0
  • Andrew Mitchell

    I had the same issue on MacBook Pro M1 just now and running the command in Terminal, as suggested above, fixed the issue for me.

    0
  • Fred Greaves

    Brian,

    At this point I am waiting to hear back from them as they are passing this along to software engineers to sort out, which hopefully will happen soon.

    This is my main production Mac so I am just using 16.2.5.9 until they figure it out or have other things for me to try. Since 16.2.5.9 works perfectly (other than the not exporting to iCloud linked folders) I am just sticking with that until we get this figured out. I use this Mac for printing and other things so I'm hoping that it is not going to involve new users, safe mode, etc., and I don't have tons of free time to fiddle around with it, to be honest. 

     

     

    0
  • Brian Jordan

    Fred Greaves. Fair enough.  I've had to take things through the support queue before.  Always had good success.  Good luck and please do post back here whatever solution you guys work out.  I'm sure at least one other person out there could benefit.

    As to the hidden files, I've spent some time on the Apple boards and this issue isn't related solely to Capture One.  Looks like an Apple/iCloud problem.  Apple's advice per their support site is to show all hidden files or to export files to non-iCloud linked folders.  I think we'll likely see a service update from Apple soon.

    0
  • Fred Greaves

    So basically after more than a week of sending screen captures, log files, running terminal commands, and doing my best to help C1 diagnose this, they only solution they have offered is to create a new user and install it there. It works under a new user, but that then creates a whole host of new issues and at least a day of unpaid downtime for me while I completely rebuild my main production Mac Studio. 

    The previous version works fine (well, other than the icloud bug and other existing bugs that haven't been resolved) under my current user, so the fact that 16.3 crashes immediately suggests it is some sort of conflict with preferences, extensions, or something like that... which the log files that I have sent again and again to them should help them identify what's going on. 

    They ding me $259 and send me "new improved" software that won't run without rebuilding my system... not feeling like a "pro" offering at this point.

     

    0
  • Fred Greaves

    Another week gone by and still no meaningful response from Capture One Support.

    I did manage to find a solution... delete all versions of Capture One, preferences, and all other related files and then reinstall 13.1 fresh.

    Before I deleted everything, I made copies of my workspaces, styles, style brushes, etc. and then transplanted them into the new version. 

    It now works, but it is really a bummer that C1 Support was no help. 

    0
  • Robert Stebler

    Had the same issue on 4 different computers at our studio and the fix was the same.  Delete all preferences and app data.  Hoping that another patch release comes out soon before it spreads too much.

    0

Please sign in to leave a comment.