macOS 10.15.2 - Tethered shooting broken
After the update to macOS 10.15.2 tethered shooting with the latest version of Capture One 13.0 is broken. No connection can be accomplished and the camera will not show up in C1. There was a change in the OS that causes the issue. Apple support confirmed this just now. This change also affects Lightroom, for anybody interested.
0
-
I had the same problem here with a Sony A7RIII!
I'm using the new Macbook Pro 16" (which only runs with Catalina, I am not able to downgrade the OS).
At the beggining of the week decided to give a try on CaptureOne 20, downloaded it, install it, started working tethered and then yesterday I tried to to more tethered stuff and the software does not recognized the camera.
The only two things that happen in this space of time is that I upgraded the MacOs and I also tried to updated the cameras firmware, but it also was not found by Sony's software.0 -
sampl_e wrote:
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.
Not buying that. I've been downloading, testing and using Apple betas for some years now, on IOS, Mac and Watches and the build details of the GM's match those of the final releases. The final 2 betas tend to be minor changes/fixes. The release names tell you a lot about how many times it takes to compile the version and how many versions there were between betas. There would be zero point in betas if the final release was different to the beta gm.
Edit. It should also be noted that 10.15.2 was released on the 11th and we received the warning from Phase on the 13th...I updated my laptop last night and held off on my main desktop computer so now I have to mess around trying to find away to roll everything back. Not impressed at all.0 -
NNN636164445060918051 wrote:
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.
LightroomCC can import files stored on a card in a camera, but can't shoot tethered ...0 -
I have a JOB to be done and I need live view to make live easier and the correct name the products I am shooting.
I found a workaround/solution for now. Just downloaded the latest versions of the Sony Remote app, it found my camera, so I will use it to live view and I will using a hot folder on CaptureOne.0 -
It is inexcusable in 2019 to have this problem
Easy to say. Adobe (LIghtroom), Nikon (Capture 2), Canon (EOS Utility) were all caught by surprise.
The tendency that a user does not feel the responsibility for its own system and find he/she can update its system as soon as an update is available without risk, is not a professional attitude. That user apparently does not take time to reflect on the update or wait till others have done so, taking the risk of damage and have time to report.
Warnings came in just hours after the 10.15.2 release was out on this subforum and Capture One was informed. I immediately responded to my social network with messages to hold off from the update. Larger Phase One/Capture One suppliers followed within 24 hours and Capture One has sent out an email within 48 hours. I have seldom seen such a quick response, if ever.
I think it is time users get educated on how to work professionally with their systems. How everything (computer hardware, operating system, application, peripherals) is linked like a chain.
That they understand an application is never compatible with a new macOS (or Windows update) by nature. And that you always take a risk by updating before the creator of an application gives the green light in their release notes (Capture One 12 and 20 are explicitly supported up to 10.15.1 as per release notes).
It is very easy to create a second macOS (or Windows) volume on your system, and see how new versions work out, if you like to try yourself. But start with disabling auto-update. And give any update the time it requires.
There is no excuse for being not responsible and professional with regard to your own update policy.0 -
Paul_Steunebrink wrote:
It is inexcusable in 2019 to have this problem
Easy to say. Adobe (LIghtroom), Nikon (Capture 2), Canon (EOS Utility) were all caught by surprise.
The tendency that a user does not feel the responsibility for its own system and find he/she can update its system as soon as an update is available without risk, is not a professional attitude. That user apparently does not take time to reflect on the update or wait till others have done so, taking the risk of damage and have time to report.
Warnings came in just hours after the 10.15.2 release was out on this subforum and Capture One was informed. I immediately responded to my social network with messages to hold off from the update. Larger Phase One/Capture One suppliers followed within 24 hours and Capture One has sent out an email within 48 hours. I have seldom seen such a quick response, if ever.
I think it is time users get educated on how to work professionally with their systems. How everything (computer hardware, operating system, application, peripherals) is linked like a chain.
That they understand an application is never compatible with a new macOS (or Windows update) by nature. And that you always take a risk by updating before the creator of an application gives the green light in their release notes (Capture One 12 and 20 are explicitly supported up to 10.15.1 as per release notes).
It is very easy to create a second macOS (or Windows) volume on your system, and see how new versions work out, if you like to try yourself. But start with disabling auto-update. And give any update the time it requires.
There is no excuse for being not responsible and professional with regard to your own update policy.
Hurray ! this is the kind lecture we professional photographers have waited for and it demonstrates the attitude many here see as the problem. I also wonder if your thoughtful advise is also valide for captureone updates or do you make an exemption in this case ?0 -
Horseoncowboy wrote:
Paul_Steunebrink wrote:
It is inexcusable in 2019 to have this problem
Easy to say. Adobe (LIghtroom), Nikon (Capture 2), Canon (EOS Utility) were all caught by surprise.
The tendency that a user does not feel the responsibility for its own system and find he/she can update its system as soon as an update is available without risk, is not a professional attitude. That user apparently does not take time to reflect on the update or wait till others have done so, taking the risk of damage and have time to report.
Warnings came in just hours after the 10.15.2 release was out on this subforum and Capture One was informed. I immediately responded to my social network with messages to hold off from the update. Larger Phase One/Capture One suppliers followed within 24 hours and Capture One has sent out an email within 48 hours. I have seldom seen such a quick response, if ever.
I think it is time users get educated on how to work professionally with their systems. How everything (computer hardware, operating system, application, peripherals) is linked like a chain.
That they understand an application is never compatible with a new macOS (or Windows update) by nature. And that you always take a risk by updating before the creator of an application gives the green light in their release notes (Capture One 12 and 20 are explicitly supported up to 10.15.1 as per release notes).
It is very easy to create a second macOS (or Windows) volume on your system, and see how new versions work out, if you like to try yourself. But start with disabling auto-update. And give any update the time it requires.
There is no excuse for being not responsible and professional with regard to your own update policy.
Hurray ! this is the kind lecture we professional photographers have waited for and it demonstrates the attitude many here see as the problem. I also wonder if your thoughtful advice is also valide for captureone updates or do you make an exemption in this case ?
My advise applies to all updates. That includes Capture One as well.0 -
My advise applies to all updates. That includes Capture One as well.
yes sure... so where can I find your last post with the advise to wait with installing c1 before all bugs are fixed and it is tested....
to call user " not responsible and professional" when they follow the advice of apple is insulting und plain stupid. there is more to consider than just if c1 works. most professionals use a lot of different software, from billing to image processing so what you describe is unrealistic BS because as paying customers I think we have the right to aspect that the software we have paid for works without testing everything before installing.
bugs can happen that's the nature of software but how a company response can make a difference.0 -
for those who are very good with Mac OS :
is it possible that the problem of tethering has a link with the "Input Monitoring" tab in the security of system preferences ?
does someone know how to force an app to "be" in that tab ?
thank you !0 -
Paul_Steunebrink wrote:
It is inexcusable in 2019 to have this problem
Easy to say. Adobe (LIghtroom), Nikon (Capture 2), Canon (EOS Utility) were all caught by surprise.
The tendency that a user does not feel the responsibility for its system and find he/she can update its system as soon as an update is available without risk, is not a professional attitude. That user does not take time to reflect on the
Paul, your opinion is biased at best and it's ok. But to call us irresponsible because we updated a system I think is way above decency. I have had C1 since version 6 and it is the only software that consistently has crashed whenever Apple makes a major update. Every year around September with the release of the new system we have become used not to update. But now even on smaller incremental changes? WTF. I don't think our money crashes in their bank account, and while we all understand that software has a value and all that good stuff, their customer services just plainly suck. Of course we could be just irresponsible about 😄0 -
I expected Paul to get a lot of flack but I think he's got a point. I've been burned in the past for updating too soon - both OS upgrades (Sierra was hell on my MacBook Pro) and imaging (mostly Adobe - I've lost hours and hours of work due to fault dot-updates). Apple has built up a track record as of late; their OS's are immature until at least .3 or .4 is released. CaptureOne I'm afraid is no different. Maybe more of us should participate in beta testing, I don't know, but I do know through hard experience that for production work it is best to hold off on updates for a while until the dust has settled down.
YMMV0 -
Laurent DUBIN wrote:
for those who are very good with Mac OS :
is it possible that the problem of tethering has a link with the "Input Monitoring" tab in the security of system preferences ?
does someone know how to force an app to "be" in that tab ?
thank you !
think input monitoring is related to the keyboard.0 -
Emile wrote:
I expected Paul to get a lot of flack but I think he's got a point. I've been burned in the past for updating too soon - both OS upgrades (Sierra was hell on my MacBook Pro) and imaging (mostly Adobe - I've lost hours and hours of work due to fault dot-updates). Apple has built up a track record as of late; their OS's are immature until at least .3 or .4 is released. CaptureOne I'm afraid is no different. Maybe more of us should participate in beta testing, I don't know, but I do know through hard experience that for production work it is best to hold off on updates for a while until the dust has settled down.
YMMV
paul has no point because he completely ignores that we are much more vulnerable than say 20 years ago. nowadays software requires us to be online for licence checking, we are connected to different networks all the time and everybody who has ever monitored the massive unauthorised attempts to connect to his system would not be so arrogant to blame user for updating their os to close security loopholes.0 -
Horseoncowboy wrote:
paul has no point because he completely ignores that we are much more vulnerable than say 20 years ago. nowadays software requires us to be online for licence checking, we are connected to different networks all the time and everybody who has ever monitored the massive unauthorised attempts to connect to his system would not be so arrogant to blame user for updating their os to close security loopholes.
Apple releases security updates for previous OS's, so there's that. I've never been bitten by not updating immediately while I *have* been bitten by upgrading immediately, and I'm as promiscuous as the next when it comes to connecting to other networks - no escaping it as event photographer. Maybe I've been lucky but ever since I've started using Mac some 12 years ago my woes with attacks have been over. But again: YMMV.
As a beside: let's *all* refrain from calling each other irresponsible, non-professional, stupid and arrogant. It's not helpful in any way.
Have a great weekend!0 -
Horseoncowboy wrote:
Laurent DUBIN wrote:
for those who are very good with Mac OS :
is it possible that the problem of tethering has a link with the "Input Monitoring" tab in the security of system preferences ?
does someone know how to force an app to "be" in that tab ?
thank you !
think input monitoring is related to the keyboard.
good to know ! thank you !
I'm quite sure there may be an issue with the security levels of Catalina ...0 -
Emile wrote:
Apple releases security updates for previous OS's, so there's that.!
while this is true 10.15 has brought massive changes to improve security compared to 10.14 so I don't think they are equal in this regard.0 -
I have 10.15.2 / p65 back / MacBook Pro 2016 and have no prob with
tethered shooting ? what's up with that.0 -
RICHARD311 wrote:
I have 10.15.2 / p65 back / MacBook Pro 2016 and have no prob with
tethered shooting ? what's up with that.
No no no, you’re not allowed to participate in this topic 😄0 -
Horseoncowboy wrote:
(...)
I think we have the right to aspect that the software we have paid for works without testing everything before installing.
This assumption is exactly the point of my post about who is responsible for upgrading your system, and when, and who carries the responsibility. I think that I am. And I carry the consequences.
Others have delegated that responsibility to their respective creators (at least in their minds) and do not want to carry the consequences.
That is fine. We can exchange how we feel about that. And maybe that is confronting for some of us. Others take a lesson from it or respectfully disagree.0 -
RICHARD311 wrote:
I have 10.15.2 / p65 back / MacBook Pro 2016 and have no prob with
tethered shooting ? what's up with that.
firewire vs usb ?0 -
RICHARD311 wrote:
I have 10.15.2 / p65 back / MacBook Pro 2016 and have no prob with
tethered shooting ? what's up with that.
always interesting to say to give the maximum informations to developers !
I hope they read the forum ! 😊0 -
Emile wrote:
Maybe more of us should participate in beta testing,
I think that is exactly the point....i dont want to be a beta tester...and at this point running the latest C1 software is pretty much beta testing....i happen to think that C1 20 is a great release, I really like the new features....I pre ordered, worked with the C1 betas to make sure everything runs well...
in this case it is very clear that phase did not do their part: simply download the mac OS beta and run C1...that's it....if there is a problem, give the warning....
i honestly also dont understand how bad the issue can be....software should be sandboxed now, since tethering does work on a system level if cant be that hard to fix...
but of course blaming the user is always the best solution
btw: this really never happens with any other software i use....adobe always gives a warning if a mac os update breaks things....0 -
Paul_Steunebrink wrote:
Horseoncowboy wrote:
(...)
I think we have the right to aspect that the software we have paid for works without testing everything before installing.
This assumption is exactly the point of my post about who is responsible for upgrading your system, and when, and who carries the responsibility. I think that I am. And I carry the consequences.
Others have delegated that responsibility to their respective creators (at least in their minds) and do not want to carry the consequences.
That is fine. We can exchange how we feel about that. And maybe that is confronting for some of us. Others take a lesson from it or respectfully disagree.
we are photographers and not test engineers and and I hope that everybody in this game acts in our interest especially when they have taken our money. so I aspect apple to improve the os and make it more secure and p1 to make c1 work with it, noting else. we are customer and we are entitled to have software that works as promised without testing and if not get at least informed as fast as possible. it is the very nature of digital that os evolve and apps need to follow. most developer can keep up with this task without complaining about irresponsible user and apple.....0 -
MacOS Catalina 10.5.2 here.
Moreover the tethering issue with C1 20, My Sony A7rIII refuse to connect to my macbook: it remains in a ‘connecting’ mode but nothing else happens, no volumes mounted on Finder.
I think the issue it’s definitely in macOS side.0 -
NNN636027279670204457 wrote:
MacOS Catalina 10.5.2 here.
Moreover the tethering issue with C1 20, My Sony A7rIII refuse to connect to my macbook: it remains in a ‘connecting’ mode but nothing else happens, no volumes mounted on Finder.
I think the issue it’s definitely in macOS side.
download sony software suite works just fine, should also work with hot folder in C200 -
PSS wrote:
NNN636027279670204457 wrote:
MacOS Catalina 10.5.2 here.
Moreover the tethering issue with C1 20, My Sony A7rIII refuse to connect to my macbook: it remains in a ‘connecting’ mode but nothing else happens, no volumes mounted on Finder.
I think the issue it’s definitely in macOS side.
download sony software suite works just fine, should also work with hot folder in C20
Not for me, I've just downloaded the latest version of Sony Suite and tried tethering with Remote app:
still unable to connect to my A7rIII.0 -
PSS wrote:
Emile wrote:
Maybe more of us should participate in beta testing,
I think that is exactly the point....i dont want to be a beta tester...and at this point running the latest C1 software is pretty much beta testing....i happen to think that C1 20 is a great release, I really like the new features....I pre ordered, worked with the C1 betas to make sure everything runs well...
in this case it is very clear that phase did not do their part: simply download the mac OS beta and run C1...that's it....if there is a problem, give the warning....
i honestly also dont understand how bad the issue can be....software should be sandboxed now, since tethering does work on a system level if cant be that hard to fix...
but of course blaming the user is always the best solution
btw: this really never happens with any other software i use....adobe always gives a warning if a mac os update breaks things....
You snipped the part where I said "I don't know" immediately after what you chose to quote. And I said "Maybe" and "I don't know" with a purpose: I really don't know how many people participate in beta testing. There's a bug where the undo stack gets all messed up when you use the direct color editor - one should think something like that would have been found with enough beta testers. So that's what I was referring to: are there enough beta testers? I don't know! If not, we're the ones who get bitten in the arse. Hence my comment.
This obviously has got nothing to do with the current tethering situation under 10.15.2. I'm not the one to jump to conclusions immediately (my wife's a diplomat, one tends to learn from each other) but I'm also not here to defend Phase. They've ignored their problems with the catalog function for years; each and every time a new OS arrives they act surprised. When they bought Media Pro they neglected to update it when Capture One was upgraded, for many months, time and time again. So there's quite a lot of improvement to be wished for. But a little reality check is in order too: all the major software companies rush out updates these days based on a financial cycle, even though the product might not be ready. Apple, Adobe, PhaseOne: not a lot of difference. Hence my waring: on a production platform, stay away from the updates for a while.0 -
Has anyone here been able to downgrade from 10.15.2 to 10.15.1 ? If so can you please let me know how you did that?
Please only answer if you done it. thanks!
It would be helpful if Phase posted instructions.0 -
dale11833 wrote:
Has anyone here been able to downgrade from 10.15.2 to 10.15.1 ? If so can you please let me know how you did that?
Please only answer if you done it. thanks!
It would be helpful if Phase posted instructions.
I used a time machine backup. If you choose a backup from before the OSX 10.15.2 update you'll end up with the previous OS, 10.15.1. In order to do the restore, I restarted in recovery mode (hold Command-R at startup). When choosing to restore from Time Machine it will show you every incremental backup along with the OS version. There is no need to wipe the hard drive or reinstall the old OS, it all happens automatically by choosing the pre-10.15.2 backup.
My last backup was Wed evening at 10:30 PM, I then installed 10.15.2 that same evening. Recovering from that time machine backup took 6 hours the next day. Everything has worked fine since then. You will lose any work you've done on your drive since that time machine backup, so you've got to back that data up somewhere else so you can restore it after.0 -
I have a new MBP 16. So no time machine backup. Guess I ain't using the new laptop tomorrow....☹️
I called apple support. It is literally impossible to revert, with my situation. Apple musta done some heavy lifting when going to 10.15.2.0
Post ist für Kommentare geschlossen.
Kommentare
104 Kommentare