Same again: impossible to run Digikam 2.x
Locked
12
12
 
|
2011/12/15 Gilles Caulier <[hidden email]> --
Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
I would like to start a fresh DB from my albums. So I need to be sure that all metadata are actually written to the files.
But the operation is made impossible, as I keep getting this message for every image I'm trying to process: digikam(14212)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable: "/home/marie-noelle/Digikam/Photos/1 - Albums/2011 - Albums/11-01 Nîmes-le-Vieux/IMG_7247.jpg" The files exist and have reading/writing permissions: -rw-rw-r-- 1 marie-noelle marie-noelle 6539783 23 mai 2011 IMG_7247.jpg What have I to do to be able to write the metadata in the images? Marie-Noëlle Le 15 décembre 2011 16:34, Marie-Noëlle Augendre <[hidden email]> a écrit :
-- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Same again: impossible to run Digikam 2.x
|
|
Check you folder rights, not only the file...
Gilles Caulier 2011/12/16 Marie-Noëlle Augendre <[hidden email]>: > I would like to start a fresh DB from my albums. So I need to be sure that > all metadata are actually written to the files. > But the operation is made impossible, as I keep getting this message for > every image I'm trying to process: > digikam(14212)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder > does not exist or is not readable: "/home/marie-noelle/Digikam/Photos/1 - > Albums/2011 - Albums/11-01 Nîmes-le-Vieux/IMG_7247.jpg" > > The files exist and have reading/writing permissions: > -rw-rw-r-- 1 marie-noelle marie-noelle 6539783 23 mai 2011 IMG_7247.jpg > > What have I to do to be able to write the metadata in the images? > > Marie-Noëlle > > Le 15 décembre 2011 16:34, Marie-Noëlle Augendre <[hidden email]> a > écrit : > >> >> >> 2011/12/15 Gilles Caulier <[hidden email]> >>> >>> >>> yes, please report this on bugzilla for Francesco... >>> >>> Gilles >>> >> Done here https://bugs.kde.org/show_bug.cgi?id=277928#c12 >> >> Marie-Noëlle >> >> >> -- >> Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe >> >> Parcourez les Cévennes à ma façon : Cévennes Plurielles >> >> Et toutes mes autres publications à partir de ma page d'accueil générale >> > > > > -- > Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe > > Parcourez les Cévennes à ma façon : Cévennes Plurielles > > Et toutes mes autres publications à partir de ma page d'accueil générale > > > _______________________________________________ > 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 |
|
|
Almost of all of them have been created from inside Digikam (create album) and the folder rights are the following:
drwxr-xr-x 2 marie-noelle marie-noelle 4096 20 oct. 23:20 11-10 Boucle Mt Lozère Marie-Noëlle 2011/12/16 Gilles Caulier <[hidden email]> Check you folder rights, not only the file... -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by tosca
Well, I really don't understant these messages. Apparently, the metadata are actually written to the files: I can see them when I open a .jpg file in ShowFoto.
Same thing for this message, when I launch Digikam afresh (I've moved all the DB and configuration files elsewhere): "Le fichier de configuration /home/marie-noelle/.kde/share/config/digikamrc n'est pas inscriptible. Veuillez contacter votre administrateur système". When I click "OK" (there seems to be no other option), the process goes on and the .kde folder is normally created! So what is this message for? Marie-Noëlle 2011/12/16 Marie-Noëlle Augendre <[hidden email]> I would like to start a fresh DB from my albums. So I need to be sure that all metadata are actually written to the files. -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
I ended starting afresh with a new Digikam and rebuilt the whole DB from the images.
From what I understand, the DB got corrupted some time in the past, and DK wouldn't accept it for an upgrade. My feeling is that some tools or scripts for checking the integrity / rebuilding Digikam databases would be very valuable, especially before upgrades. My own 0.02 And I hope I won't any more problem like that in the foreseeable future. Marie-Noëlle 2011/12/16 Marie-Noëlle Augendre <[hidden email]> -- Well, I really don't understant these messages. Apparently, the metadata are actually written to the files: I can see them when I open a .jpg file in ShowFoto. Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Don't get the 35-mm-equivalent working
|
|
> Hello. > > When I use digikam with my DSLR, than there isn't any problem with the focal length in the meta data. I see something like "50 mm (35 mm: 75 mm)". > > However, now I have also a small compact camera. And when I use it, > digikam shows me "5 mm (35 mm: unknown)". How can I get this working? > Is this a problem of the EXIF data that the camera produces? If so, can > I fix this using digikam? If not: is it a problem of digikam? The camera > is Fujifilm Finepix XP 30. The manual claims the the focal length is > 5mm-25mm, which according to the manual corresponds to 28mm-140mm for > a 35-mm-film. > > Regards The 35mm film equivalent focal length is not a digital camera property but only an information that will help human minds (and photographers minds) to evaluate a focal length value, wide angle lens, normal angle, narrow angle lens (telelens) etc. Some digital cameras manufacturers write this info in the EXIF section of images files. Some don't write it as is but provide values about the CCD sensor of the camera, that will permit recomputation. And some metadata processing software use that. What is needed is the number of pixels of the sensor in both dimensions, usually "Focal plane image width" and ".. height", and the sensor resolution (the pixels density), usually "Focal plane X resolution" and "... Y resolution". Plus the geometrical units used for that resolution, property "Focal plane resolution units". (It can be centimetres or inches.) Given that, it's possible to recompute the geometrical dimensions of the image and compare to a standard 35mm film image, i.e. 24mm x 36mm. And this gives the focal length ratio. But when these informations are not available, and software just display "35mm equivalent: unknown", all what you need for a specific camera, i.e. a specific sensor, is the ratio information. On most cases it can be found in the technical data sheet of the camera, or the manufacturer web site, given the camera model. And you have this information, your "5mm-25mm" zoom corresponds to "28mm-140mm". This gives you a dimension ratio of 5.6 (5.6 is 25/5 or 140/25). And this is a fixed value for your camera, in all cases, whatever your zoom setup is; you just have to keep it in mind. So, if you take a shoot with your zoom at, say, 10mm, the equivalent focal length will be 56mm for a 35mm film; if your zoom is at 18mm, the 35mm equivalent length is 18*5.6 = 100mm. Etc. Regards, Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Same again: impossible to run Digikam 2.x
|
|
In reply to this post by tosca
On Fri, 16 Dec 2011, Marie-Noëlle Augendre wrote: > I ended starting afresh with a new Digikam and rebuilt the whole DB from the > images. > > From what I understand, the DB got corrupted some time in the past, and DK > wouldn't accept it for an upgrade. My feeling is that some tools or scripts > for checking the integrity / rebuilding Digikam databases would be very > valuable, especially before upgrades. Marie-Noëlle, apart from Digikam itself, you can check integrity of your SQLite DB via the sqlite3 command line tools, e.g. : sqlite3 digikam4.db 'pragma integrity_check;' If your database is corrupted (in a SQL way), sqlite3 will complain. If sqlite3 says your DB is fine, and Digikam complains after an upgrade, this may indicate the new versions has some slight modifications in its DB schema and compatibility isn't assumed. Anyway, a useful practice when upgrading DB applications, or DB management system, e.g. a newer version of the libqlite3, is to do export /import of the DB under SQL format. SQL format will be a text file with all required SQL commands to rebuild the whole DB. Thus, the operation is supposed to be independent of the binary internal representation of the DB. SQL export, before upgrade : sqlite3 digikam4.db .dump > dk-dump.sql SQL import, after upgrade : sqlite3 digikam4.db < dk-dump.sql Another advantage of doing such export /import, is that the export file will contain only pertinent data informations, not garbage, deleted images, etc. So, after import you're supposed to start with a fresh and clean DB. Regards, Jean-François NB: same kind of operation, SQL export, SQL import, can be done with any RDBMS, SQLite3 of course, but also Oracle, MySQL, PostgreSQL. One has just to check proper syntax in the RDBMS manual. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Thank you for this information.
Digikam is the only SQLite-based program I use; I'm much more at ease with MySQL that I use with many other programs. However, I would very much like not to need to learn the commands for each language (regarding Digikam, I'm an "end-user"). In Piwigo for example, the interface provides a simple menu option to check and/or repair the database, so that the user can run it as often as he wants too, without having to look for commands syntax he'll only use a couple of times a year. I think this kind of function will be a very useful addition to Digikam. So not every photograph using Linux will need to become some DB specialist. Marie-Noëlle 2011/12/17 Jean-François Rabasse <[hidden email]>
-- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ 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 |