This is what I got for the second one
darktable 4.6.1
Copyright (C) 2012-2024 Johannes Hanika and other contributors.
https://www.darktable.org
darktable is an open source photography workflow application and
non-destructive raw developer for photographers.
GNU GPL version 3 or later https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Usage:
darktable [OPTIONS] [IMAGE_FILE | IMAGE_FOLDER]
Options:
–cachedir DIR
darktable keeps a cache of image thumbnails for fast image preview
and precompiled OpenCL binaries for fast startup. By default the
cache is located in $HOME/.cache/darktable/. Multiple thumbnail
caches may exist in parallel, one for each library file.
–conf KEY=VALUE
Temporarily overwrite individual settings on the command line with
this option - these settings will not be stored in darktablerc
on exit.
–configdir DIR
Where darktable stores user-specific configuration.
The default location is $HOME/.config/darktable/
–datadir DIR
Define the directory where darktable finds its runtime data.
The default location depends on your installation.
Typical locations are /opt/darktable/share/darktable/
and /usr/share/darktable/
–library FILE
Specifies an alternate location for darktable’s image information database,
which is stored in an SQLite file by default (library.db) in the directory
specified by --configdir or $HOME/.config/darktable/. You can use this
option for experimentation without affecting your original library.db.
If the specified database file doesn’t exist, darktable will create it.
When darktable starts, it locks the library to the current user by writing
the process identifier (PID) to a lock file named FILE.lock next to the
specified library. If a lock file already exists, darktable will exit.
:memory: -> Use this option as FILE to keep the database in system memory,
discarding changes on darktable termination.
–localedir DIR
Define where darktable can find its language-specific text
strings. The default location depends on your installation.
Typical locations are /opt/darktable/share/locale/
and /usr/share/locale/
–luacmd COMMAND
A string containing lua commands to execute after lua
initialization. These commands will be run after your “luarc”
file. If lua is not compiled-in, this option will be accepted
but won’t do anything.
–moduledir DIR
darktable has a modular structure and organizes its modules as
shared libraries for loading at runtime.
This option tells darktable where to look for its shared libraries.
The default location depends on your installation.
Typical locations are /opt/darktable/lib64/darktable/
and /usr/lib64/darktable/
–noiseprofiles FILE
Provide a json file that contains camera-specific noise profiles.
The default location depends on your installation.
Typical locations are /opt/darktable/share/darktable/noiseprofile.json
and /usr/share/darktable/noiseprofile.json
-t, --threads NUM
Limit number of openmp threads to use in openmp parallel sections
–tmpdir DIR
Define where darktable should store its temporary files.
If this option is not supplied darktable uses the system default.
-v, --version
Print darktable version number
-h, --help
Show this help text
Debugging:
–bench-module MODULE_A,MODULE_B
–disable-opencl
Prevent darktable from initializing the OpenCL subsystem.
–disable-pipecache
Disable the pixelpipe cache. This option allows only
two cachelines per pipe, and should be used for debugging
purposes only.
–dump-pfm MODULE_A,MODULE_B
–dump-pipe MODULE_A,MODULE_B
–dumpdir DIR
-d SIGNAL
Enable debug output to the terminal. Valid signals are:
act_on, cache, camctl, camsupport, control, dev, expose,
imageio, input, ioporder, lighttable, lua, masks, memory,
nan, opencl, params, perf, pipe, print, pwstorage, signal,
sql, tiling, undo
all -> to debug all signals
common -> to debug dev, imageio, masks, opencl, params, pipe
verbose -> when combined with debug options like '-d opencl'
provides more detailed output. To activate verbosity,
use the additional option '-d verbose'
even when using '-d all'.
There are several subsystems of darktable and each of them can be
debugged separately. You can use this option multiple times if you
want to debug more than one subsystem.
E.g. darktable -d opencl -d camctl -d perf
–d-signal SIGNAL
if -d signal or -d all is specified, specify the signal to debug
using this option. Specify ALL to debug all signals or specify
signal using it’s full name. Can be used multiple times.
–d-signal-act SIGNAL_ACT
Valid SIGNAL_ACT are:
all, raise, connect, disconnect, print-trace
If -d signal or -d all is specified, specify the signal action
to debug using this option.
See resources | darktable for more detailed documentation.
See Sign in to GitHub · GitHub to report bugs.