On Mon, Oct 17, 2022 at 03:17:38PM -0400, Patrick Shanahan wrote:
* David Vincent-Jones <david...@gmail.com> [10-17-22 12:46]:
Probably Patrick because I did not know of that option.
Most software systems, that I have used, automatically save work as a
background process and on a preset time basis. Do you think that this might
be a useful addition for dt?
you missed it. dt writes xmp files as I edit or open images and on import
while it applies the default and scripted settings.
open config
go to storage
look at xmp
"write sidecar file for each image"
select "on import" or "after edit"
I too have observed this behavior in the past (haven't crashed in a
while so I can't verify recent versions). Yes, DT writes the XMP files
after every change, so nothing is truely lost, but it does not write the
main database as frequently if at all before shutdown, which I think is
David's concern. Consider the following steps:
* Open darktable, import some images
* Close darktable, database is saved, all is good
* Open darktable again, edit some images
* System crashes (power failure, whatever)
* Start darktable again
Now, the database has recorded the images as being there, but the edits
are only present in the XMP files, so the edits appear to be lost. They
can be recovered by reimporting the files, which will reload the XMP
sidecars, but it's somewhat surprising to need an extra step to recover
a database which, hypothetically, should be at least as durable as the
sidecars.
--
Bruce Guenter <br...@untroubled.org> https://untroubled.org/
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
