> > Anyway.... yes DarkTable is slightly slow in the process of displaying and > "browsing" files AFTER importing the entire my archive. > So I guess I will try to import only small pieces as needed. >
You may need to check the size of your thumbnail cache ( https://docs.darktable.org/usermanual/3.6/preferences-settings/cpu-gpu-memory/), make sure that the disk backend is enabled, and eventually generate the cache offline ( https://docs.darktable.org/usermanual/3.6/special-topics/program-invocation/darktable-generate-cache/ ) I also read among your replies that I was advised by Guillermo to "ignore" > the DB generation, did I understand correctly? > I don't understand how it works and how to do it. > Read the --library option in the manual ( https://docs.darktable.org/usermanual/3.6/special-topics/program-invocation/darktable/). This allows you both to use a separate database for certain images (for example, one database per month), and to generate a temporary database on memory and discard it on darktable closing (if you only want to use xmp sidecars). Note that the latter doesn't eliminate the "import into database step", so probably is not what you're thinking (is more geared to people that open the images from another program or the file manager). According to your workflow description I would import a single session at a time, using the --library option to save the database file in the same folder as the photo session. Once you finish and if you don't want to keep the database file, just make sure that edits are saved to the xmps and delete the database file. Regards, Guillermo ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
