Hi,
according to the documentation, the dcraw_emu tool should produce binary identical results to those produced by dcraw with the same command line keys. I have an example file where the behaviour between the two binaries differ. You can get the file here: https://drive.google.com/file/d/0B-kBET7UtPB9RkVzVzF6NzNWQzA/view?usp=sh....
Note that I used the following command on the file: ./dcraw -v -q 3 -4 -T ./IMG_9975.CR2

Hello, it's me again.
this time about the Sigma RAW files.

After libraw_unpack(), it appears that rawdata.raw_image is null and rawdata.color3_image not null.
Does it mean that there are no Bayer patterns in this kind of file ?

My best regards,

Hi,

When I am taking picture using a Canon 80D face down, most of the image converted by libraw (current master branch as Sep/26/2016) look kind of scattered and messed up. If I take picture while taking camera horizontally, all the images are OK. I have attached a converted one by libraw. Please let me know how I can send you the raw file since it has the right image in it.

If I understand correctly the following lines make not possible to work with UNICODE paths on windows (built with MinGW-64 compiler)

#if defined(_WIN32) && !defined(__MINGW32__) && defined(_MSC_VER) && (_MSC_VER > 1310)
int LibRaw::open_file(const wchar_t *fname, INT64 max_buf_size)

Can __MINGW32__ macro be narrowed to __MINGW64__?

But it looks like that mingw64 std library has wide char file i/o functions (_wfopen).

Hello, I'm using libraw since a while in my opensource software.
However, since 0.17 I have a crash I did not have before.
gdb gives me: