It does this by writing the current process identifier (PID) into a lock file. Whenever darktable starts, it will lock the library to the current user. You may also provide :memory: as the library file, in which case the database is kept in system memory – all changes are discarded when darktable terminates. If the database file does not exist, darktable creates it for you.

if you want to do some experiments without compromising your original library.db). Use this option to provide an alternative location (e.g. The default location of that database file is file name library.db in the directory specified by -configdir or defaulted to $HOME/.config/darktable/. library darktable keeps image information in an sqlite database for fast access. The default location is $HOME/.config/darktable/. configdir Define the directory where darktable stores user-specific configuration.

Use this option if darktable crashes at startup due to a defective OpenCL implementation. disable-opencl Prevent darktable from initializing the OpenCL subsystem. version Print the darktable version number, a copyright notice, some other useful information, and then terminate. If a folder is given darktable starts in lighttable view with the content of that folder as the current collection. If a filename is given darktable starts in darkroom view with that file opened. | Optionally supply the name of an image file or folder. This option allows only two cachelines per pipe, and should be used for debugging purposes only. disable-pipecache Disable the pixelpipe cache. d-signal-act If -d signal or -d all is specified, specify the signal action to debug using this option. Specify ALL to debug all signals or specify signal using it’s full name. d-signal If -d signal or -d all is specified, specify the signal to debug using this option. The verbose option must be explicitly provided, even when using -d all. Some debug options (like -d opencl) can also provide more verbose output, which can be invoked with the additional option -d verbose. darktable -d opencl -d camctl) or debug all of them at once (with -d all). You can use this option multiple times if you want to debug more than one subsystem (e.g. There are several subsystems of darktable and each of them can be debugged separately. This is the standard way to use darktable.ĭarktable can called with the following command line parameters: darktable [-d Enable debug output to the terminal. The darktable binary starts darktable with its GUI and full functionality.

Darktable 4.4.0 for windows instal