Am 16.01.2016 um 22:55 schrieb johannes hanika: > On Sun, Jan 17, 2016 at 10:45 AM, Bernhard > <darkta...@intervalsignals.org> wrote: >> >> ~/.config/darktable >> >> This is because modules can also change with the upgrade and thus rewrite >> the xmps in a different form which cannot be read by the same module of the >> previous version. > > yes, that is a good idea. but patrick is still right that as long as > you have the db it will be the primary source of information and could > theoretically be used to write new xmp (which then contain the old > information again). but yeah.. if you have both it's better (in the > sense of backup).
Considering the fact that the xmp files may also contain some information which man not yet be in the database you may run into other trouble. My workflow is: process and export from darktable, later tagging in digikam. Unless I have a reason to process the photo again, they stay in digikam and darktable's database may not see any xmp-changes by digikam. cu Peter ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
