digiKam 3.5.0 import/rename not working as expected
Locked
digiKam 3.5.0 import/rename not working as expected
 
|
Hi,
recently digiKam 3.5.0 has been marked stable in Gentoo so I updated from digiKam 3.2.0. But after that importing photos didn't work any longer as expected. All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been imported at all. Playing a little bit around I've some workarounds: - Importing AVIs works if I disable the date base folder creating option, but filenames are "-1.avi", "-2.avi"... - Filenames are OK if I change the rename mask from "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to "[date:yyyy-MM-dd_HHmmss]" Both is not what I want to change. I always want to use the date when the photo has been taken. By using [date] I'm not sure if it's the creation date or the last modification date. But I have the strong feeling it's the later one, so I try to avoid using it. While looking at the rename mask I saw that there must have been a change from [meta:Exif.Image.DateTimeOriginal] to [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected digiKam to automagically change my rename mask. But both ways the modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the wrong way? Best regards, Andreas === My digiKam component informations === digiKam version 3.5.0 Exiv2 kann in JP2 speichern: Ja Exiv2 kann in JPEG speichern: Ja Exiv2 kann in PGF speichern: Ja Exiv2 kann in PNG speichern: Ja Exiv2 kann in TIFF speichern: Ja Exiv2 unterstützt XMP-Metadaten: Ja LibCImg: 130 LibEigen: 3.0.6 LibExiv2: 0.23 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.11.2 LibKExiv2: 2.3.1 LibKGeoMap: 2.0.0 LibKdcraw: 2.3.1 LibLCMS: 2050 LibLensFun: 0.2.7-0 LibPGF: 6.12.27 - Externe gemeinsame Bibliothek LibPNG: 1.6.8 LibQt: 4.8.5 LibRaw: 0.15.4 LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble-Funktion: 0.16.2 (stable version) Parallelisierte PGF-Codecs: Keine Parallelisiertes Entfernen von Mosaikmustern: Ja RawSpeed codec support: Keine Datenbanktreiber: QSQLITE KIPI-Module: 3.5.0 LibKface: 3.0.0 LibKipi: 2.1.0 LibOpenCV: 2.4.5 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
This feature must be fixed in last 4.0.0-beta2 release published one
month ago... Gilles Caulier 2014-02-08 10:52 GMT+01:00 Andreas Mair <[hidden email]>: > Hi, > > recently digiKam 3.5.0 has been marked stable in Gentoo so I updated > from digiKam 3.2.0. > But after that importing photos didn't work any longer as expected. > All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been > imported at all. > > Playing a little bit around I've some workarounds: > - Importing AVIs works if I disable the date base folder creating > option, but filenames are "-1.avi", "-2.avi"... > - Filenames are OK if I change the rename mask from > "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to > "[date:yyyy-MM-dd_HHmmss]" > > Both is not what I want to change. I always want to use the date when > the photo has been taken. By using [date] I'm not sure if it's the > creation date or the last modification date. But I have the strong > feeling it's the later one, so I try to avoid using it. > > While looking at the rename mask I saw that there must have been a > change from [meta:Exif.Image.DateTimeOriginal] to > [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected > digiKam to automagically change my rename mask. But both ways the > modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the > wrong way? > > Best regards, > Andreas > > > === My digiKam component informations === > digiKam version 3.5.0 > Exiv2 kann in JP2 speichern: Ja > Exiv2 kann in JPEG speichern: Ja > Exiv2 kann in PGF speichern: Ja > Exiv2 kann in PNG speichern: Ja > Exiv2 kann in TIFF speichern: Ja > Exiv2 unterstützt XMP-Metadaten: Ja > LibCImg: 130 > LibEigen: 3.0.6 > LibExiv2: 0.23 > LibJPEG: 62 > LibJasper: 1.900.1 > LibKDE: 4.11.2 > LibKExiv2: 2.3.1 > LibKGeoMap: 2.0.0 > LibKdcraw: 2.3.1 > LibLCMS: 2050 > LibLensFun: 0.2.7-0 > LibPGF: 6.12.27 - Externe gemeinsame Bibliothek > LibPNG: 1.6.8 > LibQt: 4.8.5 > LibRaw: 0.15.4 > LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler > Copyright (c) 1991-1996 Silicon Graphics, Inc. > Marble-Funktion: 0.16.2 (stable version) > Parallelisierte PGF-Codecs: Keine > Parallelisiertes Entfernen von Mosaikmustern: Ja > RawSpeed codec support: Keine > Datenbanktreiber: QSQLITE > KIPI-Module: 3.5.0 > LibKface: 3.0.0 > LibKipi: 2.1.0 > LibOpenCV: 2.4.5 > _______________________________________________ > 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 Andreas Mair-2
I run DK 3.5.0 on openSUSE
I use the import rename mask
On 02/08/2014 04:52 AM, Andreas Mair
wrote:
Hi, recently digiKam 3.5.0 has been marked stable in Gentoo so I updated from digiKam 3.2.0. But after that importing photos didn't work any longer as expected. All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been imported at all. Playing a little bit around I've some workarounds: - Importing AVIs works if I disable the date base folder creating option, but filenames are "-1.avi", "-2.avi"... - Filenames are OK if I change the rename mask from "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to "[date:yyyy-MM-dd_HHmmss]" Both is not what I want to change. I always want to use the date when the photo has been taken. By using [date] I'm not sure if it's the creation date or the last modification date. But I have the strong feeling it's the later one, so I try to avoid using it. While looking at the rename mask I saw that there must have been a change from [meta:Exif.Image.DateTimeOriginal] to [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected digiKam to automagically change my rename mask. But both ways the modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the wrong way? Best regards, Andreas === My digiKam component informations === digiKam version 3.5.0 Exiv2 kann in JP2 speichern: Ja Exiv2 kann in JPEG speichern: Ja Exiv2 kann in PGF speichern: Ja Exiv2 kann in PNG speichern: Ja Exiv2 kann in TIFF speichern: Ja Exiv2 unterstützt XMP-Metadaten: Ja LibCImg: 130 LibEigen: 3.0.6 LibExiv2: 0.23 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.11.2 LibKExiv2: 2.3.1 LibKGeoMap: 2.0.0 LibKdcraw: 2.3.1 LibLCMS: 2050 LibLensFun: 0.2.7-0 LibPGF: 6.12.27 - Externe gemeinsame Bibliothek LibPNG: 1.6.8 LibQt: 4.8.5 LibRaw: 0.15.4 LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble-Funktion: 0.16.2 (stable version) Parallelisierte PGF-Codecs: Keine Parallelisiertes Entfernen von Mosaikmustern: Ja RawSpeed codec support: Keine Datenbanktreiber: QSQLITE KIPI-Module: 3.5.0 LibKface: 3.0.0 LibKipi: 2.1.0 LibOpenCV: 2.4.5 _______________________________________________ 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 |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
In reply to this post by Gilles Caulier-4
Hi Gilles,
you suggest to use a beta release? No go! First it's not (yet) in Gentoo, second I don't trust digiKam betas because IHMO digiKam finals often have features not working as expected and I don't think betas will do better :-( Don't get me wrong: I really don't want to rant, I really loved the rock solid digiKam <2.0, but starting with digiKam 2.0 I've always had problems with this or that feature. For example renaming at imports didn't work for me since 3.2.0 (release 2013-05-15). With 4.0.0 coming in May this year this means a full year with a broken feature. Best wishes for a (hopefully) glorious release 4.0, Andreas 2014-02-08 14:20 GMT+01:00 Gilles Caulier <[hidden email]>: > This feature must be fixed in last 4.0.0-beta2 release published one > month ago... > > Gilles Caulier > > 2014-02-08 10:52 GMT+01:00 Andreas Mair <[hidden email]>: >> Hi, >> >> recently digiKam 3.5.0 has been marked stable in Gentoo so I updated >> from digiKam 3.2.0. >> But after that importing photos didn't work any longer as expected. >> All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been >> imported at all. >> >> Playing a little bit around I've some workarounds: >> - Importing AVIs works if I disable the date base folder creating >> option, but filenames are "-1.avi", "-2.avi"... >> - Filenames are OK if I change the rename mask from >> "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to >> "[date:yyyy-MM-dd_HHmmss]" >> >> Both is not what I want to change. I always want to use the date when >> the photo has been taken. By using [date] I'm not sure if it's the >> creation date or the last modification date. But I have the strong >> feeling it's the later one, so I try to avoid using it. >> >> While looking at the rename mask I saw that there must have been a >> change from [meta:Exif.Image.DateTimeOriginal] to >> [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected >> digiKam to automagically change my rename mask. But both ways the >> modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the >> wrong way? >> >> Best regards, >> Andreas >> >> >> === My digiKam component informations === >> digiKam version 3.5.0 >> Exiv2 kann in JP2 speichern: Ja >> Exiv2 kann in JPEG speichern: Ja >> Exiv2 kann in PGF speichern: Ja >> Exiv2 kann in PNG speichern: Ja >> Exiv2 kann in TIFF speichern: Ja >> Exiv2 unterstützt XMP-Metadaten: Ja >> LibCImg: 130 >> LibEigen: 3.0.6 >> LibExiv2: 0.23 >> LibJPEG: 62 >> LibJasper: 1.900.1 >> LibKDE: 4.11.2 >> LibKExiv2: 2.3.1 >> LibKGeoMap: 2.0.0 >> LibKdcraw: 2.3.1 >> LibLCMS: 2050 >> LibLensFun: 0.2.7-0 >> LibPGF: 6.12.27 - Externe gemeinsame Bibliothek >> LibPNG: 1.6.8 >> LibQt: 4.8.5 >> LibRaw: 0.15.4 >> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler >> Copyright (c) 1991-1996 Silicon Graphics, Inc. >> Marble-Funktion: 0.16.2 (stable version) >> Parallelisierte PGF-Codecs: Keine >> Parallelisiertes Entfernen von Mosaikmustern: Ja >> RawSpeed codec support: Keine >> Datenbanktreiber: QSQLITE >> KIPI-Module: 3.5.0 >> LibKface: 3.0.0 >> LibKipi: 2.1.0 >> LibOpenCV: 2.4.5 >> _______________________________________________ >> 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 |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
In reply to this post by Andreas Mair-2
2014-02-08 17:22 GMT+01:00 Andreas Mair <[hidden email]>:
> Hi Gilles, > > you suggest to use a beta release? > No go! First it's not (yet) in Gentoo, second I don't trust digiKam > betas because IHMO digiKam finals often have features not working as > expected and I don't think betas will do better :-( > > Don't get me wrong: > I really don't want to rant, I really loved the rock solid digiKam > <2.0, but starting with digiKam 2.0 I've always had problems with this > or that feature. For example renaming at imports didn't work for me > since 3.2.0 (release 2013-05-15). With 4.0.0 coming in May this year > this means a full year with a broken feature. A lots of previous features are restored now. Just take a look to current list of bugzilla files closed : https://bugs.kde.org/buglist.cgi?f1=cf_versionfixedin&o1=equals&query_format=advanced&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&v1=4.0.0&product=digikam&product=digikamimageplugins&product=kipiplugins&product=showfoto&list_id=927158 Why we wait more time with 4.0.0 : because we want a good release... Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
In reply to this post by Gilles Caulier-4
Hi,
maybe Andreas' bug is this one: https://bugs.kde.org/show_bug.cgi?id=314441 "Rename settings and auto-rotation during import ignored" It is not marked as "fixed", so I guess it is not fixed in 4.0.0-beta2. But I can't test it, since there is no gentoo ebuild for digikam-4.0.0-beta2. BTW: The bug's "version" attribut might be updated from "3.3.0" to "3.5.0". Regards, Peter Albrecht On 08.02.2014 14:20, Gilles Caulier wrote: > This feature must be fixed in last 4.0.0-beta2 release published one > month ago... > > Gilles Caulier > > 2014-02-08 10:52 GMT+01:00 Andreas Mair <[hidden email]>: >> Hi, >> >> recently digiKam 3.5.0 has been marked stable in Gentoo so I updated >> from digiKam 3.2.0. >> But after that importing photos didn't work any longer as expected. >> All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been >> imported at all. >> >> Playing a little bit around I've some workarounds: >> - Importing AVIs works if I disable the date base folder creating >> option, but filenames are "-1.avi", "-2.avi"... >> - Filenames are OK if I change the rename mask from >> "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to >> "[date:yyyy-MM-dd_HHmmss]" >> >> Both is not what I want to change. I always want to use the date when >> the photo has been taken. By using [date] I'm not sure if it's the >> creation date or the last modification date. But I have the strong >> feeling it's the later one, so I try to avoid using it. >> >> While looking at the rename mask I saw that there must have been a >> change from [meta:Exif.Image.DateTimeOriginal] to >> [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected >> digiKam to automagically change my rename mask. But both ways the >> modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the >> wrong way? >> >> Best regards, >> Andreas >> >> >> === My digiKam component informations === >> digiKam version 3.5.0 >> Exiv2 kann in JP2 speichern: Ja >> Exiv2 kann in JPEG speichern: Ja >> Exiv2 kann in PGF speichern: Ja >> Exiv2 kann in PNG speichern: Ja >> Exiv2 kann in TIFF speichern: Ja >> Exiv2 unterstützt XMP-Metadaten: Ja >> LibCImg: 130 >> LibEigen: 3.0.6 >> LibExiv2: 0.23 >> LibJPEG: 62 >> LibJasper: 1.900.1 >> LibKDE: 4.11.2 >> LibKExiv2: 2.3.1 >> LibKGeoMap: 2.0.0 >> LibKdcraw: 2.3.1 >> LibLCMS: 2050 >> LibLensFun: 0.2.7-0 >> LibPGF: 6.12.27 - Externe gemeinsame Bibliothek >> LibPNG: 1.6.8 >> LibQt: 4.8.5 >> LibRaw: 0.15.4 >> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler >> Copyright (c) 1991-1996 Silicon Graphics, Inc. >> Marble-Funktion: 0.16.2 (stable version) >> Parallelisierte PGF-Codecs: Keine >> Parallelisiertes Entfernen von Mosaikmustern: Ja >> RawSpeed codec support: Keine >> Datenbanktreiber: QSQLITE >> KIPI-Module: 3.5.0 >> LibKface: 3.0.0 >> LibKipi: 2.1.0 >> LibOpenCV: 2.4.5 >> _______________________________________________ >> 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 |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
2014-02-10 19:34 GMT+01:00 Peter Albrecht <[hidden email]>:
> Hi, > > maybe Andreas' bug is this one: > https://bugs.kde.org/show_bug.cgi?id=314441 > "Rename settings and auto-rotation during import ignored" > > It is not marked as "fixed", so I guess it is not fixed in > 4.0.0-beta2. But I can't test it, since there is no gentoo > ebuild for digikam-4.0.0-beta2. > > BTW: The bug's "version" attribut might be updated from > "3.3.0" to "3.5.0". Done... Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
In reply to this post by Peter Albrecht
Hi Peter,
bug 314441 might be the reason in case of imports. But I'm also talking about the rename feature. My problem is that the rename pattern "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" no longer works. The first problem is that I now must replace "...Exif.Image..." by "...Exif.Photo...". After that I can use "[meta:Exif.Photo.DateTimeOriginal]". But I want to change the date format to my needs and this seems to be impossible now. If I use "[date:yyyy-MM-dd_HHmmss]" it works, but not "[meta:Exif.Photo.DateTimeOriginal:yyyy-MM-dd_HHmmss]". Can anybody test this with digiKam 4.0beta? Best regards, Andreas 2014-02-10 19:34 GMT+01:00 Peter Albrecht <[hidden email]>: > Hi, > > maybe Andreas' bug is this one: > https://bugs.kde.org/show_bug.cgi?id=314441 > "Rename settings and auto-rotation during import ignored" > > It is not marked as "fixed", so I guess it is not fixed in > 4.0.0-beta2. But I can't test it, since there is no gentoo > ebuild for digikam-4.0.0-beta2. > > BTW: The bug's "version" attribut might be updated from > "3.3.0" to "3.5.0". > > Regards, > Peter Albrecht > > On 08.02.2014 14:20, Gilles Caulier wrote: >> This feature must be fixed in last 4.0.0-beta2 release published one >> month ago... >> >> Gilles Caulier >> >> 2014-02-08 10:52 GMT+01:00 Andreas Mair <[hidden email]>: >>> Hi, >>> >>> recently digiKam 3.5.0 has been marked stable in Gentoo so I updated >>> from digiKam 3.2.0. >>> But after that importing photos didn't work any longer as expected. >>> All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been >>> imported at all. >>> >>> Playing a little bit around I've some workarounds: >>> - Importing AVIs works if I disable the date base folder creating >>> option, but filenames are "-1.avi", "-2.avi"... >>> - Filenames are OK if I change the rename mask from >>> "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to >>> "[date:yyyy-MM-dd_HHmmss]" >>> >>> Both is not what I want to change. I always want to use the date when >>> the photo has been taken. By using [date] I'm not sure if it's the >>> creation date or the last modification date. But I have the strong >>> feeling it's the later one, so I try to avoid using it. >>> >>> While looking at the rename mask I saw that there must have been a >>> change from [meta:Exif.Image.DateTimeOriginal] to >>> [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected >>> digiKam to automagically change my rename mask. But both ways the >>> modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the >>> wrong way? >>> >>> Best regards, >>> Andreas >>> >>> >>> === My digiKam component informations === >>> digiKam version 3.5.0 >>> Exiv2 kann in JP2 speichern: Ja >>> Exiv2 kann in JPEG speichern: Ja >>> Exiv2 kann in PGF speichern: Ja >>> Exiv2 kann in PNG speichern: Ja >>> Exiv2 kann in TIFF speichern: Ja >>> Exiv2 unterstützt XMP-Metadaten: Ja >>> LibCImg: 130 >>> LibEigen: 3.0.6 >>> LibExiv2: 0.23 >>> LibJPEG: 62 >>> LibJasper: 1.900.1 >>> LibKDE: 4.11.2 >>> LibKExiv2: 2.3.1 >>> LibKGeoMap: 2.0.0 >>> LibKdcraw: 2.3.1 >>> LibLCMS: 2050 >>> LibLensFun: 0.2.7-0 >>> LibPGF: 6.12.27 - Externe gemeinsame Bibliothek >>> LibPNG: 1.6.8 >>> LibQt: 4.8.5 >>> LibRaw: 0.15.4 >>> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler >>> Copyright (c) 1991-1996 Silicon Graphics, Inc. >>> Marble-Funktion: 0.16.2 (stable version) >>> Parallelisierte PGF-Codecs: Keine >>> Parallelisiertes Entfernen von Mosaikmustern: Ja >>> RawSpeed codec support: Keine >>> Datenbanktreiber: QSQLITE >>> KIPI-Module: 3.5.0 >>> LibKface: 3.0.0 >>> LibKipi: 2.1.0 >>> LibOpenCV: 2.4.5 >>> _______________________________________________ >>> 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 |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
In reply to this post by Gilles Caulier-4
On 10.02.2014 20:31, Gilles Caulier wrote:
> 2014-02-10 19:34 GMT+01:00 Peter Albrecht <[hidden email]>: >> maybe Andreas' bug is this one: >> https://bugs.kde.org/show_bug.cgi?id=314441 >> "Rename settings and auto-rotation during import ignored" >> ... >> BTW: The bug's "version" attribut might be updated from >> "3.3.0" to "3.5.0". > > Done... > Thanks :) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digiKam 3.5.0 import/rename not working as expected
|
|
In reply to this post by Andreas Mair-2
Hi,
2014-02-11 12:17 GMT+01:00 Andreas Mair <[hidden email]>: > Hi Peter, > > bug 314441 might be the reason in case of imports. But I'm also > talking about the rename feature. > > My problem is that the rename pattern > "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" no longer > works. The first problem is that I now must replace "...Exif.Image..." > by "...Exif.Photo...". After that I can use > "[meta:Exif.Photo.DateTimeOriginal]". > > But I want to change the date format to my needs and this seems to be > impossible now. If I use "[date:yyyy-MM-dd_HHmmss]" it works, but not > "[meta:Exif.Photo.DateTimeOriginal:yyyy-MM-dd_HHmmss]". > > Can anybody test this with digiKam 4.0beta? I've now tried the renamer in v4.0beta2 and "[meta:Exif.Photo.DateTimeOriginal:yyyy-MM-dd_HHmmss]" doesn't work. Let's hope it will be fixed in 4.0 final. Best regards, Andreas > 2014-02-10 19:34 GMT+01:00 Peter Albrecht <[hidden email]>: >> Hi, >> >> maybe Andreas' bug is this one: >> https://bugs.kde.org/show_bug.cgi?id=314441 >> "Rename settings and auto-rotation during import ignored" >> >> It is not marked as "fixed", so I guess it is not fixed in >> 4.0.0-beta2. But I can't test it, since there is no gentoo >> ebuild for digikam-4.0.0-beta2. >> >> BTW: The bug's "version" attribut might be updated from >> "3.3.0" to "3.5.0". >> >> Regards, >> Peter Albrecht >> >> On 08.02.2014 14:20, Gilles Caulier wrote: >>> This feature must be fixed in last 4.0.0-beta2 release published one >>> month ago... >>> >>> Gilles Caulier >>> >>> 2014-02-08 10:52 GMT+01:00 Andreas Mair <[hidden email]>: >>>> Hi, >>>> >>>> recently digiKam 3.5.0 has been marked stable in Gentoo so I updated >>>> from digiKam 3.2.0. >>>> But after that importing photos didn't work any longer as expected. >>>> All images are named "-1.jpg", "-2.jpg", "-3.jpg"... AVIs haven't been >>>> imported at all. >>>> >>>> Playing a little bit around I've some workarounds: >>>> - Importing AVIs works if I disable the date base folder creating >>>> option, but filenames are "-1.avi", "-2.avi"... >>>> - Filenames are OK if I change the rename mask from >>>> "[meta:Exif.Image.DateTimeOriginal:yyyy-MM-dd_HHmmss]" to >>>> "[date:yyyy-MM-dd_HHmmss]" >>>> >>>> Both is not what I want to change. I always want to use the date when >>>> the photo has been taken. By using [date] I'm not sure if it's the >>>> creation date or the last modification date. But I have the strong >>>> feeling it's the later one, so I try to avoid using it. >>>> >>>> While looking at the rename mask I saw that there must have been a >>>> change from [meta:Exif.Image.DateTimeOriginal] to >>>> [meta:Exif.Photo.DateTimeOriginal]. If that's true I'd expected >>>> digiKam to automagically change my rename mask. But both ways the >>>> modifier "yyyy-MM-dd_HHmmss" doesn't work. Bug? Or do I use it the >>>> wrong way? >>>> >>>> Best regards, >>>> Andreas >>>> >>>> >>>> === My digiKam component informations === >>>> digiKam version 3.5.0 >>>> Exiv2 kann in JP2 speichern: Ja >>>> Exiv2 kann in JPEG speichern: Ja >>>> Exiv2 kann in PGF speichern: Ja >>>> Exiv2 kann in PNG speichern: Ja >>>> Exiv2 kann in TIFF speichern: Ja >>>> Exiv2 unterstützt XMP-Metadaten: Ja >>>> LibCImg: 130 >>>> LibEigen: 3.0.6 >>>> LibExiv2: 0.23 >>>> LibJPEG: 62 >>>> LibJasper: 1.900.1 >>>> LibKDE: 4.11.2 >>>> LibKExiv2: 2.3.1 >>>> LibKGeoMap: 2.0.0 >>>> LibKdcraw: 2.3.1 >>>> LibLCMS: 2050 >>>> LibLensFun: 0.2.7-0 >>>> LibPGF: 6.12.27 - Externe gemeinsame Bibliothek >>>> LibPNG: 1.6.8 >>>> LibQt: 4.8.5 >>>> LibRaw: 0.15.4 >>>> LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler >>>> Copyright (c) 1991-1996 Silicon Graphics, Inc. >>>> Marble-Funktion: 0.16.2 (stable version) >>>> Parallelisierte PGF-Codecs: Keine >>>> Parallelisiertes Entfernen von Mosaikmustern: Ja >>>> RawSpeed codec support: Keine >>>> Datenbanktreiber: QSQLITE >>>> KIPI-Module: 3.5.0 >>>> LibKface: 3.0.0 >>>> LibKipi: 2.1.0 >>>> LibOpenCV: 2.4.5 >>>> _______________________________________________ >>>> 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 |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |