Teathering on M1 Macbook Pro
Anyone else having a Problem with teathering on a MacBook Pro M1?
-
Way too generic - which camera, OS version, C1P version, connection method, connection cable if used, camera firmware version, is cloud backup involved...
I don't think you can assert that you tried many devices to state the problem as a general problem with tethering feature, somehow.
(And is it "tethering", or are you looking for an elusive "teathering", whatever that is?)
0 -
I agree. We need more details. There are many factors that can influence tethering. Please tell us as many details as possible including OS version, Capture One version, camera make and model, camera firmware, type of connection and cable, length of cable, whether you have a card in the camera during tethering, and anything else you can provide.
1 -
I am sorry, it was too lazy of me to just ask without further details - here you go:
not working on capture version 16.3: teathering via usb teatherpro 3 meter cable from sony alpha a1 to macbookpro m1 (mac os 14), capture version 16.3. (23) - Card included and not included, neither works.
I also own capture 21 and everything works fine on the same computer.
Camera shows PC connection on capture version 23 but no image coming in. Very Strange ...
Thanks for your support!
Harry
1 -
I also own capture 21 and everything works fine on the same computer.
This kind-of points at compatibility problems between your version of Capture One and system. Can you check the exact full version strings for both? It's possible you just slightly ran out of support range.
More details can be read in the lower part of this page:
0 -
Thanks for the quick answer, the M1 MacBookPro is fully maxed out in terms of configuration:
Capture 21: 14.4.1.16
Capture 23: 16.3.2.32
The funny thing is, the same setup works perfecty on my macpro - everything is fine, just the M1 isnt ...
Harry
1 -
If it works with different version of CO on the same Mac I would assume something is wrong with your installation of version 16. Reinstall this version and check again.
0 -
All solved by going back to OS 13 - Thanks for providing me with the information!
Harry
1
Post is closed for comments.
Comments
7 comments