No tethering with Nikon D5500 on Windows 10
My Nikon D5500 is not detected with the Windows 10 version of Darktable, works fine under Linux (Ubuntu)just get the message "no camera with tethering support available for use"
#2 Updated by Peter Budai almost 2 years ago
This should be added to our release notes on Windows:
For thethering to work (in general for libgphoto and libusb to work):
Use this program to install USB driver on Windows for your camera:
follow the description (https://github.com/pbatard/libwdi/wiki/Zadig).
When you run it, replace current Windows camera driver with WinUSB driver.
Start dt after replacing the driver.
With that my Nikon D5000 was working nicely.
#3 Updated by Peter Budai almost 2 years ago
Hi Steve, as I saw that has not helped.
Could you please run:
darktable.exe -d camctl
and after closing share the contents of the darktable-log file, which you can find:
Als give a try changing the following environment variable:
from: C:\Program Files\darktable\lib\libgphoto2\2.5.12
to: C:\Program Files\darktable\lib\libgphoto2\2.5.14
You can do that by:
select Control Panel/System/Edit the system environment variables
and then Environment Variables/System Variables
restart, and launch darktable again.
#4 Updated by Peter Budai almost 2 years ago
Apologies, the environment variabel name is CAMLIBS - that’s what libgphoto is using
if you open a cmd prompt what is the result of:
The existing installer had a wrong path - this will be fixed in next release. Also please note if you change an environment variable on the Windows Control Panel UI the changes do not take effect until you log off and then log back on. You can always test whether the env change has propagated by launching cmd and type echo CAMLIBS
#5 Updated by Peter Budai almost 2 years ago
I'm adding here the log I got from Steve:
version: darktable 2.3.0+866~gc23bd4a5a
start: 2017:09:06 18:00:40
[camera_control] creating new context 000000000db09920
[camera_control] loaded 2426 camera drivers.
[camera_control] loaded 6 port drivers.
[camera_control] 1 cameras connected
[camera_control] failed to initialize camera Nikon DSC D5500 on port usb:002,006
[camera_control] failed to initialize device Nikon DSC D5500 on port usb:002,006, probably causes are: locked by another application, no access to udev etc.
[camera_control] registering listener 000000000d927c40
So first it seems that the camera has been properly recognized as Nikon D5500, but then failed to initialize.
#6 Updated by Peter Budai over 1 year ago
Here is a short description, how we could collect more debug info. Basically we would need a detailed log from the camera recognition, and therefore I suggest to manually install gphoto2 front-end as follows.
1. Download gphoto from here:
2. Open with 7-zip
3. From the folder in the archive "mingw64/bin" copy gphoto2.exe to the C:\Program Files\darktable\bin folder
4. Download popt from here:
5. Open with 7-Zip
6. From the folder in the archive "mingw64/bin" copy libpopt-0.dll to the C:\Program Files\darktable\bin folder
7. Download readline7 from here:
8. Open with 7-Zip
9. From the folder in the archive "mingw64/bin" copy libreadline7.dll to the C:\Program Files\darktable\bin folder
10. Download termcap from here:
11. From the folder in the archive "mingw64/bin" copy libtermcap-0.dll to the C:\Program Files\darktable\bin folder
12. Open a cmd prompt
13. Go to the C:\Program Files\darktable\bin folder and
gphoto2.exe --summary --debug > C:\users\[your username]\Documents\summary.txt 2>&1
Please note the redirection at the end of the command which pipes the log to a file
15. Post here the summary.txt file from your Documents folder which supposed to contain the whole detailed log. In my case it begins like:
0.000500 main (2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.001000 main (2): gphoto2 2.5.14
0.001499 main (2): gphoto2 has been compiled with the following options:
0.001999 main (2): + x86_64-w64-mingw32-gcc (C compiler used)
0.002499 main (2): + popt (mandatory, for handling command-line parameters)
0.002999 main (2): + exif (for displaying EXIF information)
0.003499 main (2): + no cdk (for accessing configuration options)
#9 Updated by Peter Budai over 1 year ago
Hi Steve, the account you have used when you logged in: is it part of the local Administrators group, or just a "plain" user?
Can you try running darktable as Administrator: rigth click on the darktable icon in the Start Menu, then "More" then select "Run as administrator"?
#10 Updated by Steve Cuthbert over 1 year ago
I ran Darktable just as a plain user would you like a new summary.txt redone as an Admin?. I did notice in that summary.txt file I sent there was no mention of any Nikon libraries, is that too obvious a reason why my Nikon won`t connect?.
#12 Updated by Steve Cuthbert over 1 year ago
Darktable running fine as Admin but still my Nikon not connected! In case you were wondering my C: partition is rapidly filling up so all my apps are installed (if they allow it) on my D: partition so the Darktable exe is currently installed at D:\darktable\bin.
#13 Updated by Peter Budai over 1 year ago
Nikon cameras are handled by the ptp2.dll, so its ok not to see a driver named like Nikon.
The second attached txt file seem to me broken (see line endings), can you verify pls?
Also, Steve, have you replaced the default mass storage driver with a WinUSB driver for your Nikon? Windows by default installs a mass storage driver, which is not working with libghoto2 and darktable. So if you have not done that before, pls follow this:
For tethering to work (in general for libgphoto and libusb to work):
Use this program to install libusb compatible driver on Windows for your camera:
Follow the description here: https://github.com/pbatard/libwdi/wiki/Zadig6,
When you run it, replace current Windows camera driver with WinUSB driver.
Start darktable after replacing the driver.
#14 Updated by Steve Cuthbert over 1 year ago
I haven't changed any usb drivers just using the one's installed by default with Windows 10.The only problem that I might have in changing it is that I use my Nikon to take astronomical images using a couple of Tethering apps one called 'Backyard Nikon' and another called 'ControlmyNikon' both working fine ATM will they be affected changing the driver?.
#15 Updated by Michel PETTE over 1 year ago
Hi Steve and Peter,
As the bug #11744, I changed the installed drivers by the Zadig drivers, my two cameras are now recognized by Darktable, and the Nikon software "Nikon Transfer 2" continues to work fine. Probably for your two tethering apps it will be the same. But the better way is that Darktable uses the installed drivers
#18 Updated by Steve Cuthbert over 1 year ago
Ah! right sounds a little involved think it's maybe best to hang fire for me for now with the Darktable tethering 😙. I also have other cooled astro CCD's connected by usb don't want to lose those 😊. Happy to carry on using Darktable for the processing for now.
#19 Updated by Peter Budai over 1 year ago
- libgphoto2 uses libusb as a standardized way to communicate with the cameras.
- That requires a driver which implements libusb
- Backyard Nikon and other softwares (like Nikon's ViewNX) are using proprietary ways to talk to the camera, and they don't provide libusb interface, hence they cannot use for libgphoto2 and darktable alone
- If you want to use darktable with your camera tethering, you need to install a driver which has this libusb interface.
- On Windows this driver called WinUSB - please note that this is actually a driver which is from Microsoft
- The above mentioned software (http://zadig.akeo.ie/) just makes it easy to install this driver for any USB device
- Also please note that it is actually very easy to revert back to the original driver if you want
With that I believe we can close this issue.