Bug 179031

Created attachment 29719 [details]
screenshot of exposure time

Can you send me the picture and one of the others with 8/100s exposure to my private address?

These pictures are not supported by exiv2. Andreas, do you know anything about .rw2 files?

Gilles, the wrong values come from libraw's rawFileIdentify. Do you know why these values are wrong?

No, but it seems they are of the TIFF-like variety with a custom TIFF-header. At least as far as reading the metadata is concerned. Adding basic read-support to Exiv2 won't be a big deal.

>Gilles, the wrong values come from libraw's rawFileIdentify. Do you know why >these values are wrong? 

Marcel, 

I don't know. I will contact Alex Tutubalin from LibRaw project for details.

Sven,

Can you perform a simple test with dcraw command line program:

dcraw -i -v myrawfile.rw2 

Another try is to use test program 'identify' from libraw generated with libkdcraw. This program emulate "dcraw -i -v". Just run it with your rw2 file

Gilles Caulier

Marcel,

This is the response from Alex:

------------------------------------------------------------------
Gilles Caulier wrote:

    Alex,

    Can you take a look in this bug report from KDE bugzilla:

    http://bugs.kde.org/show_bug.cgi?id=179031

I've tested my tiny collection of .rw2 files with identify without any problems.

Also, it is not easy to get negative shutter speed (this value is either directly
read from file or calculated as pow(2, some-value) ).

Possible error source is _float_ shutter value: if some code interprets it as double
many strange things may happen.

Anyway, need sample file with this error

-- 
Alex Tutubalin
Web: http://blog.lexa.ru
mailto:lexa@lexa.ru
--------------------------------------------------------------------------

For the picture that shows 160 s in digikam I get:

dcraw -i -v p1000039.rw2 

Filename: p1000039.rw2
Timestamp: Tue Dec 23 14:36:55 2008
Camera: Panasonic DMC-LX3          
ISO speed: 80                      
Shutter: 1/160.0 sec               
Aperture: f/2.8                    
Focal length: 5.1 mm               
Embedded ICC profile: no
Number of raw images: 1
Thumb size:  1920 x 1440
Full size:   3724 x 2754
Image size:  3724 x 2754
Output size: 3724 x 2754
Raw colors: 3
Filter pattern: RGGBRGGBRGGBRGGB
Daylight multipliers: 1.000000 1.000000 1.000000
Camera multipliers: 482.000000 263.000000 463.000000 0.000000

For the picture with the negative exposure time I get:

dcraw -i -v p1000041.rw2 

Filename: p1000041.rw2
Timestamp: Tue Dec 23 14:38:43 2008
Camera: Panasonic DMC-LX3          
ISO speed: 80                      
Shutter: 1/125.0 sec               
Aperture: f/2.8                    
Focal length: 5.1 mm               
Embedded ICC profile: no
Number of raw images: 1
Thumb size:  1920 x 1440
Full size:   3724 x 2754
Image size:  3724 x 2754
Output size: 3724 x 2754
Raw colors: 3
Filter pattern: RGGBRGGBRGGBRGGB
Daylight multipliers: 1.000000 1.000000 1.000000
Camera multipliers: 535.000000 263.000000 432.000000 0.000000

If you need the output of "identify" as well, let me know.

Exiv2 now has basic read-support for Panasonic RW2 format (SVN trunk, Rev. 1722). It is also possible to extract a JPG preview image from the raw file (that works at least with the samples from a DMC-LX3 and DMC-FZ28 that I have here), using exiv2 with the -pp and -ep options. Interestingly the preview contains a lot more metadata than what is readily available in the RAW file.

Andreas

SVN commit 906707 by mwiesweg:

Interpret shutter value from libraw correctly

CCBUG: 179031

 M  +1 -1      dmetadata.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=906707

Ok we fixed the original problem interpreting the value from libraw,
and got full exiv2 support now as well.

Is there some database with the meta-data or do I need to update anything else than digikam? I just compiled and installed Revision: 906728 and still see the number without the 1/ in front of it and the ...41.rw2 picture I send you now shows -21s.

Yes the value is stored in the database. (If you look at the metadata tab, which is loaded from the file, the value is correct). There is no UI tool to force a rescan currently. Quick fix for you: open your database file with the sqlite3 tool and execute
UPDATE Images SET modificationDate=NULL WHERE name LIKE '%.rw2';
which forces a rescan of *.rw2 pictures at next start.

You were right, although I got impatient since your query returned that there is no table Images and just deleted the db. I tried .databases and it showed main and temp, but .tables or .tables * showed nothing. Anyway, after creating a new db it the correct exposure times are shown. Thanks for fixing!