Save metadata to files not working

[Ben Staude]

Hello,

I'm using digikam 1.2.0 (kubuntu lucid). I'm trying to save image metadata to
the image files (right sidebar -> more -> save metadata to all files or Album
-> save metadata to files). This is not working (images on disk are left
unchanged), and digikam says "Digikam::CollectionScanner::scanAlbum: Folder
does not exist or is not readable: <path to file>" for every file. The paths
are correct, and the files are read-/writeable for me. What's wrong here?

Thanks,
Ben
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Micha Neubauer]

Hello Ben,

did you check about your permissions for the files? ;-)
Of course you must have wright access.

bye
micha

On Friday 22 October 2010, 03:10:29 Ben Staude wrote:

> Hello,
>
> I'm using digikam 1.2.0 (kubuntu lucid). I'm trying to save image metadata
> to the image files (right sidebar -> more -> save metadata to all files or
> Album -> save metadata to files). This is not working (images on disk are
> left unchanged), and digikam says "Digikam::CollectionScanner::scanAlbum:
> Folder does not exist or is not readable: <path to file>" for every file.
> The paths are correct, and the files are read-/writeable for me. What's
> wrong here?
>
> Thanks,
> Ben
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

__________________________________________________

Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com 

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Ben Staude]

Hi again,

> I'm using digikam 1.2.0 (kubuntu lucid). I'm trying to save image metadata
> to the image files (right sidebar -> more -> save metadata to all files or
> Album -> save metadata to files). This is not working (images on disk are
> left unchanged), and digikam says "Digikam::CollectionScanner::scanAlbum:
> Folder does not exist or is not readable: <path to file>" for every file.
> The paths are correct, and the files are read-/writeable for me. What's
> wrong here?

While double checking the permissions again (they're definitely ok), I found
out that - despite the warning/error message - the metadata *is* actually
being written into the image file, but the files modification timestamp is not
being updated (I guess this is not a bug, but a feature..??).

Still confused by the warning/error message, I found out that once I
edit/modify and save one image in the album (F4), digiKam somehow does/gets a
filesystem update and doesn't print the warning/error message any more, even
when metadata of another image in the album is changed!?

BTW, the files timestamp is updated after modify+save in the image editor
which, for me, is only partially consistent with the metadata behaviour
mentioned above.

I hope I was able to describe my observations clearly enough and you can make
sense of it (or verify it against the intended behaviour)?

Ben

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Montag, 25. Oktober 2010 schrieb Ben Staude:

> Hi again,
>
> > I'm using digikam 1.2.0 (kubuntu lucid). I'm trying to save image
> > metadata to the image files (right sidebar -> more -> save
> > metadata to all files or Album -> save metadata to files). This
> > is not working (images on disk are left unchanged), and digikam
> > says "Digikam::CollectionScanner::scanAlbum: Folder does not
> > exist or is not readable: <path to file>" for every file. The
> > paths are correct, and the files are read-/writeable for me.
> > What's wrong here?
>
> While double checking the permissions again (they're definitely
> ok), I found out that - despite the warning/error message - the
> metadata *is* actually being written into the image file, but the
> files modification timestamp is not being updated (I guess this is
> not a bug, but a feature..??).

It is a feature. You can enable timestamp update in the configuration
dialogue (metadata) and there in the first tab (Verhalten in german).

>
> Still confused by the warning/error message, I found out that once
> I edit/modify and save one image in the album (F4), digiKam
> somehow does/gets a filesystem update and doesn't print the
> warning/error message any more, even when metadata of another
> image in the album is changed!?
>
> BTW, the files timestamp is updated after modify+save in the image
> editor which, for me, is only partially consistent with the
> metadata behaviour mentioned above.

The image editor (showfoto) is different. If you hit save, the whole
image is written to the hard disk. In main digikam only the metadata
is updated. The image data is untouched.

>
> I hope I was able to describe my observations clearly enough and
> you can make sense of it (or verify it against the intended
> behaviour)?
>
> Ben
>


Martin
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Ben Staude]

Am Montag 25 Oktober 2010 schrieb Martin (KDE):

[...]

> It is a feature. You can enable timestamp update in the configuration
> dialogue (metadata) and there in the first tab (Verhalten in german).

Thanks for the hint - I found the option and, while thinking about whether I
really want the timestamp updated, finally decided that it might be best to
not save metadata to the image files at all:)
That's the way my old tool did it and I am fine with it (as long as the sqlite
file is backed up...). Or is it "best practice" to save it into the image
files?

> > Still confused by the warning/error message, I found out that once
> > I edit/modify and save one image in the album (F4), digiKam
> > somehow does/gets a filesystem update and doesn't print the
> > warning/error message any more, even when metadata of another
> > image in the album is changed!?

