Copy link to clipboard
Copied
Tethered capture used to work. I'd start tethered capture, restart in Rosetta mode, start it again, and then photograph away. Now, the "Detecting Camera" dialog box just sits there spinning away.
This worked on the previous version of LR Classic.
Thanks
Camera: Nikon Z6. Firmware 3.50 (also did not work on 3.40).
System:
Lightroom Classic version: 12.1 [ 202212072312-d7ab524b ]
License: Creative Cloud
Language setting: en-AU
Operating system: Mac OS 13
Version: 13.1.0 [22C65]
Application architecture: x64 (emulated)
Logical processor count: 10
Processor speed: 2.4GHz
SqLite Version: 3.36.0
Built-in memory: 65,536.0 MB
Real memory available to Lightroom: 65,536.0 MB
Real memory used by Lightroom: 2,681.2 MB (4.0%)
Virtual memory used by Lightroom: 46,593.8 MB
Memory cache size: 145.9MB
Internal Camera Raw version: 15.1 [ 1329 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 1MB / 32767MB (0%)
Camera Raw real memory: 3MB / 65536MB (0%)
Standard Preview Size: 2880 pixels
Displays: 1) 2560x1440, 2) 3600x2338
Graphics Processor Info:
Metal: Apple M1 Max
Init State: GPU for Export supported by default
User Preference: Auto
Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/geoffbartlett/Pictures/_00 LR Working/00 LR Working-v12.lrcat
Settings Folder: /Users/geoffbartlett/Library/Application Support/Adobe/Lightroom
Installed Plugins:
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Flickr
4) jb: Search + Replace
5) Nikon Tether Plugin [v 12.1.0.202212072312]
Config.lua flags: None
Once pointed in the direction of the issue being Ventura, this is a known issue - ignore this post.
Copy link to clipboard
Copied
I have just found this post (under a different search): https://community.adobe.com/t5/lightroom-classic-discussions/tethering-nikon-under-ventura-quick-dir...
It might be a MacOS that contributed to breaking Tethering.
Copy link to clipboard
Copied
Once pointed in the direction of the issue being Ventura, this is a known issue - ignore this post.