Jump to content

SL2 tethering: MacBook Pro M1, Windows11, Capture One 22 (15.1) - not working


Recommended Posts

Advertisement (gone after registration)

Hi all,

after a longer break I just started to set up may headshot workflow. I stopped a while ago with Windows 10/11 and the SL2, it was working in principle but often with connection dropouts (haven't tried the 3m tether pro cable, still on 5m).

In the meantime I switched back to Apple, new MacBook Pro 16 M1 (great!), but I get only C1 connection errors in the event panel). So PTP is not working at all, mass storage works. Tried the Windows 11 again, still the connection dropouts. 

Followed all tips here in the forum and from the C1 side, SL2 hast firmware 3.0, C1 22 has 15.1.

Any ideas from somebody? I will open a ticket to C1 and Leica but this will probably take a while. Maybe someone has encountered the some issues and found a valid workaround?

Will shoot on SD card in the meantime again. 

I still don't understand why Leica is doing so hard with tethering. There was a video recently here and everything looks easy but it is far from that actually.

Cheers

Rob

Link to post
Share on other sites

The SL2 doesn't show up in the USB section of the system, tried different cables. I have granted C1 all necessary rights to the Mac, tried C1 21 and 22. You can see also the error message generated by C1. To me this seems to be primarily a connection error. How to address this?

Cheers

Rob

 

 

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

Edited by Rob Cale
Link to post
Share on other sites

After some research on the C1 sites I found a solution for me, at least it works stable at the moment. Text from my C1 post

https://support.captureone.com/hc/en-us/articles/360002727817?page=1#comment_4405433029405

The following steps worked for me:

  1. Open terminal and enter

    tccutil reset SystemPolicyRemovableVolumes com.captureone.captureone15
    tccutil reset Photos com.captureone.captureone15
    tccutil reset All com.captureone.captureone15

    all together in the terminal, not step by step - it works only that way. Replace 15 with 14 for C1 21
  2. Connect the camera and switch it on - the Leica has options for the USB mode - select the last one - this brings up a menu on the Leica where you select PTP - all other combinations won't work
  3. Open C1 - the first time you have to give approvals due to the fact that you have reset access with the terminal command in step 1
  4. When ready, quit C1 before you switch off the camera. This seems the only way the setting got saved stable to C1. If you you switch off the camera first you have to do all steps again the next time you start

Good luck

Rob

Link to post
Share on other sites

good to hear you figured it out. If you rely on tethering you have to stay away form newly released Os-Updates at the beginning. I once happened to me with my GFX, I initially updated the system and wasn't able to tether with that machine for many days until Phaseone released a fix. 

Link to post
Share on other sites

vor 16 Minuten schrieb Photoworks:

that is all you need to do and use PTP connection with 3.1 or 3.2 cable.

Not really. It's a bit more to watch and follow steps in a certain order. There is an issue between Mac OS rights management, the M1 machine and the SL2. No card and PTP was not the point.

But in the end it is possible and works fine, currently not "plug and tether" with the combination described, but maybe there will be a fix at some point, e.g. a reset function within C1 to get the access rights set w/o terminal.

Link to post
Share on other sites

15 minutes ago, Rob Cale said:

Not really. It's a bit more to watch and follow steps in a certain order. There is an issue between Mac OS rights management, the M1 machine and the SL2. No card and PTP was not the point.

But in the end it is possible and works fine, currently not "plug and tether" with the combination described, but maybe there will be a fix at some point, e.g. a reset function within C1 to get the access rights set w/o terminal.

Capture one asks you to set it first time you open it..

in any case that is a security issue of MACOS. I see it in many programs.

 

Thanks for explaining.

Link to post
Share on other sites

vor 4 Minuten schrieb Photoworks:

in any case that is a security issue of MACOS. I see it in many programs.

Yes, the issue is on the Mac OS side, for sure. But maybe C1 could workaround this issue with a reset function within the tether preferences window, simply sending the reset commands that have to be figured out via C1 forum (glad I found it!) and sent via terminal (not stuff for every user) just with with one simple click as the issue may reappear under certain circumstances.

Link to post
Share on other sites

On 2/4/2022 at 6:29 PM, Rob Cale said:

Hi all,

after a longer break I just started to set up may headshot workflow. I stopped a while ago with Windows 10/11 and the SL2, it was working in principle but often with connection dropouts (haven't tried the 3m tether pro cable, still on 5m).

In the meantime I switched back to Apple, new MacBook Pro 16 M1 (great!), but I get only C1 connection errors in the event panel). So PTP is not working at all, mass storage works. Tried the Windows 11 again, still the connection dropouts. 

Followed all tips here in the forum and from the C1 side, SL2 hast firmware 3.0, C1 22 has 15.1.

Any ideas from somebody? I will open a ticket to C1 and Leica but this will probably take a while. Maybe someone has encountered the some issues and found a valid workaround?

Will shoot on SD card in the meantime again. 

I still don't understand why Leica is doing so hard with tethering. There was a video recently here and everything looks easy but it is far from that actually.

Cheers

Rob

I am glad you could find a solution 😀

I didn't have any issue with tethering in C1 22 15.1 with my SL2 and MacBook Pro M1 Max 16in. The SL2 was recognised immediately and it worked as usual.

If not a cable issue, may be it could be a setting/accessibility not confirmed in the Privacy panel in the Security and Privacy section of the System Preference? 

Edited by Hanno
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...