Read Error in windows version of Digikam but not in Linux version
I'm a new Digikam user.
I am trying to organise all my old photos and maintain things ongoing. I
have a collection of older images, mainly jpegs and some newer RAW images
taken from a Nikon D7200 camera. All stored on a local NAS.
I have 2 instances of Digikam installed.
Version 5.6.0 on a laptop running Ubuntu Mate
Version 5.9.0 on an different Laptop running Windows 10
I installed the Ubuntu version first and set it up and it seems to be
running OK. However my windows 10 laptop is far more powerful so I decided
to try the windows version.
On this instance when I set up Digikam the same and add the same NAS folder
as a collection I get a load of errors when I run Digikam and when I try to
open any of the RAW images downloaded from the camera.
The errors I am getting are:
Read Error at Scanline xxxxxxx, got 252 bytes, expected 8160
Unknown Field with tag 36867 (0x9003) encountered
ASCII value for TAG 'Copyright' contains null byte in value
Value incorrectly truncated during reading due to implementation
These errors despite reading exactly the same files in both instances.
I have asked this question on the digikam forum and am told that it the errors are comming from Exiv.
Can anyone here help with this?
Thanks and Regards
RE: Read Error in windows version of Digikam but not in Linux version - Added by Robin Mills 3 months ago
Please attach a file and I will investigate. I don't know anything about digiKam. The Exiv2 library also provides a command-line utility exiv2(.exe) which enable the user to read, write, modify and remove metadata. In the first instance, it would be very help for you to execute the command:
$ exiv2 -pa foo.jpgThe message
"Read Error at Scanline xxxx"is coming from digiKam and I don't know what it means.
I have a Nikon D5300. It doesn't store "copyright" in the metadata:
836 rmills@rmillsmbp:~/gnu/github/exiv2/exiv2 $ exiv2 -pa /Volumes/Backup/Photos/2016/Raw/DSC_0001.NEF | grep -i copyIs it possible that the Copyright metadata is added by digiKam when your image is imported?
It's not helpful for digiKam to dump this on Exiv2 for support. In the first instance, I would prefer that they investigate and identify the issue.