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

macOS Sonoma 14.2 - breaks tethering across multiple applications, please update to 16.3.3 if possible

Comments

23 comments

  • Official comment
    Jack W
    Admin

    Today at 13.30 we released Capture One Pro (16.3.3) to address this behavior: https://www.captureone.com/en/account/download

  • Jon Rauschenberger

    If it's not a "Capture One issue" how will C1 be supporting 14.2 soon? Are you (C1) stuck waiting for Apple to release an update? 

    Also, if this was a known issue, there should have been proactive notice sent to customers warning us not to install the upgrade. Given that it's just a minor point release update to the OS, there's no reason to think it would break something as fundamental as tethering. 

    I just had shoot where I couldn't tether because I installed the update last night. 

    4
  • Charlie Bard

    Autoupdate caught me out. Might want to make some noise about this on socials to prevent a bad day

     

    Edit: The earlier version of C1 does work a treat. I assume I'll be able to edit in the latest post shoot without an issue too

     

    2
  • Sergi Salillas
    Admin

    Jon Rauschenberger
    To attend to your questions. These are 2 different things. One, Sonoma 14.2 not being yet supported by Capture One (Which shouldn't break tethering), and second Sonoma 14.2 breaks camera connectivity not only in Capture One but with other software too.

    Soon we will be supporting Sonoma 14.2, but the Tethering issue also needs to be fixed by Mac. Capture One is also looking into fixing it from our end.  

    As is mentioned in the post reverting to 16.2 for some users this can bypass the Sonoma 14.2 issue. 
    However, the best practice would be downgrading macOS.

    2
  • FirstName LastName

    Totally understand that Sonoma 14.2 issues aren't your fault, but not having resources in place to regression test your expensive application when OS updates come out, and proactively sending out an advisory email, is inexcusable.

    And, yes, the same goes for Adobe!

    2
  • Norman Posselt

    I always consider this way of dealing with (professional) users of (professional) software to be questionable. Adobe and Autodesk are sometimes similar. So it’s not a question of actual company size. It’s more a question of attitude. Developer betas from Apple have been available for many weeks. It makes you wonder what you’re paying money for every month ... only to be told not to install security-relevant system updates. Thank you. 

    2
  • Jack W
    Admin

    It’s not a Capture One issue… but yes, we will be supporting macOS 14.2 soon.

    1
  • Sergi Salillas
    Admin

    Johnny Papagni
    Thank you for your message. It is more complicated than that due to changes in Sonoma 14.2 that affect only Capture One 16.3. 
    However, we are working on that and we are getting positive responses from our engineers that this very soon will be fixed. 

    1
  • Stephen Long

    Hey C1 team, I am running C1 20, 13.1.2.37. Is this now never going to tether to MacOS 14.2? Is there a workaround which will get it running? I have no need to upgrade to the latest C1 and no wish to spend more money on software but find it very frustrating that something that was working fine is now broken.

    1
  • Fredgotts

    I was using the MacOS 14.2 beta for a long time and C1 v16.3 tethering never worked, then i dowgraded C1 to v16.2.6.7 and tethering started working again so you don't need to dowgrade MacOS with is a pain in the ass. Lightroom is broken too btw, no tethering and you can't import images straight from the camera anymore.

    0
  • Philip Skillern

    Also autoupdate got me no loner able to connect my camera. please update ASAP got an important shoot tomorrow. Do the capture one devalopment team not run the macOS developer betas to have a fix ready to go when a Mac OS update is released.

    0
  • Johnny Papagni

    But if version 16.2 works, can't you use the same tethering method in version 16.3 that bypasses the problem?

    0
  • Philip Skillern

    so where do I find older version 16.2.6 am I stupid can't seem to see it anywhere on your site. at least put a download to 16.2.6 in your post at top. this is a joke. 

     

    As a workaround, Capture One 16.2.6 does not get affected by this Sonoma 14.2 issue. Therefore downgrading Capture One could also be a workaround, however, keep in mind that Sonoma 14.2 is not supported yet. 

    0
  • Marcin Mrzygłocki
    Top Commenter

    Philip Skillern might depend on the kind of license you have got and when. Most likely should be enough to scroll down to "Previous versions" on https://www.captureone.com/en/account/download

    0
  • Walter Rowe
    Moderator
    Top Commenter

    OS releases are not entirely locked and stable until they are publicly released. While Capture One likely was testing 14.2 during the beta phase it is possible that Apple made last minute updates that were not previously available for testing.

    0
  • Norman Posselt

    Walter Rowe That is totally normal. But I certainly know that the Build number of macOS 14.2 did not change for five days (before release); RC 2 became the final public version. That is almost a week or 40 normal work hours … So there was really not single minute to check/ test and give a warning? If so, that is even more concerning. Anyway I am looking forward to get an update.

    0
  • Frank Schroeter
    Moderator

    We have today released Capture One 16.3.3, which is compatible with macOS14.2.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Stephen Long CO 20 is not certified for Sonoma so don't expect an update. CO 16.3 was effectively CO 24 (17) but CO seems to be parting ways with traditional version numbering. You will probably have to upgrade. Probably not the message you were hoping for.

    0
  • Frank Schroeter
    Moderator

    Generally you have to remain within the system requirements of the product you use. See details here: https://support.captureone.com/hc/en-us/articles/360007791797-All-about-perpetual-and-subscription-licenses .

    0
  • Frank Schroeter
    Moderator

    Walter Rowe, it is important to differentiate between product name and version number. Before Capture One 20, the "major version" was also part of the product name, e.g. Capture One 12 was also version 12.x. From 2020 to 2023, we included a number in the product name that related to the year: Capture One 20 to Capture One 23 . The version number on the other hand has always been continuous, so Capture One 20 was version 13.x, Capture One 21 version 14.x, aso.  Since we moved to the new perpetual license model, the product name is without any number, but we are of course still counting versions. 

    0
  • Jürgen Pfeiffer

    Hello Stephen Long,

    does C1 13.1.2.37 tethering work in Mac OS 14.1? Or which OS do you actually use? Can't say anything about C1 20, but I tried tethering with a Nikon Z camera on C1 22 running Mac OS 14.2 and it worked. So, when the tethering worked in OS 14.1 I think 14.2 should be no problem.

    This is just my personal experience, so try at your own risk

    I suppose the tethering problems had something to do with the new tether features introduced with C1 16.3

     

    0
  • RVZ

    Trying Capture One 16.3.3 with macOS14.2 on a crash-test machine (Mac Mini M1).

    Now C1 sees my cameras, the shutter is actually released by pressing the capture button in C1, but can't get any image dowloaded to my computer. Tried 5D Mk3, Eos R5... Same each time.

    Edit : Re-re-re booted the computer, now the R5 captures are downloaded correctly. But nothing better for 5D MK3.

    Edit 2 : Now using macOS 14.2.1 and CaptureOne 16.3.3.6, and all works as intended with any supported camera, including a 5DM3.

    0
  • Chris S

    Seems to be working on machines without the M2 chipset, just ran in to this tether loss problem too on my other two machines! Capture One needs to address this soon!

    -1

Please sign in to leave a comment.