Skip to main content
Shipp
Known Participant
Mar 16, 2021 4:07 PM UTC
Released

P: Lightroom Classic: Tethered capture not working after update Canon 5Ds

Updated LRC and now tethered capture window doesn't even show. Files are not transferring to computer regardless. 

 

LR Classic 10.4

Canon 5ds

Catalina 10.15.7

 

I rolled back to version LRC 10.3 because I have to shoot today but here are my specs

 

Lightroom Classic version: 10.3 [ 202105281559-8dc50eb4 ]
License: Creative Cloud
Language setting: en-AU
Operating system: Mac OS 10
Version: 10.15.7 [19H1323]
Application architecture: x64
Logical processor count: 20
Processor speed: 3.6GHz
SqLite Version: 3.34.0
Built-in memory: 131,072.0 MB

 

Also - is it possible that the software has updated when I have preferences set to no automatic updates for this very reason?

This topic is closed to new replies. Start a new post to keep the conversation going.

44 replies

Inspiring
Jun 10, 2021 6:59 PM UTC

It's working for me... now on 11.4, M1 powered MacBook Air.  It steadily improved since I started this thread.  The tethering experience for me is the best its ever been.  I've been tethering Canons to LR for more than a decade now.  The only drawback now is you have to relaunch LR into Rosetta to start tethering as the tethering part of LR does not support running natively on Apple Silicon yet.  I'm hopeful that changes soon.

Translate
AndyFranck
Participating Frequently
Jun 10, 2021 6:44 PM UTC

In my early use of 10.3 this issue does not appear to be fixed.  (Using MacOS 10.15.7 and Canon R5)

Translate
Inspiring
Apr 5, 2021 1:13 PM UTC

I've recreteated the issue with the 5D mkIV as well, I am usually using an extension USB cable along with a shorter cable, I removed the extension and had the same error with both cameras.

I've taken a shaky smartphone video (actually two, one with each camera), how should I best send it?

Translate
Inspiring
Apr 5, 2021 10:36 AM UTC

I'm using a Canon EOS 5DS R tethered to Lightroom, but I could try with a 5D mk IV later.

With the 5DS R, it happens every time I close the tethered shooting bar and want to start it again

I will try to take a video later as well

Translate
rubyk58010202
Participating Frequently
Apr 5, 2021 10:03 AM UTC

*arpad_ikuma_csizmazia  Which camera are you using? Does it happen everytime? Is it possible for you to share a video of issue? 

Thanks,

Ruby

Translate
Inspiring
Apr 3, 2021 2:35 PM UTC

It works fine as long as the tether capture bar (or "detecting camera") stays on the screen.  Once that tether capture bar is closed, you have to relaunch Lightroom.  I mainly use a 5DsR as well

Translate
Inspiring
Apr 3, 2021 2:34 PM UTC

Forgot to add, I'm using Windows 10.

Translate
Inspiring
Apr 3, 2021 2:32 PM UTC

*Bob_Smith does that problem occur for you when you switch the camera off and back on? Because that doesn't cause any issue for me, neither does disconnecting the tether cable as it seems to be the case for you.

So perhaps yours is a new camera issue as well as this...

I'm using an old 5DS R btw

Translate
Inspiring
Apr 3, 2021 2:28 PM UTC

I'm seeing the same thing except without any error message.  It's just impossible to restart tethered capture without relaunching LR.  At first I thought it was specific to a newly supported camera.  It isn't. It was reported in this thread... and confirmed a few times.  

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-tethered-canon-r5-works-in-102-sort-of/6050d7b13facef17f7f33564 

Aside from this I feel like tethered capture is generally more reliable in 10.2.  Hopefully they'll fix this annoyance soon.

Translate
Inspiring
Apr 3, 2021 12:57 PM UTC

Hello, I've been encountering this issue since the 10.2 update:

After quitting the tethered capture while still keeping Lighroom open and afterwards trying to start tethered capture again, upon clicking on 'Start tethered capture', I will immediately get this error:

unexpected error performing command: ?:0 attempt to index a nil value

Only restarting lightroom will let me start tethered capture again.

Hope this can be fixed soon!

Best,

Ikuma

Translate