On 2017-05-23 11:13, Jens Georg wrote:
Hi,The photos were made around 13 hours (11 UTC). I can check the exif date on JPG (and it is correct on one of the failed photos), but I don't know how to see the timestamp on the NEF for verification.try the exiv2 commandline tool. that should be able to read it.
cer@minas-tirith:~/Pictures/2017/05> exiv2 DSC_2295.NEF Image timestamp : 2017:05:13 16:48:17 cer@minas-tirith:~/Pictures/2017/05> exiv2 DSC_2295.JPG Image timestamp : 2017:05:13 16:48:17 cer@minas-tirith:~/Pictures/2017/05> exiv2 DSC_2340.NEF Image timestamp : 2017:05:13 17:16:34 cer@minas-tirith:~/Pictures/2017/05> exiv2 DSC_2340.JPG Image timestamp : 2017:05:13 17:16:34 The times match.
Is there any method to force shotwell to accept a pair of JPG and NEF as the same photo, after the bad import? If there isn't, could you add it? Even as an external CLI tool.Might be doable, since it is (as far as I see it) just an entry in the database.
Thanks :-)
This is a failure that happens almost on every import from the camera. I can live with the crashes, but unpaired photos are a real nuisance.I would be interested in the crashes as well, though.
Sure, I can run the program from the terminal and see what it says when
it crashes next. But I'm not running the latest version because my
distro doesn't have it (Leap 42.2). I will have a look at trying to
build it myself.
It is a very good program; the raw photos mismatch is the only problem,
and happens perhaps to 2% of the photos.
What I have done sometimes is move those problem files to somewhere the
program doesn't see it, then delete from database those orphan photos
(needs a restart), place the photos back into the correct directory, and
restart to force an automatic import. Sometimes it work, sometimes it
doesn't. But it takes long, because the automatic import takes very long.
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" (Minas Tirith))
Attachment:
signature.asc
Description: OpenPGP digital signature