1.6 svn matter when metadata are modified outside of Digikam

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

1.6 svn matter when metadata are modified outside of Digikam

Nicolas B.

Hi,

I just notice something annoying with Digikam. First of all I think the  
matter came from CaptureNX, but it seems now, that Digikam is the source  
of this matter.

I use Digikam svn version (updated today) with Ubuntu 10.10 64 bits. Here  
are the details :


digiKam version 1.6.0 (rev.: 1196931)
Dématriçage parallélisé: Oui
Exiv2 peut écrire dans un fichier JP2: Oui
Exiv2 peut écrire dans un fichier JPEG: Oui
Exiv2 peut écrire dans un fichier PGF: Non
Exiv2 peut écrire dans un fichier PNG: Oui
Exiv2 peut écrire dans un fichier TIFF: Oui
Exiv2 prend en charge les métadonnées XMP: Oui
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.19
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.5.1 (KDE 4.5.1)
LibKExiv2: 1.2.0
LibKdcraw: 1.2.0
LibLCMS: 118
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.09.44 - internal library
LibPNG: 1.2.44
LibQt: 4.7.0
LibRaw: 0.11.2
LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler  
Copyright (c) 1991-1996 Silicon Graphics, Inc.
Élément graphique Marble: 0.10.1
LibGphoto2: 2.4.8
LibKipi: 1.2.0
Moteur de base de données: QSQLITE


In fact, I edited some pictures with CaptureNX (under Virtualbox and a  
Digikam collection as a shared folder) after rating them with Digikam with  
in mind to only working on best ones.

When I was working, I changed my mind about one picture, and add a rating  
to it, but when I'm going back in Digikam, the change has been viewed by  
Digikam since Digikam update its thumbnail, but the rating was not updated.

What let me think that Digikam is responsible here, is if I'm going in  
"Image" menu and choosing "Lire à nouveau les métadonnées à partir de  
l'image" (read once again metadatas from the image or something like that  
in english), then, the rating appear correctly. After testing, it is the  
same thing for some other metadata like keywords.

I check the option at the first start for Digikam to "scan for new item at  
start up", but apparently, modifications are viewed (thumbnail update),  
but metadatas are not rescanned.

Is there anybody else experienced this ? Is there something I missed ?

Thanks

Regards,

Nicolas

--
Nicolas Boulesteix
Photographe chasseur de lueurs
http://www.photonoxx.fr

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Fwd: 1.6 svn matter when metadata are modified outside of Digikam

Photonoxx
Sorry, I didn't notice I used the wrong mail account... I don't know if  
it's possible to cancel the first one (from nicolas boulesteix at  
laposte.net).

I repost with the good email account.

------- Message réexpédié-------
De:
A:
Sujet:
Date: Sun, 14 Nov 2010 17:25:00 +0100

Hi,

I just notice something annoying with Digikam. First of all I think the
matter came from CaptureNX, but it seems now, that Digikam is the source
of this matter.

I use Digikam svn version (updated today) with Ubuntu 10.10 64 bits. Here
are the details :


digiKam version 1.6.0 (rev.: 1196931)
Dématriçage parallélisé: Oui
Exiv2 peut écrire dans un fichier JP2: Oui
Exiv2 peut écrire dans un fichier JPEG: Oui
Exiv2 peut écrire dans un fichier PGF: Non
Exiv2 peut écrire dans un fichier PNG: Oui
Exiv2 peut écrire dans un fichier TIFF: Oui
Exiv2 prend en charge les métadonnées XMP: Oui
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.19
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.5.1 (KDE 4.5.1)
LibKExiv2: 1.2.0
LibKdcraw: 1.2.0
LibLCMS: 118
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.09.44 - internal library
LibPNG: 1.2.44
LibQt: 4.7.0
LibRaw: 0.11.2
LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.
Élément graphique Marble: 0.10.1
LibGphoto2: 2.4.8
LibKipi: 1.2.0
Moteur de base de données: QSQLITE


