[simico]

Simico - What version of dcraw are you using? The latest is v8.86, I believe.

Hmm, yast tells it is version 1.404-1.33
I've just checked dcraw's homepage and now K2000/K-m is on the list... I'm sure it wasn't there the last time I checked.
Anyways I already switched raw format to dng and shoot raw+jpg.

[graemev]

I've had a K-m now for a whole week!
Before deciding to buy it I made sure I could read the raw files and process them in the GIMP. I downloaded some PEF and some worked and other got this error. Since some worked I took that to mean the format worked but there were some corrupt files out there.


Turns out not to be the case ... support was lacking.

In order to process PEF files at all, I built a custom version of GIMP 2.6 (with UFRAW support) ... having got the source I was able to research this a little.

While PEF format was supported . The K-m / K2000 was not.
Support for K-m / K2000 was added in dcraw 8.92 ...this is not yet built into any versions of ufraw. ufraw seems to use a (moderately different ) version of the dcraw file it's been converted into C++ and hacked a bit ... so you can't just copy the dcraw.c into the ufraw build tree.

The GIMP I have uses ufraw 0.15 which is based on dcraw 8.89

Support for DNG seems good ...so I've switched to that for (I prefer more open formats anyhow). If you have PEF format files ... don't despair ... just need dcraw 8.92 or later... it's only a single line change so it's not a lot of effort to be ported.

$ diff dcraw.cc.orig dcraw.cc
6463a6464,6468
>
> { "PENTAX K-m", 0, 0,
> { 11057,-3604,-1155,-5152,13046,2329,-282,375,8104 } },
>

[graemev]

My longish post got lost ...so I'm just trying this junk msg (sorry) to test it wont lose it again

[graemev]

OK that one survived.

In short then:

I've ha d K-m for a week now. Before buying it I made sure GIMP could read the PEF files. In order to do so I built a version of GIMP 2.6 from source (11:00PM---5:00 AM ) anyhow if could read some not all PEF) so I bought the Camera.

Hit this problem.

Seems support for K-m/K2000 was added in dcraw 8.92 .. I was using UFRAW 0.15 which was built based on dcraw 8.89.

dcraw 8.92 is able to read the PEF OK ... but not what I want since I want UFRAW + GIMP to support it.

The change is a single line, so it should make it across soon.

Right now I switched to DNG format which works fine even with older dcraw/ufraw

If you're interested the line is:


6463a6464,6468
>
> { "PENTAX K-m", 0, 0,
> { 11057,-3604,-1155,-5152,13046,2329,-282,375,8104 } },
>


I suspect it's just and offset that's changed somewhere.

[lawsonstone]

I continue to have this problem, but keep noticing my bad files are under 10 MB. These files are opening just fine in Graphic Converter. Exporting from there to TIFF and then importing into Aperture at least allows me to edit them full-scale.

I wonder if a utility to change the EXIF data line for camera type from K2000 to, say, K20D, would do the trick? We did that back when Mac OSX was choking on PEFs and the cause turned out to be that the manufacturer name line in the EXIF file was different. A utility to re-write the file with that tag changed fixed it. Likewise with lens type data.

Just a thought. I'm no coder, but that might work as a short term fix.

[simico]

Seems support for K-m/K2000 was added in dcraw 8.92 ..
dcraw 8.92 is able to read the PEF OK ...

Yesterday I tried the new rc version of Raw Therapee. It uses a newer version of dcraw than the previous rc and now it can open all of my PEF files including the "problematic" ones too. So probably the newest dcraw version is included in it.

[lawsonstone]

For us basic Mac OS X users, would that be the next Raw Support update? It is at least useful to know the files are not just being randomly corrupted.

[graemev]

30 mins researching this problem then 2 hours trying to log back into this site. .... then it lost my post (again)

Anyhow the fix was note quite as simple as I'd suggested. Looks like David had two bites of cherry. 8.92 fixed the K-m / K2000 issues with a hard coded hack Then he came back in 8.93 and did a cleaner job
There was a new mapping function for Pentax which I'd missed. I ported the full hack into ufraw 0.15 (dcraw.cc) and hey presto I can load PEF (K-m) files and also DNG files ... works great.

So: dcraw 8.92 works
dcraw 8.93 works
ufraw 0.15 does not work (unless you hack it)

In terms of the Mac, there seem to be compiled version of dcraw 8.93 at:

Pukkita's Digital Darkroom Corner

(as described on the dcraw homepage Decoding raw digital photos in Linux )

The Mac version looks like its intended to be untared into / (root) ... which strikes
me as a bit tacky , but I guess it works (suggest you back up the files it overwrites 1st)

$ tar tzvf dcraw-MacOSX.tgz
-rw-r--r-- pacopepe/pacopepe 6659 2009-03-03 20:53 usr/share/man/man1/dcraw.1
-rwxr-xr-x pacopepe/pacopepe 290804 2009-03-12 00:00 usr/bin/dcraw
-rw-r--r-- root/wheel 4078 2009-03-12 00:00 usr/bin/dcraw.1
-rwxr-xr-x root/wheel 392764 2009-03-12 00:00 usr/bin/dcrawG4
-rwxr-xr-x root/wheel 388564 2009-03-12 00:00 usr/bin/dcrawG5
-rwxr-xr-x root/wheel 1084884 2009-03-12 00:00 usr/bin/dcrawU
-rwxr-xr-x root/wheel 297740 2009-03-12 00:00 usr/bin/dcrawx86

... there may be better install instruction on the site ... I didn't look.

[lawsonstone]

Here's my own update. I still get a pretty good fraction of PEFs from my K2000 that the MacOS cannot open. A string of 10 will be fine, then 2 or 3 are black.

I can open them in Pentax Photo Browser, export as DNG and they are fine in Aperture, iPhoto, anything OSX.

Interesting point: If I shoot DNG in the camera, the MacOS can't see the lens model data. But if I shoot PEF and convert the troublesome PEFs to DNG in PPB, the EXIF data is fine.

Mac users can recall a long saga of problems related to lens model data in RAW files. Not relelvant, but still ironic.

SO...my pesky PEFs are fine if I convert to DNG using PPL. A workaround is at least some kind of solution until the real problem is solved.

NOTE: I've tried many brands of card, no dice. Size of file doesn't matter. ISO doesn't matter as far as I can tell. I really think there is some little bitty random problem with the way the PEF file gets written. The MacOS expects "rules" to be followed to the letter, maybe the Pentax and Adobe software are a little more flexible?

[Marc Sabatella]

Regarding lens info, my recollection is that it can be stored in two different places in EXIF (the "regular" area or MakerNotes area). And one of those areas might use a text string and the other a numeric code. My guess is that MacOS can display the info only if happens to be stored using the text string in the specific field where it is looking.

As for the black frames, I wonder if maybe there are multiple compression schemes that the Pentax firmware chooses from when saving a PEF, and MacOS doesn't understand one of them? I recall something similar being the case with another program and another camera model.

[simico]

Here's my own update. I still get a pretty good fraction of PEFs from my K2000 that the MacOS cannot open.

I think it's the same story as with Bibble 5: they received some K-m/K2000 PEF files (I also sent some) and reverse engineered them - unfortunately this resulted in not 100% compatibility. Bibble 5 (and DigiKam) also cannot open some PEF files while latest version of RAW Therapee and ufraw can open them fine (PPL can open them fine, of course ).