P: Canon tethering stopped working after updating to Lightroom Classic v15.4

Hello,

I’m having the same issue with my Canon R1. No photos are being written to the hard disk on my MacBook Pro, only to the CFExpress cards. 

Having this same issue 

I am experiencing a tethering issue with Lightroom Classic and my Canon EOS R6 Mark II.

My setup:

• Canon EOS R6 Mark II
• MacBook Pro M5 Max (128GB RAM)
• Tether Tools Pro USB cable
• RAW shooting
• Internal SSD with plenty of free space

During tethered shooting, Lightroom works normally at first, but after around 29 RAW photos, the camera shows "PC FULL" and stops shooting. This also happens with JPEG files.

I have tested the same camera and cable with Canon EOS Utility, and tethering works perfectly without any issues. I also tested the RAW files in Canon Digital Photo Professional 4, and everything works normally.

I increased Lightroom Camera Raw Cache to 50GB, checked my SSD storage, and confirmed that my computer has sufficient resources, but the issue still happens consistently.

Since the problem only occurs in Lightroom Classic, I believe it may be related to Lightroom's tethering process or buffer management. I have lastest version of Lightroom and camera firmware.

Could you please help me resolve this issue?

I’ve been getting the same error since upgrading LR to 15.4.1, R6, MacBook Pro, 

I downgraded to the previous LR & no problems, so its definitely the newest LR update.

Description of Issue Canon EOS R6 Mark III cannot be detected by Lightroom Classic for tethered capture. Using the same Mac, the same USB cables, and the same Lightroom installation, Canon EOS R3 and EOS R5 work perfectly. The EOS R6 Mark III has never worked with Lightroom Classic since it was purchased. Lightroom Classic Version 15.4.1 Camera Raw 18.4 Operating System macOS Sequoia 15.7.1 Computer Mac Studio (M1 Ultra) Additional verification was also performed on: MacBook Pro (M2) Lightroom Classic 15.2 Camera Raw 18.2 Symptoms When I select: File > Tethered Capture > Start Tethered Capture Lightroom displays: "No camera detected." At the same time, the EOS R6 Mark III repeatedly disconnects and reconnects, and the camera LCD continuously flashes as if the USB connection is being reset. Important observation Apple Image Capture recognizes the EOS R6 Mark III immediately and remains connected without disconnecting. Only Lightroom Classic causes the repeated USB reconnect behavior. Environment Camera: Canon EOS R6 Mark III Firmware 1.0.2 Comparison cameras: Canon EOS R3 Canon EOS R5 Both R3 and R5 work perfectly using the identical setup. USB cables tested: - Tether Tools USB-C 5m - Cable Matters USB-C 5Gbps 7.5m Both cables work perfectly with R3 and R5. Troubleshooting already completed - Canon SDK enabled - Canon SDK disabled - USB Application = Image Import / Remote Control - Wi-Fi disabled - Bluetooth disabled - EOS Utility not running - macOS recognizes the camera in Image Capture - Two different Macs tested - Multiple Lightroom Classic versions tested - Multiple USB cables tested Expected Result EOS R6 Mark III should be detected for tethered capture exactly like EOS R3 and EOS R5. Actual Result Only EOS R6 Mark III fails to connect. Lightroom repeatedly resets the USB connection and never detects the camera. Question Could Adobe Engineering please confirm whether this is a known compatibility issue with the EOS R6 Mark III? If additional logs or testing are required, I would be happy to provide them.

Because the same Mac, same USB cables, and same Lightroom installation work perfectly with EOS R3 and EOS R5, this issue appears to be specific to the EOS R6 Mark III.

Not sure if this will help anyone with the current update but when I was having tethering errors with previous LR Classic updates, I stumbled across a workaround that got me connected. Straight into File/Tethered Capture/ Start Tethered Capture would never connect but if I followed these steps, it would tether correctly.  

Camera connected and turned off (mine is a Canon R62)

File/ Import Photos and Video

Turn the camera on and observe the camera’s name pop in on the left side

Hit Cancel on the Import Screen

Then, select Tethered Capture/ Start Tethered Capture

I had a session today - first time with the new update - and I did all this from habit and it worked fine.  

Macbook Pro M4 with Sequoia 15.6, Canon R62

Hope it helps someone!

Hello Adobe Lightroom Support Team,

I am experiencing a tethering issue with Lightroom Classic and my Canon EOS R6 Mark II.

My setup:

• Canon EOS R6 Mark II
• MacBook Pro M5 Max (128GB RAM)
• Tether Tools Pro USB cable
• RAW shooting
• Internal SSD with plenty of free space

During tethered shooting, Lightroom works normally at first, but after 29 RAW photos, the camera shows "PC FULL" and stops shooting.

I have tested the same camera and cable with Canon EOS Utility, and tethering works perfectly without any issues. I also tested the RAW files in Canon Digital Photo Professional 4 and capture one as well, and everything works normally.

I increased Lightroom Camera Raw Cache to 50GB, I have 1.3tb ssd empty storage.

Since the problem only occurs in Lightroom Classic, I believe it may be related to Lightroom's tethering process or buffer management. I have lastest version of lightroom and camera firmware. 

Could you please help me resolve this issue?

Thank you.

 Updated Camera firmware and checked connections and cables. Reverting back to older version it works normally. I can take photos but image review is unavailable and autofocus will stop working while tethered. If I unplug camera functions normally. This update was forced mid workday and now my catalog upgraded so I can’t go back. Please help as this is setting me back on my work.

“Use Canon SDK for tethering Canon cameras” seemed to temperoarily fix the issue of the “PC Full” message popping up. But, now the the catalog just closes on it’s own when I’m shooting or disconects from my camera on it’s own.

Adobe y’all are such a mess. It’s actually ridiculous how bad your live tethering is.

Has these been a resolution to this? I have the same issue and all of my discussions with help have not resolved the issue.