Running Darktable 5.01 on MacOS Most horizontal orientation crw files from my D30 open correctly but most of the files that show as rotated in Finder will not open and are reported as unsupported. I haven’t owned a D30 for over 20 years at this point but I recall that the camera could not detect that it was being used in a vertical orientation and I probably rotated the raw files on a computer when I originally loaded them from the CF card. At the time I was running Windows XP and using Breeze Browser to browse the photos. I suspect metadata was added to the RAW file that Darktable does not recognize. Has anyone seen something similar? Is there a log file with more detailed error messages I can look at somewhere on my Mac?
I wonder if you could share one of the images that will not open so others can test it out and look at the metadata.
Sure, what is the best way to do that?
Just post the raw file here by dragging and dropping it into the replywindow. But attach a licence to it. You can copy one of these from the PlayRaw category.
Thanks
https://creativecommons.org/licenses/by/4.0
CRW_7362.CRW (2.7 MB)
DT gave me message saying file is corrupt. I wonder if other software will load it? Photoshop CS6 loaded image into camera RAW OK. RawTherapee opened the file.
A temporary work around would be to use a DNG converter on these images, but hopefully someone can resolve the issue for you.
I see the same error. I can load it with other software like Pixelmator.
There is one sample from a Canon D30 at https://raw.pixls.us and that sample open OK for me in darktable. I’d guess something is either corrupt or the metadata of your raw file has been altered.
Canon’s own software, Digital Photo Professional v4 on windows opened it.
Some hints:
If you change -Makernotes:Rotation from 270 to 0 - via ExifTool -, darktable 5.0.1 can open the photo. Colours are way off, until you either disable Colour calibration or use ‘set white balance to detected from area’.
LightZone can open the unchanged photo.
So many replies and trials, and no one attempted to find anything relevant in the log?
I would rather read Hegel, but this is something that even I can find in the evil darktable-log.txt file:
28,4615 [rawspeed] CRW_7362.CRW corrupt: virtual std::unique_ptr<rawspeed::RawDecoder> rawspeed::RawParser::getDecoder(const rawspeed::CameraMetaData*), line 97: No decoder found. Sorry.
1 Like
Thanks. It’s curious that one tag change caused the CrwDecoder to be discarded… Oh well, a RawSpeed debug session is called for I’m afraid…
I also wonder if Exiftool maybe cleans up some other silliness another tool created?
Yep, looks like this is the case, and the first tool changed some offsets in the file in an unpredictable manner. So the easiest workaround might be to either a) run all of those affected files through ExifTool, or b) force dt to use the less strict LibRaw loader via the libraw_extensions=crw workaround in darktablerc.
Lesson learned (again and again): do NOT let any tool make changes to a raw file, there be dragons. If you did, you better have kept a backup of the pristine one.
@kmilos These files were created and edited a long time ago. Later Canon cameras have an orientation sensor and the rotation happens in camera so only a D30 issue, at least for me.
@mlenard Thank, it looks like you found the issue and it is what I expected it to be, RawSpeed can’t handle the rotation tag. Where is the log file btw?
Btw, it’s not the value of the rotation tag per se that actually created the problem, just that the tool corrupted its structure. Modifying anything via ExifTool should fix it and one can even force rewrite of an entire folder w/o any metadata changes (back up first, of course).
On a Mac, they are output to the console.