darktable for Windows

Software darktable
,
78

The Windows 10 version seems to have the same bug like on my linux system.
When moving the mouse in the lighttable over the pictures the CPU goes like crazy…
Should I file a bug, especially for the windows 10 version? If not, here is the bug, which I opened a couple of month ago: https://redmine.darktable.org/issues/11572

79

Used it a couple of times on WIN10 and it works wonderful, no problems so far. What an incredible software!!!

80

Tested on Windows 8.1 pro and it works smoothly. But I wonder why it doesn’t use OpenCL. darktable-cltest gives the following results:

[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ‘’
[opencl_init] opencl_memory_requirement: 768
[opencl_init] opencl_memory_headroom: 300
[opencl_init] opencl_device_priority: ‘/!0,//’
[opencl_init] opencl_mandatory_timeout: 200
[opencl_init] opencl_size_roundup: 16
[opencl_init] opencl_async_pixelpipe: 0
[opencl_init] opencl_synch_cache: 0
[opencl_init] opencl_number_event_handles: 25
[opencl_init] opencl_micro_nap: 1000
[opencl_init] opencl_use_pinned_memory: 0
[opencl_init] opencl_use_cpu_devices: 0
[opencl_init] opencl_avoid_atomics: 0
[opencl_init]
[opencl_init] found opencl runtime library ‘OpenCL.dll’
[opencl_init] opencl library ‘OpenCL.dll’ found on your system and loaded
[opencl_init] found 1 platform
[opencl_init] found 2 devices
[opencl_init] device 0 Intel(R) HD Graphics 4400' supports image sizes of 16384 x 16384 [opencl_init] device 0 Intel(R) HD Graphics 4400’ allows GPU memory allocations
of up to 356MB
[opencl_init] device 0: Intel(R) HD Graphics 4400
GLOBAL_MEM_SIZE: 1426MB
MAX_WORK_GROUP_SIZE: 512
MAX_WORK_ITEM_DIMENSIONS: 3
MAX_WORK_ITEM_SIZES: [ 512 512 512 ]
DRIVER_VERSION: 10.18.14.4578
DEVICE_VERSION: OpenCL 1.2
[opencl_init] compiling program demosaic_ppg.cl' .. [opencl_fopen_stat] could not open file C:\Users*****\AppData\Local\Microsoft
\Windows\INetCache\darktable/cached_kernels_for_IntelRHDGraphics4400/demosaic_pp
g.cl.bin.a9fb114d983b3f1a3026021ee2f96f1d’!
[opencl_load_program] could not load cached binary program, trying to compile so
urce
[opencl_load_program] successfully loaded program from `C:\Program Files\darktab
le\share\darktable/kernels/demosaic_ppg.cl’
[opencl_build_program] could not build program: -43
[opencl_build_program] BUILD STATUS: -2
BUILD LOG:

[opencl_init] failed to compile program `demosaic_ppg.cl’!
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.

press any key to exit

81

Thats a bug which has been recently fixed:
Having a space in install folder name prevents OpenCL to work

Next build will contain the fix. In the meantime you can install it to a folder which has no space in the path.

1 Like
82

Could you please run from a command prompt:
darktable.exe -d camctl

and after closing darktable share the contents of the darktable-log file, which you can find:
C:\Users\[username]\AppData\Local\Microsoft\Windows\INetCache\darktable\darktable-log.txt

83

There have been some more fixes since the last snapshot, so today you shall have another one.

Changes (the more important ones, for full changelog always have a look at the git history on github!):

  • Offer to uninstall old darktable from within the installer – you should do that in general
  • Exiv2 with unicode support
  • Fix opencl when there are spaces in the install path
  • Handle non-ascii command line arguments more gracefully → fixes being used by GIMP
  • Updated lensfun db
  • Fix gphoto2 location setting
  • Add image to intermediate-export-image in Lua
  • Add darktable.configuration.running_os for Lua – this is subject to change

The installer: (please use link from 1st post instead)
The GPG signature: https://pixls.us/files/darktable-2.3.0%2B898~ge47c49cfc-win64.exe.asc
sha256sum: 59b3352b01386a65fc40d07f5438b4facb5f7a7e7765eb4884824a12d96e81da

3 Likes
84

[peterbud] peterbud http://discuss.pixls.us/u/peterbud
September 6

Gasman:

Hi again Peter

Running echo %CAMLIBS% gives -

D:\darktable\lib\libgphoto2\2.5.14

regards

Steve

Could you please run from a command prompt:

darktable.exe -d camctl|

and after closing darktable share the contents of the darktable-log
file, which you can find:

C:\Users[username]\AppData\Local\Microsoft\Windows\INetCache\darktable\darktable-log.txt|

Hi Peter
Please find attached darktable-log.txt
regards
Steve

darktable-log.txt (837 Bytes)

85

Note after sending you darktable-log.txt I forgot to say that the
camera was not connected did you want it connecting first before
running darktable.exe -d camctl ?.
Steve

86

Hi Steve, yes, pls.

Connect your camera, make sure its using WinUSB driver (you can use Zadig for that one) and launch darktable. Then try to scan for devices and when you finished, close darktable, and send the log file.

87

Sorry Peter no probs, attached now :wink:

best

Steve

also printed darktable-log.txt below .

darktable-log.txt (1.52 KB)

88

The new version works fine and opencl is activated on my AMD RX470 :grinning:

1 Like
89

New Version works for me. So far no issues, which were not mentioned. I guess I won’t need linux in future anymore. Only used Linux for dt.

90

Okay, now I’ve run into a problem. Albeit not a buggy problem. My brand new Nikon D7500 works currently with Windows dt. So I wanted to try out this tutorial profiling sensor and photon noise | darktable in order to noise profile my cam. But I can’t find the directory containing the folder tools. Does this currently only work on Linux?

Edit: I figured out now, that the ~darktable/tools/noise folder is on git. But I still got no clue how to make it work on Win 10.

91

You need a compiler to build the tool first. Which is something Windows doesn’t typically has. It also requires a shell environment like MSYS2 to run, so I’d say sensor profiling is not going to work easily on Windows.

92

Hmm, I am totally clueless when it comes to compiling anything as complicated as dt.
Is there any way I can replace the necessary files such as rawspeed on Linux Mint in order to profile my cam? Afaik it’s just the old rawspeed blocking me from doing it on linux (at least that is the complaint I receive on Linux)

93

Hm, if you have Linux available, compiling there is easy with the instructions from here: install | darktable (git install section) and here: https://redmine.darktable.org/projects/darktable/wiki/Building_darktable_22 on many linux distros. And if you have questions, we are still here (k, need some hours of sleep now, but tomorrow …).

94

Thanks for the hint Chris, I’ll take a closer look when I am home. How do I identify the correct version which supports my camera’s colour matrix? Is it sufficient if I only compile raw speed or do I need to compile the entire package?

95

You need to compile the whole package from git master.

96

CMakeError.txt (4.1 KB)
It almost worked, but there were some kind of issues. I also noticed that there was an error while installing lensfun-dev, claiming that it depends on lensfun0 which apparently is causing some issues, however, the terminal output was gibberish.

97

Which version of dt do you build? And with which compiler version? There has been a similar error reported and fixed, see https://redmine.darktable.org/issues/11199.