Thank you. That worked perfectly, all information recovered, tags and
edits/versions of images back. I'm up and running again. I really
appreciate the reassurance before taking the plunge (there are only so
many backups you can take of 30GB worth of files...).
Best wishes,
Adrian
On 15/07/16 23:43, I. Ivanov wrote:
You can try a test.
1. Copy a folder - together with the side cars to a test location and
then import it. Everything should be properly populated. If it works
well - then you will know that you can import normally. I have removed
images before many times and re import without issues.
2. You can copy to a safe location ~/.config/darktable/, stop DT,
remove the folder ~/.config/darktable/ and replace it with the one you
have from DT 1.6.2. Then start DT - it should manage to deal with the
folder.
If an image is in DT database but no on the file system - DT gives
skulls. If this is the case - you can remove the image from DB by
"remove from collection" and re import it.
To the best of my knowledge - DT is not destructive when it comes to
the raw images. The side cars however - as soon as it start using them
- it will write there because these are the working files. If you want
to keep 2 copies you can duplicate a file (it will create a new sidecar).
Under the history stack - right side on LT module there is "load
sidecar file". This can give you some additional options (I have not
tested them) but I don't think I would use it for very big amount of
images that have different corrections. Modes are append or override.
Hope this helps,
Regards,
B
On 16-07-15 12:12 PM, Adrian Lester wrote:
Please bear with me, I'm new to the list and fairly new to darktable.
I installed darktable last year, went through the learning curve of
at least basic usage, started a new project or two using it including
a fair amount of post-processing, and then imported and started
sorting through all my photographs going back to 2004. All good up
until a catastrophic hard drive failure of my laptop a few weeks ago.
The directory structure with all the photographs and their sidecar
files is safe on my samba server and I had a previously saved copy of
my ~/.config/darktable/darktablerc which I have given my newly
installed replacement darktable. However, despite now having the
correct paths from that old config and access to the filesystem, it
has no recollection of collections/images (other than showing my
recently used collections, but nothing in them) - presumably because
its library/database, which was stored on the local drive, is gone.
Please excuse me if I am using incorrect terminology.
What I want to do, if there is a way, is to either regenerate the
database from the sidecar files or re-import the
directories/collections/film rolls from the filesystem in such a way
that their sidecar files and any other data there will be read in
(and certainly not overwritten), processed versions of images will be
recovered etc. Is this to any extent possible? If so, how should I go
about it? I do have backups, but nonetheless I don't want to muck up
and make things worse.
On a less important note, I also have a saved copy of my old
darktable.gtkrc, but am not sure where to put this to have the new
version of darktable read it as it's ignored in ~/.config/darktable/.
In terms of software versions, this is what I had and have:
Old system - Debian Wheezy
Darktable 1.6.2 from source
New system - Debian Jessie
Darktable 2.0.5 from source
Many thanks in advance,
Adrian
____________________________________________________________________________
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]
