Hi, I just found out I forgot to respond, so I'm gonna do it now and try to remember where the problem was and what was the solution. :)
In the end it was (as it usually is with the stuff you're learning to use) my own fault (that much I remeber).
I'm not sure if it was because I was setting the values of gama etc. before LibRaw::unpack() or had error in build settings causing the new code to be built elsewhere and was always running the old project. (Or maybe both, so many things happen when you're trying to figure something out :))
Well, both would be nice to know about. The situation has changed for me since asking this question :) Right now color profile could help me a bit more.
Calculated temperature *will* differ from camera because camera and LibRaw uses different color profile (because color profile is used for xy-calculation)
The only way to check results is to compare to Adobe software (Lightroom or Camera Raw) with same color profiles (so, for example, DNG file with built-in camera matrices: ACR/Lr uses embedded color datain DNG case and LibRaw may be forced to do the same)
qDslrDashboard is a cross platform application (Android, iOS, Linux, OSX, Windows) for controlling DSLR (Nikon, Canon, Sony) and is using LibRaw for displaying RAW images downloaded from DSLR.
My Win32 binary works on it as well (although the color matrix does seem a bit odd, it loads). It's the Mac one that crashes. I'll see what I can do on the GitHub -- didn't see the link to it on the site.
Strangely enough, but LibRaw 0.16 (Win32 binary) handles this file OK.
FastRawViewer uses 'master branch' (available on GitHub: https://github.com/LibRaw/LibRaw)
This branch to be released as LibRaw 0.17 within month or less.
After years of hacking bits out of dcraw myself, I adopted LibRAW quite some time ago and haven't looked back. The software is designed for astrophotography and is called "Nebulosity 3" -- http://www.stark-labs.com/nebulosity.html
Hi! I've been looking for such a tool as well. Lately digikam makers pulled together the DNG writer for their solution. However, you can very well use the HDRMerge tool and it's command-line interface to achieve good quality. I did some testing, and to me it looks like the DNGs produced with this combo are faster in Lightroom to load than those produced by Adobe.
As to my own motivation, I'm interested in getting the best possible results out of Sony A7, and currently the best results sharpness wise still come from TIFF files produced by ImageDataConverter. I hope the best result at some point will come from LibRaw. I will be switching to DNGs by LibRaw for performance now.
LibRaw do not calculates raw data histogram.
So, you need to
1) unpack raw values using LibRaw::unpack()
2) (if needed) subtract black level (bias)
3) calculate histogram by you own code
It seems to me that black and white isn't really an adequate test in this area. I'm thinking in terms of the poor buttercup yellow gradation many cameras can have due to the fact that it's a mix of the basic bayer colours. I get the impression at times that colour mixes including yellows for instance can cause a lack of sharpness.
Just use make -f Makefile.dist to build LibRaw. You may need to edit Makefile.dist to suit your needs.
./configure script is created by running autoreconf --install
It works fine on my FreeBSD test machine (autoconf 2.69 and automake 1.14), is your autoconf/automake stuff is fresh enough?
RawSpeed/development looks very unstable. For example, Nikon small-NEF support is definitely broken; multi-sample DNG support (Fuji SuperCCD dngs) is not compatible with LibRaw in data layout and many other things looks strange (e.g. 'unprocessed raw' concept without tone curve).
So, to use development RawSpeed with LibRaw it needs heavy make-up.
Just one more question:
Are you planning to include RAF support in rawspeed?
It would seem that only the development branch of Rawspeed is actually developing things at this moment...
LibRaw uses RawSpeed only for selected (tested) formats. Fuji RAF is not in this list yet, so you'll need to change more source code.
If you change the source, you can remove libxml2 from dependencies on your copy.
Yes, I could do that, but I really would like to use the updated rawspeed, with FUJIFILM X-trans support.
I already 'translated' camers.xml to the correct format.
Now I need to alter the code in "libraw_cxx.cpp" to use pugixml instead of libxml2 in order to load the (updated) "rawspeed_xmldata.cpp" into the 'CameraMetaData' class.
Could you perhaps point me into the right direction for that?
Hi, I just found out I forgot to respond, so I'm gonna do it now and try to remember where the problem was and what was the solution. :)
In the end it was (as it usually is with the stuff you're learning to use) my own fault (that much I remeber).
I'm not sure if it was because I was setting the values of gama etc. before LibRaw::unpack() or had error in build settings causing the new code to be built elsewhere and was always running the old project. (Or maybe both, so many things happen when you're trying to figure something out :))
Well, both would be nice to know about. The situation has changed for me since asking this question :) Right now color profile could help me a bit more.
Calculated temperature *will* differ from camera because camera and LibRaw uses different color profile (because color profile is used for xy-calculation)
The only way to check results is to compare to Adobe software (Lightroom or Camera Raw) with same color profiles (so, for example, DNG file with built-in camera matrices: ACR/Lr uses embedded color datain DNG case and LibRaw may be forced to do the same)
Thank for reply.
I looked to DNG SDK but I am not able move cam_mul[] to DNG SDK required parameters dng_xy_coord. Calculated temperature is different than on camera.
What is right way how convert cam_mul to xy or XYZ?
Thank you
Ladislav
You may use code from Adobe DNG SDK sources.
For bayer image, use imgdata.rawdata.raw_image array to access unprocessed values decoded from raw file
Hi, I am working on similar function. For me will be nice RGB values.
Thanks
qDslrDashboard is a cross platform application (Android, iOS, Linux, OSX, Windows) for controlling DSLR (Nikon, Canon, Sony) and is using LibRaw for displaying RAW images downloaded from DSLR.
Glad to hear.
OK - false alarm. Build settings on one of the Macs was causing this... Sorry!
Craig
My Win32 binary works on it as well (although the color matrix does seem a bit odd, it loads). It's the Mac one that crashes. I'll see what I can do on the GitHub -- didn't see the link to it on the site.
Craig
Strangely enough, but LibRaw 0.16 (Win32 binary) handles this file OK.
FastRawViewer uses 'master branch' (available on GitHub: https://github.com/LibRaw/LibRaw)
This branch to be released as LibRaw 0.17 within month or less.
After years of hacking bits out of dcraw myself, I adopted LibRAW quite some time ago and haven't looked back. The software is designed for astrophotography and is called "Nebulosity 3" -- http://www.stark-labs.com/nebulosity.html
http://www.stark-labs.com/depot/neb3_color256x256.png
Craig
Do you need 'color profile' data, or image pixels in RGB?
Hi! I've been looking for such a tool as well. Lately digikam makers pulled together the DNG writer for their solution. However, you can very well use the HDRMerge tool and it's command-line interface to achieve good quality. I did some testing, and to me it looks like the DNGs produced with this combo are faster in Lightroom to load than those produced by Adobe.
http://jcelaya.github.io/hdrmerge/
http://jcelaya.github.io/hdrmerge/documentation/2014/07/11/user-manual.html
As to my own motivation, I'm interested in getting the best possible results out of Sony A7, and currently the best results sharpness wise still come from TIFF files produced by ImageDataConverter. I hope the best result at some point will come from LibRaw. I will be switching to DNGs by LibRaw for performance now.
LibRaw do not calculates raw data histogram.
So, you need to
1) unpack raw values using LibRaw::unpack()
2) (if needed) subtract black level (bias)
3) calculate histogram by you own code
This is not capture (camera) test, but demosaic test.
It seems to me that black and white isn't really an adequate test in this area. I'm thinking in terms of the poor buttercup yellow gradation many cameras can have due to the fact that it's a mix of the basic bayer colours. I get the impression at times that colour mixes including yellows for instance can cause a lack of sharpness.
You were right, my autoconf/automake stuff was not up to date.
I updated to autoconf 2.69 and automake 1.14, and now i get a working configure script from running
autoreconf --install
Thanks for your quick response, and have a nice day
Johann
Just use make -f Makefile.dist to build LibRaw. You may need to edit Makefile.dist to suit your needs.
./configure script is created by running autoreconf --install
It works fine on my FreeBSD test machine (autoconf 2.69 and automake 1.14), is your autoconf/automake stuff is fresh enough?
What happens if you use dcraw_emu sample with different -g parameters?
RawSpeed/development looks very unstable. For example, Nikon small-NEF support is definitely broken; multi-sample DNG support (Fuji SuperCCD dngs) is not compatible with LibRaw in data layout and many other things looks strange (e.g. 'unprocessed raw' concept without tone curve).
So, to use development RawSpeed with LibRaw it needs heavy make-up.
Thanks for the quick reply.
Just one more question:
Are you planning to include RAF support in rawspeed?
It would seem that only the development branch of Rawspeed is actually developing things at this moment...
Greetings,
Auke
LibRaw uses RawSpeed only for selected (tested) formats. Fuji RAF is not in this list yet, so you'll need to change more source code.
If you change the source, you can remove libxml2 from dependencies on your copy.
Hi,
Yes, I could do that, but I really would like to use the updated rawspeed, with FUJIFILM X-trans support.
I already 'translated' camers.xml to the correct format.
Now I need to alter the code in "libraw_cxx.cpp" to use pugixml instead of libxml2 in order to load the (updated) "rawspeed_xmldata.cpp" into the 'CameraMetaData' class.
Could you perhaps point me into the right direction for that?
Thanks and greetings,
Auke
Pages