[Digikam-users] 16bit Tiff's: no thumbs + 4 questions for 0.9.0 svn

[Caulier Gilles]

Le Jeudi 25 Mai 2006 08:12 PM, Caulier Gilles a écrit :
> > Don't know if this is a bug or a problem of my 0.9.0 svn-install:
> >
> > when saving a 16-bit TIFF there is no thumbnail for this picture.
> > Only 8bit TIFF's get a thumbnail in the albums.
>
> I'm currently working in tiff loader in digiKam core to support better
> exif/makernote/iptc during saving from editor (TIFF/EP compliant).
>
> I cannot reproduce this thumb problem with current implementation. digikam
> kioslave witch perform thumbnails rendering support 16 bits images (that
> konqueror don't support very well).
>
> Are you sure that you kioslave used by digiKam is really from 0.9.0 not
> 0.8.x (when you mix both versions on a system for example)

I have found a problem about ordering to load image data and icc profile/ 
metadata with libtiff, especially with libtiff version > 3.6.1: all metadata 
need to be load _before_ image data. 

The current implementation work fine with libtiff 3.6.1, but i suspect a 
problem with recent libtiff release.

The code is fixed in my computer, but i need to perform more advanced test 
before to commit...

Just to confirm this point, witch libtiff release you use ? Your broken tiff 
image thumb have an icc profile embedded ?

ALso, can you check in your ~/.xsession-errors file if you have some messages 
from digikam thumb kioslave, like this :

kio_digikamthumbnail: /home/gilles/Documents/photos/Test 
Photograhs/JPEG/Vertical/MINOLTA-DYNAX5D.tif : TIFF file identified
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KLauncher): ERROR: SlavePool: No communication with slave.
Warning: Upper boundary of data for directory Image,  entry 0x0132 is out of 
bounds:
Offset = 0x00b4aa3a, size = 20, exceeds buffer size by 1 Bytes; adjusting the 
size
...

or something like that...

Paco, you have already reported this problem to me recently. I think to have 
found the problem. I will trying to commit the fix tomorrow (my main computer 
is broken here at home - main board crashed...)

Gilles