Project

General

Profile

Bug #11744

Nikon camera not recognized

Added by Michel PETTE about 1 year ago. Updated 10 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
General
Target version:
Start date:
09/19/2017
Due date:
% Done:

0%

Affected Version:
git master branch
System:
Windows
bitness:
64-bit
hardware architecture:
amd64/x86

Description

My two cameras (D750 and D500) are not recognized to import pictures from them. I don't know if it is a bug, but I notice that in the directory lib/libgphoto2/2.5.14 nothing concerning a nikon.dll. Is it normal?

org_gtk_gdbus_general (78 Bytes) Michel PETTE, 09/21/2017 10:54 AM

Transfer.ldb (128 Bytes) Michel PETTE, 09/21/2017 10:56 AM

Transfer.mdb (1.2 MB) Michel PETTE, 09/21/2017 10:57 AM

darktablerc (19.8 KB) Michel PETTE, 09/21/2017 10:59 AM

data.db (124 KB) Michel PETTE, 09/21/2017 10:59 AM

keyboardrc (88.1 KB) Michel PETTE, 09/21/2017 10:59 AM

keyboardrc_default (85.9 KB) Michel PETTE, 09/21/2017 10:59 AM

library.db (928 KB) Michel PETTE, 09/21/2017 11:00 AM

settings (62 Bytes) Michel PETTE, 09/21/2017 04:40 PM

summary.txt Magnifier (18.6 KB) Michel PETTE, 09/22/2017 06:43 PM

History

#1 Updated by Tobias Ellinghaus about 1 year ago

Importing directly from camera is the same as tethering: most likely not working out of the box on Windows.

#2 Updated by Peter Budai about 1 year ago

Nikon cameras are handled by the ptp2.dll in darktable\lib\libgphoto2\2.5.14 folder.
I'm thinking about a way to have a debug on the camera recognition process on your machine. Let me give a try soon with a short protocol that cold help us to get a more meaningful debug info on your camera recognition problem.

#3 Updated by Michel PETTE about 1 year ago

HI,
In directory: C:\Users\Michel\.dbus-keyrings, I have this attached file (first file)
In a second Directory: C:\Users\Michel\AppData\Roaming\Nikon\Nikon Transfer 2\Database, I have two other files (second and third files)
In DT App directory: C:\Users\Michel\AppData\Local\darktable: other files

#4 Updated by Peter Budai about 1 year ago

Ok Michel, I hope it won't be too technical.

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:
http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-gphoto2-2.5.14-1-any.pkg.tar.xz
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:
http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-popt-1.16-1-any.pkg.tar.xz
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:
http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-readline-7.0.003-1-any.pkg.tar.xz
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:
http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-termcap-1.3.1-2-any.pkg.tar.xz
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
14. Run gphoto2.exe --summary --debug > C:\users\[your username]\Documents\summary.txt 2>&1
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)

#5 Updated by Michel PETTE about 1 year ago

Hi Peter,
I do the differents steps of the tuto, the summary file is created BUT it is empty as you can see in attachment.
in this directory: C:\Users\Michel\.gphoto I have a setting file. I join it

#6 Updated by Peter Budai about 1 year ago

Hi Michel, have you added the "2>&1" at the end of the command to redirect the output to the file?
The complete command should be this:

gphoto2.exe --summary --debug > C:\users\[your username]\Documents\summary.txt 2>&1

Also first you can try without redirection, and then just copy-paste what is written to the console with this command:

gphoto2.exe --summary --debug

#7 Updated by Michel PETTE about 1 year ago

Hi Peter, Sorry today i was very busy....
I did a mistake, I don't put the *@* before and behind the command.
Now the summary file is OK

#8 Updated by Peter Budai about 1 year ago

Michel, 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.

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:
http://zadig.akeo.ie/7
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.

#9 Updated by Michel PETTE about 1 year ago

HiPeter,
Michel, have you replaced the default mass storage driver with a WinUSB driver for your Nikon? Yes i thought, because i use to download from camera a nikon software "Nikon Transfer 2". If i transfer from camera with Nikon Transfer 2, I can automatically open lighttable, but DT don't recognize my camera. Note if i desactive the mobile driver, Nikon transfer 2 does not work.
When you run it, replace current Windows camera driver with WinUSB driver. It's OK, DT recognize my camera AND Nikon Transfer 2 continues to recognize in the same time.
It is not a bug for me, but i am not sure that all the people accept changing the drivers (Windows, Nikon etc...) to use "Capture" on Daktable. DT have to use the installed drivers

#10 Updated by Peter Budai 12 months ago

Should we close this issue?

#11 Updated by Michel PETTE 12 months ago

Hi Peter,
Yes we can, but i think for a new stable version of DT, include the DT necessaries drivers in the install process. It's just an idea....because nobody will use "Import from camera" or "Capture"

#12 Updated by Michel PETTE 11 months ago

Hi Peter,
For information, after the last new Windows 10 version 1709 release, the Zadig drivers are un-installed, and DT don't recognized any more my cameras. For the future it is a problem, twice a year, the windows users have to re-install the compatible drivers to continue used "Import from camera" or "Capture"

#13 Updated by Ċ½ilvinas Ċ½altiena 11 months ago

Michel PETTE wrote:

Hi Peter,
For information, after the last new Windows 10 version 1709 release, the Zadig drivers are un-installed, and DT don't recognized any more my cameras. For the future it is a problem, twice a year, the windows users have to re-install the compatible drivers to continue used "Import from camera" or "Capture"

Windows 10 build updates are not really updates, but in-place upgrades (whole OS is reinstalled trying to retain previously installed software and user settings), something like in-place upgrading Windows XP -> Windows Vista, just not that drastic feature wise, however similar issues are to be expected: invalidated licences of some software, broken driver installations or even complete removal of non WHQL drivers.

#14 Updated by Michel PETTE 11 months ago

Hi Zilvinas,
libghoto2 and darktable don't used non WHQL drivers.....for the moment. Build after build the free liscense software like Rawtherapee, Gimp or Nikon free software continue to work with the natives windows softwares without re-install. Darktable must be INTEGRATED in Windows world and not just work in Windows, it's just my opinion.

#15 Updated by Roman Lebedev 10 months ago

  • Target version changed from 2.4.0 to 2.6.0

Also available in: Atom PDF