> > So why do I use darktable? Because it also has a dark(room) :-) side,
> > which I like a lot.
>
> Then you can solve your "skull" problem by setting
> --library :memory:
Note that this has an important side effect; you'll lose all presets
and styles, because they're also stored in the library.
My current solution for using darktable purely for RAW development with
no asset management is to scrub images and references to them from the
database in a script before I start darktable:
#!/bin/sh
DBFILE=$HOME/.config/darktable/library.db
if [ -f $DBFILE ]; then
sqlite3 $DBFILE 'delete from images;'
sqlite3 $DBFILE 'delete from film_rolls;'
sqlite3 $DBFILE 'delete from history;'
sqlite3 $DBFILE 'delete from selected_images;'
sqlite3 $DBFILE 'delete from tagged_images;'
sqlite3 $DBFILE 'delete from color_labels;'
sqlite3 $DBFILE 'delete from mask;'
fi
exec darktable $@
(I use it as 'darkt /some/directory', where /some/directory has all
of the RAWs I want to process this time.)
This is crude but it lets me have and maintain styles and presets, which
I very much want.
- cks
------------------------------------------------------------------------------
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
