[Digikam-devel] dcraw v8.27, -2 option problem

Arnd Baecker arnd.baecker at web.de
Mon Jul 31 12:45:52 BST 2006


Hi,

I just installed digikam from cvs and also upgraded my dcraw.

With dcraw v8.27 I get:

digikam: /home/abaecker/Pictures/EOS350D/IMG_1940.CR2 : RAW file
identified
Warning: Directory Canon has an unhandled next pointer.
Warning: Size 5352 of Exif.Canon.0x4002 exceeds 4096 bytes limit. Not
decoded.
digikam: Running dcraw command
(dcraw,-c,-2,-w,-a,-o,1,/home/abaecker/Pictures/EOS350D/IMG_1940.CR2)
digikam: Dcraw StdErr: Unknown option "-2".
kio_digikampreview: Running dcraw command dcraw -c -e
'/home/abaecker/Pictures/EOS350D/IMG_1940.CR2'
kio_digikampreview: Using embedded RAW preview extraction

With dcraw  v8.11 everything works (apart from the speed, see P.S.)

The origin of the problem is that
the option
-2        Write 8-bit non-linear PPM (default)
does not exist in  v8.27

Best, Arnd


P.S.: on my slow PIII, 1.2 GHz laptop, with dcraw v8.11,
the steps:
kio_digikampreview: Running dcraw command
   dcraw -c -e '/home/abaecker/Pictures/EOS350D/IMG_1941.CR2'
kio_digikampreview: Using embedded RAW preview extraction
digikam: Parsed PPM header: width 1157 height 1737 rgbmax 61408
digikam: Parsed PPM header: width 2314 height 3474 rgbmax 255

take about 50s. Is it expected to be that slow?

P.P.S.: BTW, digikam really rocks - only for browsing through
a sequence of images I still use gqview which is quite a bit
faster (I think that one of the (if not *the*) main factor is
that gqview caches the next picture in the row).
Do you intend to implement caching of images/histogramms etc.
for 0.9, or is this a possible post 0.9 feature?



More information about the Digikam-devel mailing list