Skip to main content

macOS 10.15.2 - Tethered shooting broken

Comments

104 comments

  • Emile Gregoire
    Thanks for the heads-up. Did Apple also mention that they own the problem and will fix it?
    0
  • sampl_e
    They told me that C1 needs to push an update. There is nothing from Apple's side that will be fixed or at least nothing that support would tell me.

    Forgot to mention, I can only confirm this for a Canon 5D Mark IV.
    0
  • NNN636164445060918051
    I also can confirm this for both the Fujifilm GFX 50R and Nikon D850. Tethering is totally broken. Fun day at the studio today...
    0
  • Richard Brown
    I am on a 16 inch macbook pro also updated to 10.15.2 and no longer able to tether with EOS 5D MKIV , this is a huge problem as we have 3 large productions going.. will attempt to revertto older C1 or old Macbook .
    0
  • sampl_e
    Older version of C1 will not work as well. I tried 12.1.4 and tethering is broken as well. C1 replied to me on Twitter that they are aware of the issue and are working on a fix as quickly as possible, but no timeframe was mentioned. Only solution at the moment is to have an OS prior to 10.15.2
    0
  • Steve Lanman
    Can also confirm. We have 3 studio workstations. We did initial testing with Catalina 10.15.1 and C1 20 on 1 computer and everything worked fine. Updated the second computer and mac prompted to update to 10.15.2 now we can not shoot tethered. Do not update to 10.15.2 if you want to use C1 20. Went back to 12 for a temporary fix.
    0
  • paul schefz
    same here...tried the sony remote software and tethering works just fine with A7RIII and RX1RII....so this is a C1 issue
    0
  • photo by FA
    Well... CO20 has been validated for macOS 10.15.1 per release notes 😉
    0
  • NNN636164445060918051
    fatihayoglu wrote:
    Well... CO20 has been validated for macOS 10.15.1 per release notes 😉


    Yes. And the Mac OS Beta program is just for fun. Nothing to be bothered with and taken seriously as a software company making software for Mac OS 😉
    0
  • Ian Wilson
    NNN636164445060918051 wrote:
    fatihayoglu wrote:
    Well... CO20 has been validated for macOS 10.15.1 per release notes 😉


    Yes. And the Mac OS Beta program is just for fun. Nothing to be bothered with and taken seriously as a software company making software for Mac OS 😉

    Well, Phase One have said before that the problem with OS betas is that it is possible, and sometimes does happen, that the final release is not the same as the betas. It's possible that that is what has happened here, I suppose. 10.15.2 only came out today, and as pointed out Capture One doesn't claim to support it. (I have upgraded to 10.15.2, without thinking about that, in fact, and I seem to have been OK, though I don't do tethering.)

    Ian
    0
  • paul schefz
    not sure what is worse, Phase refusing to check their software with mac os betas or people defending phase and making snarky remarks....
    i get it, some people are 2 OS behind and use a 3 year old version of C1....because it works....
    not sure how that would work out for phase in general though....it would seem that people staying up to date is in phases interest....I mean i just paid for the C1 pro update...just so happens that my tethering mbp decided to run an automated update, which is probably a good thing anyway considering most of these are necessary because of bugs and overall security....
    apple is extremely transparent now, betas come out 2-3 weeks before....how hard is it to just run it on a machine and test C1? wouldn't that make sense? i mean they have to run it now and come up with a fix...checking the betas just makes life a little easier for those who stay up to date.....with their os and with C1....which is overall in phase's interest....
    0
  • NNN636164445060918051
    just so happens that my tethering mbp decided to run an automated update, which is probably a good thing anyway considering most of these are necessary because of bugs and overall security....
    apple is extremely transparent now, betas come out 2-3 weeks before....how hard is it to just run it on a machine and test C1? wouldn't that make sense? i mean they have to run it now and come up with a fix...checking the betas just makes life a little easier for those who stay up to date.....with their os and with C1....which is overall in phase's interest....


    Same thing happened to me. Left my computer in the studio and the update installed over night. I can’t understand why Phase just couldn’t try the betas and at least come out with a warning until they have fixed the problem Mac OS 10.15.2 causes. The last beta came out 1 week ago and it’s the same build that now is pushed out. There’s no excuse.
    0
  • ---
    PSS wrote:
    not sure what is worse, Phase refusing to check their software with mac os betas or people defending phase and making snarky remarks....
    i get it, some people are 2 OS behind and use a 3 year old version of C1....because it works....
    not sure how that would work out for phase in general though....it would seem that people staying up to date is in phases interest....I mean i just paid for the C1 pro update...just so happens that my tethering mbp decided to run an automated update, which is probably a good thing anyway considering most of these are necessary because of bugs and overall security....
    apple is extremely transparent now, betas come out 2-3 weeks before....how hard is it to just run it on a machine and test C1? wouldn't that make sense? i mean they have to run it now and come up with a fix...checking the betas just makes life a little easier for those who stay up to date.....with their os and with C1....which is overall in phase's interest....



    100% agree - I get cyber blackmailed at least once in a month what makes me think updating the os as fast as possible is a good idea and indispensable this days.
    0
  • sampl_e
    They have indeed updated their FAQ page with information specific to this problem, but that’s not really a heads up. I’d rather expect a newsletter or anything like it. They confirmed to me that there was a sudden change in the beta that was not in there before. However as stated above the beta version released a week ago is the same as the published build they should have had a fix available then. I’ve asked support for a timeframe, but still haven’t received feedback
    0
  • ---
    sampl_e wrote:
    They confirmed to me that there was a sudden change in the beta that was not in there before.


    blame apple - sad, but this is their standard excuse with any OSX related problems.
    0
  • Ian Wilson
    I think I read that the newest MacOS release had caused a similar tethering problem with Lightroom, so perhaps blaming Apple is appropriate this time?

    Ian
    0
  • NNN636164445060918051
    Ian3 wrote:
    I think I read that the newest MacOS release had caused a similar tethering problem with Lightroom, so perhaps blaming Apple is appropriate this time?

    Ian


    Lightroom CC tethering works just fine with Mac OS 10.15.2 so does Fuji's tethering software. It's a C1 issue.
    0
  • sampl_e
    Lightroom tethering did not work for me on macOS 10.15.2 - however that's why Apple releases betas so that developers can adjust their software accordingly. At least a notification to all users by email would have been nice, because I think not many are checking the FAQ section for these kind of information.
    0
  • sampl_e
    Latest comment I got on the issue:

    We can't comment on a possible timeframe. It's unfortunately not always easy to accommodate unforeseen changes in operating systems.

    Just received from email-support:

    It is a high priority issue and R&D are working on solving it.

    Please keep in mind, that due to our policy we do not comment or give out any information on future products and development.
    0
  • alessandro cecconi
    It is inexcusable in 2019 to have this problem. Phase has access to betas way before they are released but are simply too lazy to check them. There is simply no other way to explain this. Beta 10.15.2 was out to developers more than 3 weeks ago. Betas are sent out to check it something is broken. One more time, betas are sent out to check if something is broken. So phase ignored the problem and in their snotty attitude never bothered to send out a notice to customers not to upgrade. I don't expect them to have a fix on time but I do expect them to give a heads up not to upgrade. This, unfortunately, is the attitude when you have a monopoly on things. One day someone will come up with a better mousetrap and maybe they will change,
    Alessandro
    0
  • alessandro cecconi
    Horseoncowboy wrote:
    sampl_e wrote:
    They confirmed to me that there was a sudden change in the beta that was not in there before.


    blame apple - sad, but this is their standard excuse with any OSX related problems.


    Even if that is true that it was a last change in the beta, they should have warned customers not! to upgrade. As I said I don't expect them to have a fix but I do expect them to warn customers of a crash.
    0
  • ---
    alececco wrote:
    It is inexcusable in 2019 to have this problem. Phase has access to betas way before they are released but are simply too lazy to check them. There is simply no other way to explain this. Beta 10.15.2 was out to developers more than 3 weeks ago. Betas are sent out to check it something is broken. One more time, betas are sent out to check if something is broken. So phase ignored the problem and in their snotty attitude never bothered to send out a notice to customers not to upgrade. I don't expect them to have a fix on time but I do expect them to give a heads up not to upgrade. This, unfortunately, is the attitude when you have a monopoly on things. One day someone will come up with a better mousetrap and maybe they will change,
    Alessandro



    ...it always work this way because they can rely on uncritical fans and their affiliates to play issues down here and around the web. c1 20 seems to be released to early anyway because it is the buggiest update since years. my guess is that the development team is understaffed which is great for the investors but bad for us customer.
    0
  • FirstName LastName
    phase one always had this issues with an apple update, as far back to version 4. it was always the only program that forced me to keep the system a version behind.

    I run a test on Catalina and it was working, so I was finally up to date. then the update and no camera shows up in C1P

    the use to blame canon SDK, then Sony .. but it is probably always Capture one that doesn't work, you can count on it.

    Usually after a few months it works again after they found the problems.

    Disappointment
    0
  • TitleUnknown
    Confirmed broken with 5dmk4 and Fuji X Pro-2.

    Tethered all day yesterday with 10.15.1, no issues.

    EOS Utility wont work either. It just hangs and crashes.

    This is 100% on Apple
    0
  • paul schefz
    Not sure whose fault this is but the Sony remote works just fine tethering several different cameras and a friend claims that his Sony works fine tethered with LR...
    0
  • Paul Steunebrink
    The bottom-line is that tethering relies on basic functions provided by the operating system, macOS in this case. The Catalina 10.15.2 update changed that function intentionally. Now all applications affected need to release an update to accommodate the change.

    And for those who talk (or complain) about the past: yes, Apple has done similar actions before in the past.
    0
  • alessandro cecconi
    Paul_Steunebrink wrote:
    The bottom-line is that tethering relies on basic functions provided by the operating system, macOS in this case. The Catalina 10.15.2 update changed that function intentionally. Now all applications affected need to release an update to accommodate the change.

    And for those who talk (or complain) about the past: yes, Apple has done similar actions before in the past.


    Paul, I understand your position but Phase One has been categorically ignoring betas from Apple. While Apple changed the I/O driver for security reasons, that change was present in the last two betas. While a fix was not expected, a warning to customers was! That is why Apple releases betas to the developer. If Phase had bothered to test it, they would have known and didn't warn customers. If they didn't bother to test then plain shame on them. Customer service from Phase has been getting worse and worse. If you file a service report chances are they will not answer for days, Releases are rushed out and are buggy. It s just plain disregard for customer service. Now I understand that they basically have a monopoly on professional software but I sincerely hope that karma will serve them a plate of " here is a better product and better customer service" food soon
    0
  • Duncan Andison
    Betas are are made available to Software Developers not just to see or test wha's new but to make sure their software works ok. If Phase One had done this, they could have released an earlier warning not to update until a fix was found. Instead, they have turned around and said to go a search the internet on how to roll the OS back... Thanks Phase One, like I have the time to do that.

    At the very least, Phase One should go and find out how to roll back and then post details to their customers on how to do it. It's YOUR software and you (like all other developers) have access to betas to ensure your product continues to work with new releases... you've failed to do that, that's not Apples fault.
    0
  • sampl_e
    Latest from Twitter:

    We are always testing beta versions of Mac OS updates but every once in a while it happens that the beta is not identical to the actual release. We are working very hard to fix the issue - We still have full support for Catalina, version 10.15.1 for Capture One 12.1.4 and 20.
    0
  • Dubin Laurent
    And Canon EOS Utility 3 has the same problem : unable to connect with camera ...
    0

Please sign in to leave a comment.