* darkta...@911networks.com <darkta...@911networks.com> [09-25-15 17:45]: > On Fri, 25 Sep 2015 22:55:39 +0200 > KOVÁCS István <k...@kovacs-telekes.org> wrote: > > >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. > > > >But this way you won't have access to presets (as they are in the > >library DB). > > Thanks. > > --library :memory: seems to be the way forward in my case. > > but... > > The presets are gone but the settings like the various collections, > export paths... are still there.
No, it is not. Use your current library.db, backup if desired. Work the images, export them, and using *copies* return them to their owners, the raws, xmps and which-ever output format used. Then use dt to remove the images from your library.db. Or, instead of the remove process, replace your library.db with the backup copy and merely remove subject images from your system. Dt will never know they were there. Personally, I would work and export the images returning copies to rightful owners and remove images from dt using dt's process. Using :memory for library cripples you from using your presets, ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net ------------------------------------------------------------------------------ _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