The warning/error message is still present. Although I do not observe any real
problem with it, I'm still a bit concerned about it. Any suggestions, or has
this maybe been fixed since digiKam 1.2.0? This is the message again:
Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not
readable:  "/foo/bar.jpg". Note it's complaining about the *folder*, but
printing the path to a single *file*.

Thanks
Ben
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am Donnerstag, 28. Oktober 2010 schrieb Ben Staude:

> Am Montag 25 Oktober 2010 schrieb Martin (KDE):
>
> [...]
>
> > It is a feature. You can enable timestamp update in the
> > configuration dialogue (metadata) and there in the first tab
> > (Verhalten in german).
>
> Thanks for the hint - I found the option and, while thinking about
> whether I really want the timestamp updated, finally decided that
> it might be best to not save metadata to the image files at all:)
> That's the way my old tool did it and I am fine with it (as long as
> the sqlite file is backed up...). Or is it "best practice" to save
> it into the image files?

This depends. If you store the meta data to the file, you can see these
data with other tools as well. I for my point do this. Most of the
time I use gimp to edit pictures. If the exif data are in the file,
they survive editing. Without storing to file I had some meta data loss
after editing with gimp.

>
> > > Still confused by the warning/error message, I found out that
> > > once I edit/modify and save one image in the album (F4),
> > > digiKam somehow does/gets a filesystem update and doesn't
> > > print the warning/error message any more, even when metadata
> > > of another image in the album is changed!?
>
> The warning/error message is still present. Although I do not
> observe any real problem with it, I'm still a bit concerned about
> it. Any suggestions, or has this maybe been fixed since digiKam
> 1.2.0? This is the message again:
> Digikam::CollectionScanner::scanAlbum: Folder does not exist or is
> not readable:  "/foo/bar.jpg". Note it's complaining about the
> *folder*, but printing the path to a single *file*.

I never had a warning like this. But version 1.2 is a little outdated.
May be updating to current version gets rid of this error. But maybe
you have added the file "/foo/bar.jpg" as folder to your collection?

Martin

>
> Thanks
> Ben
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Ben Staude]

Am Donnerstag 28 Oktober 2010 schrieb Martin (KDE):

> Am Donnerstag, 28. Oktober 2010 schrieb Ben Staude:
> > Am Montag 25 Oktober 2010 schrieb Martin (KDE):
> >
> > [...]
> >
> > > It is a feature. You can enable timestamp update in the
> > > configuration dialogue (metadata) and there in the first tab
> > > (Verhalten in german).
> >
> > Thanks for the hint - I found the option and, while thinking about
> > whether I really want the timestamp updated, finally decided that
> > it might be best to not save metadata to the image files at all:)
> > That's the way my old tool did it and I am fine with it (as long as
> > the sqlite file is backed up...). Or is it "best practice" to save
> > it into the image files?
>
> This depends. If you store the meta data to the file, you can see these
> data with other tools as well. I for my point do this. Most of the
> time I use gimp to edit pictures. If the exif data are in the file,
> they survive editing. Without storing to file I had some meta data loss
> after editing with gimp.

That's a good point. I usually edit files with the gimp and save them as a
copy. digiKam can not guess that I'd like to have the same metadata (tags,
caption) for the new file. I'm afraid there's no "copy metadata from ...", is
there? There is "copy metadata to clipboard" in the right sidebar, but no
according "paste metadata from clipboard":(

> > > > Still confused by the warning/error message, I found out that
> > > > once I edit/modify and save one image in the album (F4),
> > > > digiKam somehow does/gets a filesystem update and doesn't
> > > > print the warning/error message any more, even when metadata
> > > > of another image in the album is changed!?
> >
> > The warning/error message is still present. Although I do not
> > observe any real problem with it, I'm still a bit concerned about
> > it. Any suggestions, or has this maybe been fixed since digiKam
> > 1.2.0? This is the message again:
> > Digikam::CollectionScanner::scanAlbum: Folder does not exist or is
> > not readable:  "/foo/bar.jpg". Note it's complaining about the
> > *folder*, but printing the path to a single *file*.
>
> I never had a warning like this. But version 1.2 is a little outdated.
> May be updating to current version gets rid of this error. But maybe
> you have added the file "/foo/bar.jpg" as folder to your collection?

I'm not aware of having added any file as a folder... The message appears for
"any" file, so I don't think this is the reason.
digiKam 1.2.0 came with my kubuntu 10.04; probably the best way to get an up-
to-date version would be to uninstall the dist packages and compile from some
tgz. I'm not sure if I want to go into that, as I'm afraid of problems with
the next dist upgrade...

Ben
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users