Darktable + Wacom: on & off

darktable
#5

Is that a USB Wacom?
If so, I would check Window’s device manager for any odd warnings.
Does the Wacom FAQ give any assistance?
You are running Wacom’s latest driver(s)?

Have fun!
Claes in Lund, Sweden

0 Likes

#6

Hi Claes,

Yes, it’s a USB wacom.
No warning of any type in the device manager, all the peripherals are running fine. I’m using the latest drivers.
At this point I think I have to give up on using the wacom with DT. Too bad, especially when it comes to fine-tune the curve

0 Likes

#7

Does this happen with the mouse plugged in only? Sometimes the USB bus power messes up. Could be for a fraction of a second and an app might lose track of the device. Only a guess…

0 Likes

(Mica) #8

I’ve seen the system get confused about which mouse is what and disable both. Perhaps that is still an issue.

Either way, start darktable from the command line in verbose debug mode and post the output.

0 Likes

#9

Hi paperdigits,

Is this the command I’m supposed to use?

darktable.exe [–verbose]

Or should I use darktable-cli.exe?
In which case I’m not sure how to complete the command…

0 Likes

(Hevii Guy) #10

Usually, it’s a Command Line variant of:

darktable -d

It’s OS-dependant. For example, on my MacBox, I must enter:

/Applications/darktable.app/Contents/MacOS/darktable -d

I’m not so sure about your Wyndowze machine :frowning: Nevertheless, give it a shot and enter the above (the first) into your terminal. If it doesn’t work, I’m certain that Mica can lead you in the right direction shortly after the sun comes up over there.

0 Likes

#11

Thank you, Hevii_Guy,

darktable.exe -d didn’t work.

0 Likes

(Mica) #12

You need to use the full path to darktable.exe, something like 'C:\Program Files\darktable\darktable.exe -d'

0 Likes

#13

Hi paperdigits,

I’m executing the command from within the folder.
I tried with the full path, though, just to make sure with the same result.

0 Likes

(Mica) #14

There is no output at all? What about the logs: https://www.darktable.org/about/faq/#faq-windows-logs

0 Likes

#15

This is how the log looks like:

========================================
version: darktable 2.4.4
start: 2018:09:07 09:53:04

> usage: darktable.exe [options] [IMG_1234.{RAW,..}|image_folder/]
> 
> options:
> 
>   --cachedir <user cache directory>
>   --conf <key>=<value>
>   --configdir <user config directory>
>   -d {all,cache,camctl,camsupport,control,dev,fswatch,input,lighttable,
>       lua, masks,memory,nan,opencl,perf,pwstorage,print,sql}
>   --datadir <data directory>
>   --disable-opencl
>   -h, --help, /?
>   --library <library file>
>   --localedir <locale directory>
>   --luacmd <lua command>
>   --moduledir <module directory>
>   --noiseprofiles <noiseprofiles json file>
>   -t <num openmp threads>
>   --tmpdir <tmp directory>
>   --version
> 
>   note: debug log and output will be written to this file:
>         C:\Users\andrayverysame\AppData\Local\Microsoft\Windows\INetCache\darktable\darktable-log.txt
0 Likes

(Mica) #16

How about the logs?

0 Likes

#17

Not sure to understand… what logs?
The only things in the log folder are these:

[folder] cached_kernels_for_GeForceGTX1080Ti
[folder] mipmaps-16ef8e3ef5c19bd5a4106477a57df487e8647ede.d
darktable-log.txt

0 Likes

(Mica) #18

Those logs, I think.

0 Likes

#19

that’s the one I posted above:

0 Likes

(Mica) #20

That’s the debug log?

0 Likes

#21

yup

0 Likes

(Mica) #22

not sure where to go from here… sorry :frowning:

0 Likes

#23

Np, thanks for trying! :slight_smile:

0 Likes

(David Sauer) #24

I had the same or similar problem with (older) Bamboo Fun tablet.
I was using latest Wacom driver with official support for Window 10, but without official support of Bamboo Fun.
When I downgraded to driver for Windows 8 (I’m actually using Window10) that supports Bamboo Fun, it started working normally.
Maybe this helps.

0 Likes