Am Dienstag, 7. August 2018, 21:56:41 CEST schrieb Robert Krawitz: > On Tue, 7 Aug 2018 12:51:30 -0700, I. Ivanov wrote: > >> I'd be perfectly happy to get rid of the database and use sidecar > >> files exclusively at least as an option. I prefer a different tool > >> for managing my image collection (KPhotoAlbum) and just use dt for > >> image processing. > > > > Maybe if you use ":memory:" as a library it would work for you. > > > > man darktable > > --library <library file> > > > > darktable keeps image information in an sqlite database for > > fast > > access. The default location of that database file is > > "$HOME/.config/darktable/library.db". You may give an > > alternative location, e.g. if you want to do some experiments without > > compromising your original library.db. If the database file does not > > exist, darktable creates it for you. You may also give ":memory:" as a > > library file in which case the database is kept in system memory - all > > changes are discarded when darktable terminates. > > This is useful. > > > I cannot advice on how to tie it with KPhotoAlbum ... but you can > > import an image, process it and then remove it. (the Darktable DB > > works well for me - in majority of cases) > > What I'd like isn't specific to KPhotoAlbum. I'd simply like to be > able to invoke > > darktable image1 image2... > > without regard for directory structure.
You can just click on the reset button of the collect module after the images got imported to see them all. If used together with :memory: as the database you won't have images from previous sessions either. Tobias
signature.asc
Description: This is a digitally signed message part.
