Data is not empty,
your pixels are in data.....data[data_size-1]
Thanks Alex, with your detailed description I was able to compile the libraw.dylib and its working now with Xamarin.Mac,
The easiest way to create libraw.dylib is to run
Note: on fresh enough macOS this command sequence may end with ...blabla...aclocal-1.15 missing
In that case you need to recreate ./configure script by using
To run that you'll need these software packages: autoconf, automake, libtool, pkg-config. You may install it using macports or homebrew, or just download source code and install (please note: autoconf 2.70 is not working for unknown reason, use version 2.69)
Will this be supported in the near future?
R5 uses new metadata format which is not supported by LibRaw 0.20.
We plan to support it in next public snapshot.
Do you have any plan to support brand new Sony A7C?
Thanks in advance.
It seems like a lot of time has passed, but is there any solution?
If you're talking about 'Microsoft RAW image extension', please contact vendor (Microsoft).
We're not involved in this product development in any way and not responsible for it.
thanks for your answer!
So I will have to wait for a new FreeImage version or try to fix the FreeImage environment myself - good to know that :-)
Thanks again and merry Christmas,
Sorry, know nothing about FreeImage.
LibRaw I/O layer (LibRaw*datastream) has changed (simplified) in LibRaw 0.20, so if FreeImage uses own LibRaw I/O implementation (subclass of LibRaw_abstract_datastream) it should be changed too.
We're completely unaware of MS schedule
Thanks. Hopefully that will support the compression option of these cameras also? How long does it then typically take MS to incorporate them into the add-ons for Windows Explorer?
EOS R5/R6 support is expected in next 'public snapshot'
Hi, when will it be compatible with the canon eos R5 camera?
std::map test; ->
std::map<std::string, LibRaw> test;
Leica M8 is bayer camera, so data is expected in imgdata.rawdata.raw_image
I suggest you to read the docs: https://www.libraw.org/docs/API-datastruct.html#libraw_rawdata_t
Hi Alex, I decode a leica M8 DNG file with unprocessed_raw compiled with adobe DNG SDK 1.5.1, after RawProcessor.unpack() with LIBRAW_SUCCESS return, I found both RawProcessor.imgdata.rawdata.color3_image and RawProcessor.imgdata.rawdata.color4_image is NULL. I can not get that unprocessed raw data. But use dcraw_emu without adobe DNG SDK, I can get a tiff file. and I can get an unprocessed data tiff file (called stage 1 data) with dng_validate, which is a sample of adobe dng sdk.
the sample file is here: https://www.dropbox.com/s/yheqp9lkvuut2ee/LEICA_M8.DNG?dl=0
another sample of Leica DMR DNG: https://www.dropbox.com/s/n9iee4b5rse4ukv/Leica_DMR_R8_L1185423.DNG?dl=0
the same problem as M8. :-(
thank you for your response
Thanks a lot.
It looks like BaselineExposure +2... is common for these files. Also, these samples displays correctly if BaselineExposure is applied.
BTW, in 1st file (11_2.5x) data maximum is 503 in green channel, so only 9 bits out of 12 are used.
Sorry for late response. here are some samples.
Hope those samples were useful.
BTW, if you have more samples from this camera, could you please share it, if possible?
In this specific sample, BaselineExposure tag is set way to high (+2.32), that results in too light rendering in Adobe tools.
it would be interesting to know is that tag setting is systematic, or resulted from some camera settings (e.g. highlight priority, resulting in underexposure)