DT 5.0.1, the nvidia saga

Software darktable
21

You don’t need to re-import, replacing darktablerc does not wipe the database.

Could you share your broken darktablerc so we could investigate, find the reason and maybe a fix?

22

you need to check also the cldevice_v5_* settings in darktablerc - especially parameter h according to

https://darktable-org.github.io/dtdocs/en/special-topics/mem-performance/#device-specific-opencl-configuration

23
  • Navigate to your new config directory with working darktablerc
  • From the command line run
    grep -e cldevice -e clplatform -e opencl darktablerc
  • Take the output lines of this command to replace the corresponding lines in your damaged darktablerc one by one
  • Remove any superfluous lines containing cldevice, clplatform or opencl from your old (damaged) darktablerc

Once again, note that darktable must not be running while you are making changes to darktablerc !

24

I already tried once to fix darktablerc and it didn’t work.

So I went the quick way aka the sledge hammer.

I deleted the ~/.config/darktable directory. DT recreated the darktablerc and it worked.

I just had reimported the images and it took me another 10mn to recreate my presets (they were already in my re-imported images).

Thanks

25

The trouble with that approach is that, even though you solved your problem, we learnt nothing of the root cause, won’t be able to help anyone who has the same problem, and, in case there is a bug lurking in the code, now we are unable to find and fix it, as we cannot reproduce the problem.

2 Likes
26

Which may very well be the original poster after a future update or system change…

27

I did :frowning:

This most likely had something to do with a setting in the DBs. This is why I use the XMPs, so I can start from fresh, just in case…

BTW, Soon I will not be using the lighttable anymore. I have been using DigiKam as the dam and will be switching next month to darktable --library :memory: when I get my much bigger and faster drive.

Thanks

28

The DBs and the sidecars have nothing to do with OpenCL.

2 Likes
29

Do you still have the damaged darktablerc available? Could you share it ? Together with the now working darktablerc ? It would be really useful to be able to determine the real cause of the problem. You may be satisfied, but the benefit for others is unfortunately close to zero.
And as @kofa already mentioned : the database and the sidecar files have absolutely no influence on the activation of OpenCL nor the re-import you did. All you had to do was copy library.db and data.db …

30

It could be the specific device was disabled in the per-device settings.

31

Thanks