In fact, I edited some pictures with CaptureNX (under Virtualbox and a
Digikam collection as a shared folder) after rating them with Digikam with
in mind to only working on best ones.

When I was working, I changed my mind about one picture, and add a rating
to it, but when I'm going back in Digikam, the change has been viewed by
Digikam since Digikam update its thumbnail, but the rating was not updated.

What let me think that Digikam is responsible here, is if I'm going in
"Image" menu and choosing "Lire à nouveau les métadonnées à partir de
l'image" (read once again metadatas from the image or something like that
in english), then, the rating appear correctly. After testing, it is the
same thing for some other metadata like keywords.

I check the option at the first start for Digikam to "scan for new item at
start up", but apparently, modifications are viewed (thumbnail update),
but metadatas are not rescanned.

Is there anybody else experienced this ? Is there something I missed ?

Thanks

Regards,

Nicolas


--
--
Nicolas Boulesteix
Photographe chasseur de lueurs
http://www.photonoxx.fr
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: 1.6 svn matter when metadata are modified outside of Digikam

Photonoxx
No idea about that ?

Le Sun, 14 Nov 2010 17:30:49 +0100, Photonoxx <[hidden email]> a écrit:>

> Hi,
>
> I just notice something annoying with Digikam. First of all I think the
> matter came from CaptureNX, but it seems now, that Digikam is the source
> of this matter.
>
> I use Digikam svn version (updated today) with Ubuntu 10.10 64 bits. Here
> are the details :
>
>
> digiKam version 1.6.0 (rev.: 1196931)
> Dématriçage parallélisé: Oui
> Exiv2 peut écrire dans un fichier JP2: Oui
> Exiv2 peut écrire dans un fichier JPEG: Oui
> Exiv2 peut écrire dans un fichier PGF: Non
> Exiv2 peut écrire dans un fichier PNG: Oui
> Exiv2 peut écrire dans un fichier TIFF: Oui
> Exiv2 prend en charge les métadonnées XMP: Oui
> LibCImg: 130
> LibClapack: internal library
> LibExiv2: 0.19
> LibJPEG: 62
> LibJasper: 1.900.1
> LibKDE: 4.5.1 (KDE 4.5.1)
> LibKExiv2: 1.2.0
> LibKdcraw: 1.2.0
> LibLCMS: 118
> LibLensFun: external shared library
> LibLqr: internal library
> LibPGF: 6.09.44 - internal library
> LibPNG: 1.2.44
> LibQt: 4.7.0
> LibRaw: 0.11.2
> LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler
> Copyright (c) 1991-1996 Silicon Graphics, Inc.
> Élément graphique Marble: 0.10.1
> LibGphoto2: 2.4.8
> LibKipi: 1.2.0
> Moteur de base de données: QSQLITE
>
>
> In fact, I edited some pictures with CaptureNX (under Virtualbox and a
> Digikam collection as a shared folder) after rating them with Digikam  
> with
> in mind to only working on best ones.
>
> When I was working, I changed my mind about one picture, and add a rating
> to it, but when I'm going back in Digikam, the change has been viewed by
> Digikam since Digikam update its thumbnail, but the rating was not  
> updated.
>
> What let me think that Digikam is responsible here, is if I'm going in
> "Image" menu and choosing "Lire à nouveau les métadonnées à partir de
> l'image" (read once again metadatas from the image or something like that
> in english), then, the rating appear correctly. After testing, it is the
> same thing for some other metadata like keywords.
>
> I check the option at the first start for Digikam to "scan for new item  
> at
> start up", but apparently, modifications are viewed (thumbnail update),
> but metadatas are not rescanned.
>
> Is there anybody else experienced this ? Is there something I missed ?
>
> Thanks
>
> Regards,
>
> Nicolas
>
>


--
--
Nicolas Boulesteix
Photographe chasseur de lueurs
http://www.photonoxx.fr
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users