Re: Digikam-users Digest, Vol 67, Issue 48

Happy new year 2011 at all, and with Digikam for the best.

Re: Digikam-users Digest, Vol 67, Issue 48

Happy new to everyone from us here on the Northern California Coast in the US b

Digikam eats a large part of my memory

_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users

Re: Migrating from F-Spot to digiKam: how to import tags?

Am 31.12.2010 20:04 schrieb Rafael Coninck Teigão:
> I believe it's XMP (just have to figure out how to write it for photos
> I've already tagged.)
> 
> Is there a particular way to import it or should I just use the import
> database tool?
> 
> Also, is it possible to retain the hierarchy of tags?

digiKam itself stores the tags with hierarchy in XMP, so parsing them is
not a problem. I don't if f-spot can write an appropriate structure.
This looks promising:
http://pozzi.ws/index.php?page=xmp-spot

Regards and happy new year,
Johannes

_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users

Different Versions of Images (Merge RAW and JPEG)

Hi and a happy new year!

I have a Canon 450D and on every shoot this cam saves two pictures: a
raw and a jpg. If I import those pictures in digikam I have all
pictures twice. And if I edit them I have some pictures even three
times in the library. On F-Spot there is a feature to merge all these
pictures into one as different "Versions" of each other so that the
picture is only shown once in the library with it's newest Version.
But you can vie any version of the image! (and the plugin is merging
the raw and it's jpg automagicly) Is there anythink like that in
digikam?

thx, Jan

Re: Digikam eats a large part of my memory

> I use Digikam 1.7 on Kubuntu 10.10 with Kde 4.5.4
> 
> Is it normal that it uses so much memory ?
> 
> I had also found in version 1.2 and 1.3

Could be better answered with a bit more context of the current use pattern.
Which one is the effective memory usage? The KDE system monitor is afaik 
pretty accurate to calculate that number.

Consider that an image e.g. loaded from a RAW, 14Mpx camera, 16bit, takes more 
than 100 MB of memory.

Marcel

Re: Different Versions of Images (Merge RAW and JPEG)

> I have a Canon 450D and on every shoot this cam saves two pictures: a
> raw and a jpg. If I import those pictures in digikam I have all
> pictures twice. And if I edit them I have some pictures even three
> times in the library. On F-Spot there is a feature to merge all these
> pictures into one as different "Versions" of each other so that the
> picture is only shown once in the library with it's newest Version.
> But you can vie any version of the image! (and the plugin is merging
> the raw and it's jpg automagicly) Is there anythink like that in
> digikam?

Versioning comes with 2.0, beta1 will be released very soon.
The auto-merging of RAW + JPEG is still missing though.

Re: Digikam eats a large part of my memory

_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users

Re: Digikam eats a large part of my memory

_______________________________________________
Digikam-users mailing list
Digikam-users@...
https://mail.kde.org/mailman/listinfo/digikam-users

Re: Digikam eats a large part of my memory

Marcel Wiesweg wrote:
> > I use Digikam 1.7 on Kubuntu 10.10 with Kde 4.5.4
> >
> > Is it normal that it uses so much memory ?
> >
> > I had also found in version 1.2 and 1.3
>
> Could be better answered with a bit more context of the current use
> pattern. Which one is the effective memory usage? The KDE system monitor is
> afaik pretty accurate to calculate that number.

I have also just recently had a bad experience with the DK memory usage.

I'm running DK 1.7.0 under openSUSE 11.2 x64, KDE 4.5.4 on a machine with 6 GB 
RAM. There are about 158000 photos in about 7000 albums in my collection, and 
I'm using mysql as database, if that matters.

If I have some applications running then e.g. a total of 1.9 GB of RAM is 
being used. Normally, if I then start DK, the total memory usage increases to 
about 2.5 GB, which I find OK.

Recently I've tried to let DK find all duplicates in my collection. First 
generated the fingerprints of all photos, and then ran "search duplicates". 
As expected, this took quite some time, but the bad thing was that this 
started to eat up all available memory, plus all my swap space. When I killed 
DK ('killall digikam') the memory was freed immediately. 

However, when I re-started DK then it obviously started to eat up all my 
memory again while the info message at the top of the startup logo 
said "Reading database ...". Unfortunately I did not find a way to stop this 
except killing DK again. The only I found to get this fixed was to delete all 
tables in the database and let DK build the database from scratch. 
Fortunately I have all attributes stored in the photos so it didn't hurt too 
much to rebuild the database. 

Anyway, this is an ugly behaviour. Maybe searches should only be remembered 
when they are explicitely saved.

Beside this, DK is a really great piece of software which I really like to 
work with.

Martin