Hi
I meet the following problems when tagging multiple images at the same time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which I happen to have on another machine. Anyone else see this? How to generate: Select 10 images. Apply a tag to all. Problem 1, XMP metadata not always updated in image files: When writing metadata to the image files, dk occasionally omits to write the new XMP metadata, leaving the previous XMP metadata in the image file. This can be seen by for example by tag fields not being updated when tags are changed and applied. You have to look through the images one-by-one to find one or two where this has happened. (The IPTC metadata is always written correctly, so when this happens there is a difference between the IPTC:Keywords (tags) field and the various XMP tags fields.) Problem 2, xmp sidecars sometimes truncated: Occasionally one or more of the xmp sidecars is truncated to just its first line, with a size of only 39 bytes. (Use a file manager to see that this has happened.) If the problems don't show up the first time, change the tags and then re-apply. Over 2 or 3 cycles I always see both problems appear. I see this behaviour when 10 (or more) images are selected. I have not seen it with only 1 or 2 images selected. I haven't checked in between. The problems appear random. A file which has a problem the first time usually doesn't have it after tagging a second time. The problems appear to be independent, i.e. when writing metadata to both sidecars and image files, they don't occur together, they affect different images. Regards Philip _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 05/19/2014 11:24 PM, Phil wrote:
> I meet the following problems when tagging multiple images at the same > time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which > I happen to have on another machine. Anyone else see this? Hi DK 4.1.0 ? It doesnt exist... -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
4.1.0 is what the current source from git calls itself, I.e. it's the development version.
Can you try with 4.0.0? Best Philip ----- Mail d'origine ----- De: maderios <[hidden email]> À: [hidden email] Envoyé: Tue, 20 May 2014 18:03:06 +0200 (CEST) Objet: Re: [Digikam-users] 2 problems tagging multiple images On 05/19/2014 11:24 PM, Phil wrote: > I meet the following problems when tagging multiple images at the same > time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which > I happen to have on another machine. Anyone else see this? Hi DK 4.1.0 ? It doesnt exist... -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 05/20/2014 06:43 PM, [hidden email] wrote:
> 4.1.0 is what the current source from git calls itself, I.e. it's the development version. > Can you try with 4.0.0? > Best Philip > Hi OK... Tagging (only XMP) with DK 4.0 (Debian Sid) works for me *now*. I hate Sqlite (so slow). I succeeded to use this DK version with Mysql (external DB): much faster. I have to test more... -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 20/05/14 18:56, maderios wrote:
> On 05/20/2014 06:43 PM, [hidden email] wrote: >> 4.1.0 is what the current source from git calls itself, I.e. it's the >> development version. >> Can you try with 4.0.0? >> Best Philip >> > Hi > OK... > Tagging (only XMP) with DK 4.0 (Debian Sid) works for me *now*. > I hate Sqlite (so slow). I succeeded to use this DK version with Mysql > (external DB): much faster. > I have to test more... Just to be clear, I haven't noticed any problems with dk managing its own database, only with writing metadata to xmp sidecars or to the image files themselves (which by the way I guess is slower than writing the database). _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Tuckey-2
For 4.0.0 I've also experienced that tags I applied in DK we're not picked up by Darktable although I have the "write to sidecar" in DK enabled. After going back to DK and forcing a rewrite of tags it was OK. I didn't however investigate deeper, so not sure whether it's exactly the same problem...
-- Composed on my tablet. Apologies for typos. > On 21 May, 2014, at 2:03, "Phil" <[hidden email]> wrote: > >> On 20/05/14 18:56, maderios wrote: >>> On 05/20/2014 06:43 PM, [hidden email] wrote: >>> 4.1.0 is what the current source from git calls itself, I.e. it's the >>> development version. >>> Can you try with 4.0.0? >>> Best Philip >> Hi >> OK... >> Tagging (only XMP) with DK 4.0 (Debian Sid) works for me *now*. >> I hate Sqlite (so slow). I succeeded to use this DK version with Mysql >> (external DB): much faster. >> I have to test more... > > Just to be clear, I haven't noticed any problems with dk managing its > own database, only with writing metadata to xmp sidecars or to the image > files themselves (which by the way I guess is slower than writing the > database). > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Sounds like it could be the same problem, I.e. the sidecars problem. It is easy to check, tag multiple images and then look in your file browser (sort on file size) to see if any of the sidecars are very small, 39 bytes for me.
I agree that rewriting tags on the affected images one-by-one fixes the sidecars, but if you retag simultaneously all the images you were working on, you may fix the ones initially affected but create the problem for others. On 21 May 2014 04:31:25 CEST, HaJo Schatz <[hidden email]> wrote: For 4.0.0 I've also experienced that tags I applied in DK we're not picked up by Darktable although I have the "write to sidecar" in DK enabled. After going back to DK and forcing a rewrite of tags it was OK. I didn't however investigate deeper, so not sure whether it's exactly the same problem... -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Tuckey-2
On 05/20/2014 10:32 PM, Phil wrote:
> On 20/05/14 18:56, maderios wrote: >> On 05/20/2014 06:43 PM, [hidden email] wrote: >>> 4.1.0 is what the current source from git calls itself, I.e. it's the >>> development version. >>> Can you try with 4.0.0? >>> Best Philip >>> >> Hi >> OK... >> Tagging (only XMP) with DK 4.0 (Debian Sid) works for me *now*. >> I hate Sqlite (so slow). I succeeded to use this DK version with Mysql >> (external DB): much faster. >> I have to test more... > > Just to be clear, I haven't noticed any problems with dk managing its > own database, only with writing metadata to xmp sidecars or to the image > files themselves (which by the way I guess is slower than writing the > database). Conditions: I only use xmp keywords tags. Debian Jessie/testing system + Digikam-4.0.0-1 Sid packages No any problem with writing/updating metadata to images and xmp sidecars. -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 21/05/14 14:37, maderios wrote:
> On 05/20/2014 10:32 PM, Phil wrote: >> On 20/05/14 18:56, maderios wrote: >>> On 05/20/2014 06:43 PM, [hidden email] wrote: >>>> 4.1.0 is what the current source from git calls itself, I.e. it's the >>>> development version. >>>> Can you try with 4.0.0? >>>> Best Philip >>>> >>> Hi >>> OK... >>> Tagging (only XMP) with DK 4.0 (Debian Sid) works for me *now*. >>> I hate Sqlite (so slow). I succeeded to use this DK version with Mysql >>> (external DB): much faster. >>> I have to test more... >> >> Just to be clear, I haven't noticed any problems with dk managing its >> own database, only with writing metadata to xmp sidecars or to the image >> files themselves (which by the way I guess is slower than writing the >> database). > > Conditions: I only use xmp keywords tags. Debian Jessie/testing system + > Digikam-4.0.0-1 Sid packages > No any problem with writing/updating metadata to images and xmp sidecars. Thanks for looking. How do you force dk to only write xmp metadata? When I add a tag to an image, dk writes it to 5 metadata fields, 4 of which are xmp but also the IPTC Keywords field. Dk also writes various housekeeping information to other IPTC fields. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Tuckey-2
I went back to 3.5.0 to do more testing and I found both the problems
which I described below for 4.0.0. (Both running on OSX 10.9.2.) When sidecars are truncated, I see the following error messages on stdout: digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : XMP Toolkit error 101: Unregistered schema namespace URI digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : Failed to encode XMP metadata. digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file ' "20140101-144225-IMG_4657.jpg" ' written to XMP sidecar. I don't see any error messages on stdout which correspond to the other problem, when XMP metadata in the image file is not updated. I have done more testing with 3.3.0 on ubuntu 12.04 and have not been able to provoke these problems. Philip On 19/05/14 23:24, Phil wrote: > Hi > > I meet the following problems when tagging multiple images at the same > time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which > I happen to have on another machine. Anyone else see this? > > How to generate: > Select 10 images. > Apply a tag to all. > > Problem 1, XMP metadata not always updated in image files: > When writing metadata to the image files, dk occasionally omits to write > the new XMP metadata, leaving the previous XMP metadata in the image > file. This can be seen by for example by tag fields not being updated > when tags are changed and applied. You have to look through the images > one-by-one to find one or two where this has happened. (The IPTC > metadata is always written correctly, so when this happens there is a > difference between the IPTC:Keywords (tags) field and the various XMP > tags fields.) > > Problem 2, xmp sidecars sometimes truncated: > Occasionally one or more of the xmp sidecars is truncated to just its > first line, with a size of only 39 bytes. (Use a file manager to see > that this has happened.) > > If the problems don't show up the first time, change the tags and then > re-apply. Over 2 or 3 cycles I always see both problems appear. > > I see this behaviour when 10 (or more) images are selected. I have not > seen it with only 1 or 2 images selected. I haven't checked in between. > > The problems appear random. A file which has a problem the first time > usually doesn't have it after tagging a second time. > > The problems appear to be independent, i.e. when writing metadata to > both sidecars and image files, they don't occur together, they affect > different images. > > Regards > Philip > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
An XMP namespace URI is not registered by Exiv2, and library do know
how to manage it. digiKam do not manage XMP namespace registration. All is done by Exiv2 by default. We can do it, just to declare URI, but structure managed into are unknow. The Q is w : which XMP namespace generate this error ? I recommend to report this problem to Exiv2 project, including image with metadata to investiguate. Best Gilles Caulier 2014-05-21 23:35 GMT+02:00 Phil <[hidden email]>: > I went back to 3.5.0 to do more testing and I found both the problems which > I described below for 4.0.0. (Both running on OSX 10.9.2.) > > When sidecars are truncated, I see the following error messages on stdout: > > digikam(21240)/KEXIV2 > KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : XMP > Toolkit error 101: Unregistered schema namespace URI > digikam(21240)/KEXIV2 > KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : Failed > to encode XMP metadata. > digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file ' > "20140101-144225-IMG_4657.jpg" ' written to XMP sidecar. > > I don't see any error messages on stdout which correspond to the other > problem, when XMP metadata in the image file is not updated. > > I have done more testing with 3.3.0 on ubuntu 12.04 and have not been able > to provoke these problems. > > Philip > > > > On 19/05/14 23:24, Phil wrote: >> >> Hi >> >> I meet the following problems when tagging multiple images at the same >> time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which >> I happen to have on another machine. Anyone else see this? >> >> How to generate: >> Select 10 images. >> Apply a tag to all. >> >> Problem 1, XMP metadata not always updated in image files: >> When writing metadata to the image files, dk occasionally omits to write >> the new XMP metadata, leaving the previous XMP metadata in the image >> file. This can be seen by for example by tag fields not being updated >> when tags are changed and applied. You have to look through the images >> one-by-one to find one or two where this has happened. (The IPTC >> metadata is always written correctly, so when this happens there is a >> difference between the IPTC:Keywords (tags) field and the various XMP >> tags fields.) >> >> Problem 2, xmp sidecars sometimes truncated: >> Occasionally one or more of the xmp sidecars is truncated to just its >> first line, with a size of only 39 bytes. (Use a file manager to see >> that this has happened.) >> >> If the problems don't show up the first time, change the tags and then >> re-apply. Over 2 or 3 cycles I always see both problems appear. >> >> I see this behaviour when 10 (or more) images are selected. I have not >> seen it with only 1 or 2 images selected. I haven't checked in between. >> >> The problems appear random. A file which has a problem the first time >> usually doesn't have it after tagging a second time. >> >> The problems appear to be independent, i.e. when writing metadata to >> both sidecars and image files, they don't occur together, they affect >> different images. >> >> Regards >> Philip >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi Gilles
Unfortunately the problem cannot just be an unknown URI in some of my images, because: - I am simultaneously applying the same tags to many photos which have all come out of the same camera, and the problem only occurs for one or two of them each time; - if I re-tag the same photos, the ones which had a problem the first time are usually ok, but the problem appears for one or two others, which had no problem the first time; - also, if I take an image for which this error has just occurred and rewrite the tags of only this image, it works fine. So I cannot provide a specific image which provokes this error. It results from the process of tagging many photos at the same time in dk. I have the impression that it occurs less often in 3.5.0 than in 4.0.0. In 3.5.0 I have to select about 100 photos and tag them for the problem to occur regularly. Best Philip On 22/05/14 07:22, Gilles Caulier wrote: > An XMP namespace URI is not registered by Exiv2, and library do know > how to manage it. > > digiKam do not manage XMP namespace registration. All is done by Exiv2 > by default. > > We can do it, just to declare URI, but structure managed into are unknow. > > The Q is w : which XMP namespace generate this error ? > > I recommend to report this problem to Exiv2 project, including image > with metadata to investiguate. > > Best > > Gilles Caulier > > 2014-05-21 23:35 GMT+02:00 Phil <[hidden email]>: >> I went back to 3.5.0 to do more testing and I found both the problems which >> I described below for 4.0.0. (Both running on OSX 10.9.2.) >> >> When sidecars are truncated, I see the following error messages on stdout: >> >> digikam(21240)/KEXIV2 >> KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : XMP >> Toolkit error 101: Unregistered schema namespace URI >> digikam(21240)/KEXIV2 >> KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : Failed >> to encode XMP metadata. >> digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file ' >> "20140101-144225-IMG_4657.jpg" ' written to XMP sidecar. >> >> I don't see any error messages on stdout which correspond to the other >> problem, when XMP metadata in the image file is not updated. >> >> I have done more testing with 3.3.0 on ubuntu 12.04 and have not been able >> to provoke these problems. >> >> Philip >> >> >> >> On 19/05/14 23:24, Phil wrote: >>> >>> Hi >>> >>> I meet the following problems when tagging multiple images at the same >>> time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which >>> I happen to have on another machine. Anyone else see this? >>> >>> How to generate: >>> Select 10 images. >>> Apply a tag to all. >>> >>> Problem 1, XMP metadata not always updated in image files: >>> When writing metadata to the image files, dk occasionally omits to write >>> the new XMP metadata, leaving the previous XMP metadata in the image >>> file. This can be seen by for example by tag fields not being updated >>> when tags are changed and applied. You have to look through the images >>> one-by-one to find one or two where this has happened. (The IPTC >>> metadata is always written correctly, so when this happens there is a >>> difference between the IPTC:Keywords (tags) field and the various XMP >>> tags fields.) >>> >>> Problem 2, xmp sidecars sometimes truncated: >>> Occasionally one or more of the xmp sidecars is truncated to just its >>> first line, with a size of only 39 bytes. (Use a file manager to see >>> that this has happened.) >>> >>> If the problems don't show up the first time, change the tags and then >>> re-apply. Over 2 or 3 cycles I always see both problems appear. >>> >>> I see this behaviour when 10 (or more) images are selected. I have not >>> seen it with only 1 or 2 images selected. I haven't checked in between. >>> >>> The problems appear random. A file which has a problem the first time >>> usually doesn't have it after tagging a second time. >>> >>> The problems appear to be independent, i.e. when writing metadata to >>> both sidecars and image files, they don't occur together, they affect >>> different images. >>> >>> Regards >>> Philip >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
The difference must be Exiv2 shared lib which can be updated between 2
digiKam versions. Go to Help/Components info dialog for details. At least, error message come from Adobe XMP SDK which is included in Exiv2, not digiKam... Gilles Caulier 2014-05-22 8:52 GMT+02:00 Phil <[hidden email]>: > Hi Gilles > Unfortunately the problem cannot just be an unknown URI in some of my > images, because: > - I am simultaneously applying the same tags to many photos which have all > come out of the same camera, and the problem only occurs for one or two of > them each time; > - if I re-tag the same photos, the ones which had a problem the first time > are usually ok, but the problem appears for one or two others, which had no > problem the first time; > - also, if I take an image for which this error has just occurred and > rewrite the tags of only this image, it works fine. > So I cannot provide a specific image which provokes this error. It results > from the process of tagging many photos at the same time in dk. > I have the impression that it occurs less often in 3.5.0 than in 4.0.0. In > 3.5.0 I have to select about 100 photos and tag them for the problem to > occur regularly. > Best Philip > > > > On 22/05/14 07:22, Gilles Caulier wrote: >> >> An XMP namespace URI is not registered by Exiv2, and library do know >> how to manage it. >> >> digiKam do not manage XMP namespace registration. All is done by Exiv2 >> by default. >> >> We can do it, just to declare URI, but structure managed into are unknow. >> >> The Q is w : which XMP namespace generate this error ? >> >> I recommend to report this problem to Exiv2 project, including image >> with metadata to investiguate. >> >> Best >> >> Gilles Caulier >> >> 2014-05-21 23:35 GMT+02:00 Phil <[hidden email]>: >>> >>> I went back to 3.5.0 to do more testing and I found both the problems >>> which >>> I described below for 4.0.0. (Both running on OSX 10.9.2.) >>> >>> When sidecars are truncated, I see the following error messages on >>> stdout: >>> >>> digikam(21240)/KEXIV2 >>> KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : XMP >>> Toolkit error 101: Unregistered schema namespace URI >>> digikam(21240)/KEXIV2 >>> KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : >>> Failed >>> to encode XMP metadata. >>> digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file ' >>> "20140101-144225-IMG_4657.jpg" ' written to XMP sidecar. >>> >>> I don't see any error messages on stdout which correspond to the other >>> problem, when XMP metadata in the image file is not updated. >>> >>> I have done more testing with 3.3.0 on ubuntu 12.04 and have not been >>> able >>> to provoke these problems. >>> >>> Philip >>> >>> >>> >>> On 19/05/14 23:24, Phil wrote: >>>> >>>> >>>> Hi >>>> >>>> I meet the following problems when tagging multiple images at the same >>>> time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which >>>> I happen to have on another machine. Anyone else see this? >>>> >>>> How to generate: >>>> Select 10 images. >>>> Apply a tag to all. >>>> >>>> Problem 1, XMP metadata not always updated in image files: >>>> When writing metadata to the image files, dk occasionally omits to write >>>> the new XMP metadata, leaving the previous XMP metadata in the image >>>> file. This can be seen by for example by tag fields not being updated >>>> when tags are changed and applied. You have to look through the images >>>> one-by-one to find one or two where this has happened. (The IPTC >>>> metadata is always written correctly, so when this happens there is a >>>> difference between the IPTC:Keywords (tags) field and the various XMP >>>> tags fields.) >>>> >>>> Problem 2, xmp sidecars sometimes truncated: >>>> Occasionally one or more of the xmp sidecars is truncated to just its >>>> first line, with a size of only 39 bytes. (Use a file manager to see >>>> that this has happened.) >>>> >>>> If the problems don't show up the first time, change the tags and then >>>> re-apply. Over 2 or 3 cycles I always see both problems appear. >>>> >>>> I see this behaviour when 10 (or more) images are selected. I have not >>>> seen it with only 1 or 2 images selected. I haven't checked in between. >>>> >>>> The problems appear random. A file which has a problem the first time >>>> usually doesn't have it after tagging a second time. >>>> >>>> The problems appear to be independent, i.e. when writing metadata to >>>> both sidecars and image files, they don't occur together, they affect >>>> different images. >>>> >>>> Regards >>>> Philip >>>> _______________________________________________ >>>> Digikam-users mailing list >>>> [hidden email] >>>> https://mail.kde.org/mailman/listinfo/digikam-users >>> >>> >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Tuckey-2
On 05/21/2014 05:57 PM, Phil wrote:
> How do you force dk to only write xmp metadata? When I add a tag to an > image, dk writes it to 5 metadata fields, 4 of which are xmp but also > the IPTC Keywords field. Dk also writes various housekeeping information > to other IPTC fields. First, with Exiv2 tool (or an other one), I delete all unwanted tags from pictures http://www.exiv2.org/ Then in DK, I disable all tags management except xmp: - settings, configure DK - metadata - behaviour: I clear all except image tags, read & write sidecar files (write to image and xmp sidecar), update file timestamp..., - display: unselect/clear all (exif, iptc, makernotes, etc) except xmp viewer -xmpviewer: select all Dont forget kipi plugins-> metadataEdit -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 22/05/14 14:27, maderios wrote:
> On 05/21/2014 05:57 PM, Phil wrote: > >> How do you force dk to only write xmp metadata? When I add a tag to an >> image, dk writes it to 5 metadata fields, 4 of which are xmp but also >> the IPTC Keywords field. Dk also writes various housekeeping information >> to other IPTC fields. > > First, with Exiv2 tool (or an other one), I delete all unwanted tags > from pictures > http://www.exiv2.org/ > Then in DK, I disable all tags management except xmp: > - settings, configure DK > - metadata > - behaviour: I clear all except image tags, read & write sidecar files > (write to image and xmp sidecar), update file timestamp..., > - display: unselect/clear all (exif, iptc, makernotes, etc) except xmp > viewer > -xmpviewer: select all > > Dont forget kipi plugins-> metadataEdit Thanks. If I understand correctly, you say that the display settings don't only control display of metadata in dk, but also have an effect on which metadata dk writes to the image files? So with the above configuration, dk doesn't write the image tags to an IPTC:Keywords field in the image file? _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-4
If dk is using the exiv2 I have installed from MacPorts then no, 3.5.0,
4.0.0 and 4.1.0 are all using the same version (0.24), I have compiled them all recently. Because of what I wrote below, it looks as though there is "random" corruption in metadata by the time it reaches the place in libexiv2 which is generating the error message. This corruption could be happening within libexiv2, or it might be in dk before giving the data to libexiv2. When we select and tag many images, does dk give libexiv2 the tags only once and a list of images to apply them to, or does it give the tags separately for each image? In the first case, any corruption must be in libexiv2. In the second case, it could be in libexiv2 or dk. (I'm not used to looking through complex code bases, it will take me some time just to find where this is happening...) Philip On 22/05/14 09:16, Gilles Caulier wrote: > The difference must be Exiv2 shared lib which can be updated between 2 > digiKam versions. > > Go to Help/Components info dialog for details. > > At least, error message come from Adobe XMP SDK which is included in > Exiv2, not digiKam... > > Gilles Caulier > > 2014-05-22 8:52 GMT+02:00 Phil <[hidden email]>: >> Hi Gilles >> Unfortunately the problem cannot just be an unknown URI in some of my >> images, because: >> - I am simultaneously applying the same tags to many photos which have all >> come out of the same camera, and the problem only occurs for one or two of >> them each time; >> - if I re-tag the same photos, the ones which had a problem the first time >> are usually ok, but the problem appears for one or two others, which had no >> problem the first time; >> - also, if I take an image for which this error has just occurred and >> rewrite the tags of only this image, it works fine. >> So I cannot provide a specific image which provokes this error. It results >> from the process of tagging many photos at the same time in dk. >> I have the impression that it occurs less often in 3.5.0 than in 4.0.0. In >> 3.5.0 I have to select about 100 photos and tag them for the problem to >> occur regularly. >> Best Philip >> >> >> >> On 22/05/14 07:22, Gilles Caulier wrote: >>> >>> An XMP namespace URI is not registered by Exiv2, and library do know >>> how to manage it. >>> >>> digiKam do not manage XMP namespace registration. All is done by Exiv2 >>> by default. >>> >>> We can do it, just to declare URI, but structure managed into are unknow. >>> >>> The Q is w : which XMP namespace generate this error ? >>> >>> I recommend to report this problem to Exiv2 project, including image >>> with metadata to investiguate. >>> >>> Best >>> >>> Gilles Caulier >>> >>> 2014-05-21 23:35 GMT+02:00 Phil <[hidden email]>: >>>> >>>> I went back to 3.5.0 to do more testing and I found both the problems >>>> which >>>> I described below for 4.0.0. (Both running on OSX 10.9.2.) >>>> >>>> When sidecars are truncated, I see the following error messages on >>>> stdout: >>>> >>>> digikam(21240)/KEXIV2 >>>> KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : XMP >>>> Toolkit error 101: Unregistered schema namespace URI >>>> digikam(21240)/KEXIV2 >>>> KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : >>>> Failed >>>> to encode XMP metadata. >>>> digikam(21240)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file ' >>>> "20140101-144225-IMG_4657.jpg" ' written to XMP sidecar. >>>> >>>> I don't see any error messages on stdout which correspond to the other >>>> problem, when XMP metadata in the image file is not updated. >>>> >>>> I have done more testing with 3.3.0 on ubuntu 12.04 and have not been >>>> able >>>> to provoke these problems. >>>> >>>> Philip >>>> >>>> >>>> >>>> On 19/05/14 23:24, Phil wrote: >>>>> >>>>> >>>>> Hi >>>>> >>>>> I meet the following problems when tagging multiple images at the same >>>>> time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which >>>>> I happen to have on another machine. Anyone else see this? >>>>> >>>>> How to generate: >>>>> Select 10 images. >>>>> Apply a tag to all. >>>>> >>>>> Problem 1, XMP metadata not always updated in image files: >>>>> When writing metadata to the image files, dk occasionally omits to write >>>>> the new XMP metadata, leaving the previous XMP metadata in the image >>>>> file. This can be seen by for example by tag fields not being updated >>>>> when tags are changed and applied. You have to look through the images >>>>> one-by-one to find one or two where this has happened. (The IPTC >>>>> metadata is always written correctly, so when this happens there is a >>>>> difference between the IPTC:Keywords (tags) field and the various XMP >>>>> tags fields.) >>>>> >>>>> Problem 2, xmp sidecars sometimes truncated: >>>>> Occasionally one or more of the xmp sidecars is truncated to just its >>>>> first line, with a size of only 39 bytes. (Use a file manager to see >>>>> that this has happened.) >>>>> >>>>> If the problems don't show up the first time, change the tags and then >>>>> re-apply. Over 2 or 3 cycles I always see both problems appear. >>>>> >>>>> I see this behaviour when 10 (or more) images are selected. I have not >>>>> seen it with only 1 or 2 images selected. I haven't checked in between. >>>>> >>>>> The problems appear random. A file which has a problem the first time >>>>> usually doesn't have it after tagging a second time. >>>>> >>>>> The problems appear to be independent, i.e. when writing metadata to >>>>> both sidecars and image files, they don't occur together, they affect >>>>> different images. >>>>> >>>>> Regards >>>>> Philip >>>>> _______________________________________________ >>>>> Digikam-users mailing list >>>>> [hidden email] >>>>> https://mail.kde.org/mailman/listinfo/digikam-users >>>> >>>> >>>> _______________________________________________ >>>> Digikam-users mailing list >>>> [hidden email] >>>> https://mail.kde.org/mailman/listinfo/digikam-users >>> >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >>> >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Tuckey-2
On 05/22/2014 08:28 PM, Phil wrote:
> On 22/05/14 14:27, maderios wrote: >> On 05/21/2014 05:57 PM, Phil wrote: >> >>> How do you force dk to only write xmp metadata? When I add a tag to an >>> image, dk writes it to 5 metadata fields, 4 of which are xmp but also >>> the IPTC Keywords field. Dk also writes various housekeeping information >>> to other IPTC fields. >> >> First, with Exiv2 tool (or an other one), I delete all unwanted tags >> from pictures >> http://www.exiv2.org/ >> Then in DK, I disable all tags management except xmp: >> - settings, configure DK >> - metadata >> - behaviour: I clear all except image tags, read & write sidecar files >> (write to image and xmp sidecar), update file timestamp..., >> - display: unselect/clear all (exif, iptc, makernotes, etc) except xmp >> viewer >> -xmpviewer: select all >> >> Dont forget kipi plugins-> metadataEdit > > Thanks. If I understand correctly, you say that the display settings > don't only control display of metadata in dk, but also have an effect on > which metadata dk writes to the image files? So with the above > configuration, dk doesn't write the image tags to an IPTC:Keywords field > in the image file? -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 22/05/14 21:28, maderios wrote:
> On 05/22/2014 08:28 PM, Phil wrote: >> On 22/05/14 14:27, maderios wrote: >>> On 05/21/2014 05:57 PM, Phil wrote: >>> >>>> How do you force dk to only write xmp metadata? When I add a tag to an >>>> image, dk writes it to 5 metadata fields, 4 of which are xmp but also >>>> the IPTC Keywords field. Dk also writes various housekeeping >>>> information >>>> to other IPTC fields. >>> >>> First, with Exiv2 tool (or an other one), I delete all unwanted tags >>> from pictures >>> http://www.exiv2.org/ >>> Then in DK, I disable all tags management except xmp: >>> - settings, configure DK >>> - metadata >>> - behaviour: I clear all except image tags, read & write sidecar files >>> (write to image and xmp sidecar), update file timestamp..., >>> - display: unselect/clear all (exif, iptc, makernotes, etc) except xmp >>> viewer >>> -xmpviewer: select all >>> >>> Dont forget kipi plugins-> metadataEdit >> >> Thanks. If I understand correctly, you say that the display settings >> don't only control display of metadata in dk, but also have an effect on >> which metadata dk writes to the image files? So with the above >> configuration, dk doesn't write the image tags to an IPTC:Keywords field >> in the image file? > I told you I use *only* xmp... I dont know anything about IPTC... My guess is that if you look at the image files themselves (using Exiv2 or exiftool) you will find that dk is in fact writing IPTC metadata to them, as well as XMP. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 05/22/2014 10:00 PM, Phil wrote:
> My guess is that if you look at the image files themselves (using Exiv2 > or exiftool) you will find that dk is in fact writing IPTC metadata to > them, as well as XMP Stop guessing, just do it... Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Tuckey-2
I am still looking for the source of the problem I meet when selecting
and tagging multiple images simultaneously - a small number of the xmp sidecars are truncated to just the first line, apparently randomly. I tried different versions of Exiv2 to see if that changes something. Dk 3.5.0 compiled with Exiv2 0.24, 0.23, 0.22 all show the same problem. Dk 4.0.0 with Exiv2 0.24 and 0.23 also show the same problem. (Dk 4.0.0 with Exiv2 0.22 doesn't write any sidecars because Exiv2 fails on the mwg-rs tags.) On 19/05/14 23:24, Phil wrote: > Hi > > I meet the following problems when tagging multiple images at the same > time, in both 4.0.0 and 4.1.0. I don't see this problem in a 3.3.0 which > I happen to have on another machine. Anyone else see this? > > How to generate: > Select 10 images. > Apply a tag to all. > > Problem 1, XMP metadata not always updated in image files: > When writing metadata to the image files, dk occasionally omits to write > the new XMP metadata, leaving the previous XMP metadata in the image > file. This can be seen by for example by tag fields not being updated > when tags are changed and applied. You have to look through the images > one-by-one to find one or two where this has happened. (The IPTC > metadata is always written correctly, so when this happens there is a > difference between the IPTC:Keywords (tags) field and the various XMP > tags fields.) > > Problem 2, xmp sidecars sometimes truncated: > Occasionally one or more of the xmp sidecars is truncated to just its > first line, with a size of only 39 bytes. (Use a file manager to see > that this has happened.) > > If the problems don't show up the first time, change the tags and then > re-apply. Over 2 or 3 cycles I always see both problems appear. > > I see this behaviour when 10 (or more) images are selected. I have not > seen it with only 1 or 2 images selected. I haven't checked in between. > > The problems appear random. A file which has a problem the first time > usually doesn't have it after tagging a second time. > > The problems appear to be independent, i.e. when writing metadata to > both sidecars and image files, they don't occur together, they affect > different images. > > Regards > Philip > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |