On 2018-12-24 01:06, Bernhard wrote:
There is an option in darktable that will help you with this:
look for updated xmp files on startup
Check file modification times of all XMP files on startup to find out
if any got updated in the meantime by some other software. If updated
XMP files are found a menu opens for the user to decide which of the
XMP files to be reloaded – replacing darktable's database entries by
the XMP file contents – and *which of the XMP files to be overwritten
by darktable's database*. Activating this option also causes
darktable to check for text sidecar files that have been added after
import time – see option “overlay txt sidecar over zoomed images” in
Section 8.1, “GUI options”
<https://www.darktable.org/usermanual/en/preferences_chapter.html#gui_options>
(default off).
see https://www.darktable.org/usermanual/en/core_options.html
Thank you - looks like it is bidirectional (XMP can update DB and DB can
update XMP). For some reason I thought it is unidirectional (XMP can
update DB only).
I will certainly check various options and test them. I do keep backup
of my files but it was daily. I did accelerate this significantly since
yesterday. It is good that multiple options exist.
--
regards
Bernhard
https://www.bilddateien.de
Thank you,
B
I. Ivanov schrieb am 24.12.18 um 02:21:
On 2018-12-23 16:12, Edgardo Hoszowski wrote:
There's an option on lighttable under history stack "write sidecar
files", that should do it.
This is very promising! Thank you!
I did few tests and works well. It is exactly the function I was
looking for.
Regards,
B
El dom., 23 dic. 2018 a las 20:54, I. Ivanov (<[email protected]
<mailto:[email protected]>>) escribió:
On 2018-12-23 15:28, Patrick Shanahan wrote:
> * I. Ivanov <[email protected] <mailto:[email protected]>>
[12-23-18 17:57]:
>> Hi Guys,
>>
>> I had an unfortunate event to clear metadata from about 600
images (it took
>> me close to 3h to restore as much as I could).
>>
>> Because there is no "undo" this brings me to the question.
>>
>> What can I do to have a good backup for such cases? I can
backup easily (and
>> very frequent) "/home/myhome/.config/darktable"
>>
>> However - if metadata (or tags) happen to be deleted by
accident and I
>> restore the DB - how can I push the DB to re populate the XMP
files?
> perhaps (not tried), remove the images from the db
> import the images again
> will/should read the accompaning xmp files
>
> or, maybe just telling dt to read the xmp files will work
Not sure if I expressed myself correctly... If I backup
"/home/myhome/.config/darktable" then data.db and library.db would
be the "correct" ones.
To my best knowledge - when Darktable works - it uses data from
the .DB files (not from .XMP) and when the file changes - it
populates the data to .XMP
The reason why I am trying to backup the database (as an opposite
to the .XMP) is because I can easily backup the DB in the cloud
with multiple versions (and restore what I need). I wouldn't be
able to easily restore the .XMP files (to the belonging locations)
even if I manage to accelerate the frequency of their backups.
DT can check for changed .XMP files but I am under impression that
the checking and populating of changes is unidirectional - XMP to
DB (not DB to XMP). Is it possible at all to push what is stored
in the .DB files to the .XMP? For example - can I delete the .XMP
files and rely that the information stored in the .DB would create
accurate .XMP for all files that are missing the .XMP?
Regards,
B
>
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to
[email protected]
<mailto:darktable-user%[email protected]>
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to
[email protected]
____________________________________________________________________________
darktable user mailing list to unsubscribe send a mail to
[email protected]
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
