hi, we are usually very concerned about keeping backward compatibility if at all possible. we were just discussing in IRC how to bring back support for these .dt files. back then i don't think many people used dt at all, and in fact this is the first time this issue comes up. i'd consider it a more exotic edge case.. but ideally we want to keep compatibility even here.
cheers, jo On Thu, Dec 28, 2017 at 8:15 AM, I. Ivanov <iv3...@gmail.com> wrote: > Hi Guys, > > A side question closely related to this subject. > > If the .XMP files evolve in the future (this is expected) - what is the > best approach for a user to make sure historical images are still readable > by DT (in the future)? > > I understand if the user always keeps up with upgrades this should not be an > issue but if somebody is to have a very large collection - they may not keep > all images imported all the time (so in theory have similar case one day). > > I cannot code at this level (so I wouldn't be able to fix it myself). But I > love DT and I am 100% in - so I am just trying to look what it may be 5 or > 10 years from now. Or perhaps you guys already thought about such > possibility? > > Regards, > > B > > > On 2017-12-27 10:14 AM, Martín Soto wrote: > > Hi Johannes, > > thankfully, your commit link put me on the right track. I had to choose > between manually redoing 520 pictures, or writing a script to parse and > convert the format, and decided to do the second as it appeared to be more > fun. > > It was! If anyone is interested, please find the Python script attached. > What it does is parsing the .dt file (I followed the C code) and replacing > the image history in the database by the history contained in the .dt file. > This seems to work for all images I checked so far, but may fail in special > cases (modules that became obsolete, for example) so your mileage may vary. > > In any case: make sure that you create a backup of your library database > before doing anything; YOU HAVE BEEN WARNED! ;-) > > Best wishes, > > Martín > > On Wed, Dec 27, 2017 at 11:18 AM, johannes hanika <hana...@gmail.com> wrote: >> >> hi, >> >> please don't rename these files.. they are ancient to an extent that i >> forgot what the format was. there was once a version of dt that could >> read both files, so i guess there's hope. i don't think you can >> reasonably read these files nowadays, but the way to do it would >> probably be a standalone tool that converts them to xmp, using some >> arcane code from git. >> >> as a point of reference, this commit removed the writing functions (so >> the diff may be seen as the spec of these files): >> >> >> https://github.com/darktable-org/darktable/commit/8883a806cbe71f9c2789372defd9156fa7d77d54 >> >> -jo >> >> On Wed, Dec 27, 2017 at 1:53 PM, Michael Rasmussen <m...@miras.org> wrote: >> > On Wed, 27 Dec 2017 01:36:34 +0100 >> > Martín Soto <dons...@gmail.com> wrote: >> > >> >> Hi everyone: >> >> >> >> Looking at some of my older pictures, I found a bunch of files that >> >> were >> >> processed with an ancient version of Darktable, which produced .dt >> >> sidecars >> >> instead of .xmp. As far as I can see, though, recent versions of >> >> Darktable >> >> will just ignore these files and create fresh .xmp's for images having >> >> a >> >> .dt sidecar. >> >> >> >> I'd really love to recover the settings I used back then, so reading >> >> the >> >> .dt files would be great. Is there a reasonable way of doing it? >> >> >> > Have you tried simply renaming them from some_name.dt to some_name.xmp >> > >> > -- >> > Hilsen/Regards >> > Michael Rasmussen >> > >> > Get my public GnuPG keys: >> > michael <at> rasmussen <dot> cc >> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E >> > mir <at> datanom <dot> net >> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C >> > mir <at> miras <dot> org >> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 >> > -------------------------------------------------------------- >> > /usr/games/fortune -es says: >> > Colorless green ideas sleep furiously. >> >> ____________________________________________________________________________ >> 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 > > > > ____________________________________________________________________________ > 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
