tethering does not work after updating from 4.6.0 to 4.6.1
Describe the bug
tethering has been working fine with my Nikon D850 and my Nikon D810 when using 4.6.0. After updating to 4.6.1 the tethering option does not show up, after switching the camera on.
all steps mentioned in the trouble-shooting guide have been executed successfully (see attached log):
- the camera is identified correctly
- gphoto2 is able to trigger the camera
- gphoto2 receives the image from the camera when using the trigger button of the camera
Steps to reproduce
- start darktable
- connect camera using usb cable
- switch on camera
Expected behavior
darktable should offer to start tethering
Logfile | Screenshot | Screencast
Commit
No response
Where did you obtain darktable from?
downloaded from www.darktable.org
darktable version
4.6.1
What OS are you using?
Mac
What is the version of your OS?
Sonoma 14.3.1 (23D60)
Describe your system?
No response
Are you using OpenCL GPU in darktable?
None
If yes, what is the GPU card and driver?
No response
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
in your description to reproduce an essential step is missing: connecting the cam for tethering in darktable: Are you sure you followed the description in https://docs.darktable.org/usermanual/4.6/en/tethering/overview/ (especially 3rd paragraph)?
Hello @MStraeten
yes, I did exactly that: the issue is: in the import section there is no button coming up when the camera is connected (and switched on). This was the case before I upgraded to 4.6.1
This is strange as nothing has changed in this area since 4.6.0. Are you sure 4.6.1 has been built with gphoto2 and so tethering mode enabled?
What is displayed for:
$ darktable --version
/Applications/darktable.app/Contents/MacOS % clear && ./darktable --version
this is darktable 4.6.1
Copyright (C) 2012-2024 Johannes Hanika and other contributors.
Compile options:
Bit depth -> 64 bit
Debug -> DISABLED
SSE2 optimizations -> ENABLED
OpenMP -> ENABLED
OpenCL -> ENABLED
Lua -> ENABLED - API version 9.2.0
Colord -> DISABLED
gPhoto2 -> ENABLED
GMIC -> DISABLED - Compressed LUTs are NOT supported
GraphicsMagick -> DISABLED
ImageMagick -> ENABLED
libavif -> ENABLED
libheif -> ENABLED
libjxl -> ENABLED
OpenJPEG -> ENABLED
OpenEXR -> ENABLED
WebP -> ENABLED
See https://www.darktable.org/resources/ for detailed documentation.
See https://github.com/darktable-org/darktable/issues/new/choose to report bugs.
Lua support enabled
/Applications/darktable.app/Contents/MacOS %
This is strange as nothing has changed in this area since 4.6.0.
There are now two different builds?
I see, it is macOS... I have zero experience with this. I'll let macOS expert answer, sorry for the noise.
@ms-photo this is the homebrew based build of darktable. Can you please download and try the other arm64 package and report here.
We need to investigate if there is an issue with gphoto on homebrew based builds.
i tried it with my 4.6.1 build (the 12.5 arm64 build based on macports) and was able to connect my canon cam for tethering
Ok thanks! So let's again dive into homebrew stuff...
Strange, works for me too with my Canon, homebrew build.
@ms-photo this is the homebrew based build of darktable. Can you please download and try the other arm64 package and report here.
We need to investigate if there is an issue with gphoto on homebrew based builds.
I downloaded the x86_64 built and installed it (without homebrew) and it's working there. So the issue seems to be related to the homebrew built.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
still not fixed
Given the comments that's not a dt issue but probably some library to connect to the camera missing. Anyway no need to keep this open.