[Digikam-devel] [Bug 307602] Large TIFF files crash digiKam (>1Gb)

[Axel Krebs]

https://bugs.kde.org/show_bug.cgi?id=307602

Axel Krebs <axel.krebs at t-online.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |axel.krebs at t-online.de

--- Comment #23 from Axel Krebs <axel.krebs at t-online.de> ---
I've got a new camera D800 with 36 mio pixels.
It looks like large pixels-numbers can improve doing panoramas.

First observation: all takes huge space and _much_ more time.

Storing times in digiKam are _much_ longer, even when doing (only) small
modifictions in picture editor.
Maybe a new storage concept could overcome this potential handicap? I think
about
working with virtual pics-copies and when finishing work on pics, the
output will be written on disk- not before.

When working with tags (geotagging, e.g.), it feels _much_ slowlier than with
smaller pics (14, 3 as before). I do not understand why, as metadata should
scale constant (that is independent form pic size).

Crashes occour, when HUGIN as an external program finishes, as described
previously (bug #...?).

When finishing digiKam, I still get a crash event rather than simply closing
(bug #...?).

?? Do you need specific information, some minimal statistics, maybe?
Loadings times, storing times for small (7 mio)  medium size (14 mio)  and
large pics (30 mio)??

Have a nice Sunday-



Axel

My statistics right now:
digiKam version 2.8.0
Bilder:
BMP: 3
GIF: 99
JP2: 14
JPEG: 273
JPG: 118942
NIKON-NEF: 640
PGF: 2
PNG: 1608
RAW-CR2: 632
RAW-CRW: 11258
RAW-DNG: 7
RAW-NEF: 80755
TIFF: 1780
XCF: 1
Gesamt: 216014
:
:
Videos:
AVI: 60
MOV: 23
MPEG: 3
Gesamt: 86
:
:
Gesamtzahl der Einträge: 216100
Alben: 2222
Stichwörter: 109
Datenbanktreiber: QSQLITE

-- 
You are receiving this mail because:
You are the assignee for the bug.