Le 21/11/2016 à 18:49, Patrick Shanahan a écrit :
* Stéphane Gourichon <[email protected]> [11-21-16 12:21]:
Also, option write_sidecar_files is not the wished behavior, as XMP files
are definitely useful when they contain not only generated information, cf.
8.2. Core options | user manual | darktable
<http://www.darktable.org/usermanual/ch08s02.html.php>
there is an option to "write sidecar file for each image". turn it "off".
I already covered this case, see citation above.
Don't get me wrong, XMP sidecar is necessary, I even consider it the
primary storage for two reasons:
(1) I love darktable's ability to move my HD to any machine and open
files from there with all their edits even if local database does not
know them (also via network mount)
(2) Several times within recent years I had darktable *lose* editing
work in database *and* overwrite XMP files with default content, which
is not good. Now I version control XMP files to protect against this. My
1.3Tb, 260k+ photo+video collection is now in git-annex: XMP sidecars as
regular git files, RAW and JPG in the annex. Efficiently replicated by
git-annex. Should be safe and somehow future-proof.
Yet, generating wads of XMP any time darktable is used to view a
pristine directory on other people's drives and network mounts feels
clutter to me and others. It also happened that I lost editing work
removing unwanted XMPs to clean up the clutter... ಠ_ಠ
--
Stéphane Gourichon
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
