if you have regulary backups of your ~/.config/darktable directory you can replace library.db with a recently backup. Then you lose all edits done after the backup.
if you have regulary backups of the image directories (& didnt disable writing xmp files) you can restore the xmp files and let dt check for changed xmps at startup via preferences setting. Then you can select to apply the xmp over the database see: https://docs.darktable.org/usermanual/4.0/en/preferences-settings/storage/#xmp Am Fr., 3. Feb. 2023 um 07:12 Uhr schrieb Andrew Greig < and...@algphoto.com.au>: > Hi All, > > I found that the information I received from Patrick Shannahan really > useful so I loaded a couple of processes in Darktable and acted as a taxi > for my mother in law, did some shopping had coffee and the results were > waiting for me when I arrived home. This will be useful for the times when > I am working late, I can set the tasks running and head to bed. Everything > will be in place in the morning. > > The disaster above was caused by using the history stack to apply certain > modules in the Light-table, I inadvertently blitzed the whole history stack > for the complete set of images. Is there any way to reverse that, or do I > need to wipe all of the sidecar files and re-import the RAW files? > > Many thanks > -- > > ____________________________________________________________________________ > darktable user mailing list to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
