Why is the D1X explicitely disabled? about rawspeed

[klauspost]

The reason, as I remember it is, that it basically gives a different result than dcraw. I want to minimize the difference between them, and since it (even at the time I started writing RS) is a very old camera, I just decided to ignore it than spend too much time on it, since Nikon luckily dropped that path of development.

[pedrocr]

The result it gives is what's in the file, a half height image that needs to be scaled up after demosaic. dcraw does that upscale. I don't think rawspeed does any demosaic itself, and if it does, at least darktable certainly doesn't use it, so it's usually up to the app to scale up the image.

rawspeed should definitely provide the app with the metadata it needs to apply the operation. We need to think of an interface to do this as it's also an issue with the fuji cameras that need rotation after demosaic. I suppose adding that info to cameras.xml and providing it through the existing metadata interface would be our best bet.

[LibRaw]

There are a lot of D1X files in archives.
So, generally speaking, it is better to decode it and provide aspect ratio to RawSpeed users.

The same thing with some very old Kodak files (DC50 or DC120, cannot remember). But the image is compressed in horizontal direction.

[pedrocr]

@LibRaw I assume you mean decode the raw data and pass on the metadata on what to do to it after demosaic (2x scale up in this case). That's the only thing you can do when the app wants the raw bayer data and not a RGB image.

[LibRaw]

I agree. The only way to deal with bayer-processing upper layer is to return bayer array as-is and provide aspect ratio data for use after demosaic.

[klauspost]

Should be fixed with #49