https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #29 from Maik Qualmann ---
I think it was the output of 3 x verbose from ExifTool (-v3) and I grabbed the
UserComment from it.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In|7.1.0 |7.3.0
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #27 from caulier.gil...@gmail.com ---
Maik,
>From your comment #26, how did you print the raw data values from tags with
ExifTool ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
Maik Qualmann changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=422240
ja...@lab6.com changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=422240
ja...@lab6.com changed:
What|Removed |Added
CC||ja...@lab6.com
--- Comment #24 from
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #23 from MarcP ---
It only happened once to me, but I was just saying that it was a possibility.
Using an external tool (e.g. http://exif.regex.info/exif.cgi ) you can make
sure if the text "binary comment" has actually been written to the
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #22 from loyukfai ---
(In reply to Maik Qualmann from comment #20)
> An existing comment is not deleted from the DB when the metadata is re-read
> unless the option to clean up the database is temporarily activated in the
> digiKam metadata
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #21 from loyukfai ---
(In reply to MarcP from comment #18)
> In a few cases, the words "binary comment" were saved into the picture as
> the comment when I saved the metadata overwriting the actual comment. If
> re-reading the metadata
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #20 from Maik Qualmann ---
An existing comment is not deleted from the DB when the metadata is re-read
unless the option to clean up the database is temporarily activated in the
digiKam metadata setup.
Maik
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #19 from caulier.gil...@gmail.com ---
Another case, is the Exiv2 shared library version which deal with the "comment
contents"
In face Exiv2 must detect and decode the binary form automatically. If you have
a older Exiv2 version, Exiv2 will
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #18 from MarcP ---
In a few cases, the words "binary comment" were saved into the picture as the
comment when I saved the metadata overwriting the actual comment. If
re-reading the metadata doesn't change it, that might be this case.
--
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #17 from caulier.gil...@gmail.com ---
Perform a "Read-read metadat from image to database"...
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
loyukfai changed:
What|Removed |Added
CC||loyuk...@gmail.com
--- Comment #16 from loyukfai
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #15 from Maik Qualmann ---
Git commit 3b9b6615fd7b6a9711a5aa8986d143429bb31909 by Maik Qualmann.
Committed on 23/08/2020 at 07:02.
Pushed by mqualmann into branch 'master'.
filter "binary comment" from the comment fields
Since Exiv2-0.27.3
https://bugs.kde.org/show_bug.cgi?id=422240
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #13 from MarcP ---
And finally, since the XMP seemed to be corrupted, I tagged the face once
again, and checked the exiv2 output. This time it seems that the XMP metadata
could be repaired and everything looks fine:
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #12 from MarcP ---
Update:
I tagged that picture with a face, and ran the same command again. After
re-reading the metadata, now the caption appears, but it seems that the XMP
metadata is corrupted somehow. This is the output (I redacted
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #11 from MarcP ---
Just to provide more information, even if it's not caused by digikam, some of
the files are still affected after restarting digikam.
I ran "exiv2 -pa" on the affected file, this is what I see. As a reference, the
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #10 from Maik Qualmann ---
For interest only, that was the bug report for Exiv2:
https://github.com/Exiv2/exiv2/issues/597
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #9 from Maik Qualmann ---
The bug also affects Gimp... The problem may have arisen during the conversion.
https://gitlab.gnome.org/GNOME/gimp/-/issues/2111
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #8 from MarcP ---
Oh, but these were all JPG pictures. I only use PNG during the scan process so
I don't lose quality when editing the picture. But digikam only used the jpg
version.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #7 from Maik Qualmann ---
Hmm, PNG files were very problematic before Exiv2-0.27.1. Exiv2 saved the color
profile / name incorrectly and calculated an incorrect checksum.
Maik
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #6 from MarcP ---
I see. The metadata was only edited in digikam. Prior to that, this is what I
did:
I scanned the picture (using Xsane) to png, straightened and cropped the
picture using gimp and saved to jpg, copied to a folder in my
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #5 from Maik Qualmann ---
The string "binary comment" does not come from digiKam. So Exiv2 decoded this.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #4 from Maik Qualmann ---
Is that the collection about the bad network connection? Exiv2 probably had
read errors from the file. I've never seen this problem before.
Maik
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #3 from Maik Qualmann ---
Reading the metadata again fixes it ???
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422240
--- Comment #2 from Maik Qualmann ---
Exiv2 cannot decode the field because some program wrote there wrong data. Also
possible that it is an audio file or the like. What does Exiftool decode?
Maik
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=422240
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=422240
MarcP changed:
What|Removed |Added
CC||iwannaber...@gmail.com
--
You are receiving this mail
30 matches
Mail list logo
