we created a new build that exposes the TIFF option as a C API. Not sure when it will be part of the official release but should be part of the Nightlies.
scroll to line 1475 for the imports definitions and 1690 for the actual usage of the methods . You may have to change the calls for C# but i trust it should work just the same.
Note the new build was really to expose the -tiff option which is now avail via this statement:
Did anyone figure out how to do this? I'm another one interested in using libraw, here again in C#, but I cannot figure out how to pass parameters. Would appreciate any help I can get, even if implemented in VB or another language.
You ca even use existing tools instead of coding w/ libraw or libtiff, see e.g. http://netpbm.sourceforge.net/doc/rawtopgm.html (and then easily convert PGM to TIFF w/ pamtotiff), or you can also use ImageMagick/GraphicsMagick and define the 'gray' input:
convert -size 512x512 -depth 16 -endian LSB gray:original.bayer -type grayscale result.tif (of course change the dimensions and endianness to suit your need)
Dear Sir:
We do support all raw samples from Leaf Aptus 17 that we have.
The easiest way to check if your files are supported is to download free trial of FastRawViewer https://www.fastrawviewer.com/download and open your .mos files with it.
I can't browse mos file on my windows 10 PC.
It is installed raw image extension program.But it doesn't work.
Mos file have been shot by leaf aptus 17.
That problem is viewing dark image preview on my PC.
I hope you support leaf aptus 17 raw file format.
I am trying to recreate the pixel statistics (min/max/avg/σ) that appear in RawDigger (per channel). Am I correct in assuming you are the authors of this software? If yes, then which LibRaw parameter was used to obtain these values?
Thanks
Well, I was originally trying to perform my analysis on difference images (subtract one image with identical parameters from another in order to remove flat field effects) but I'm getting ridiculously large values for the std dev (in the 1000s) which doesn't seem right. Am I being naive in assuming I can simply subtract the values of one raw array from the other?
yes, raw colorspace is 'as is'
I will look into the code and follow up if I have any questions. Also, what does the RAW colorspace mean? Does it mean the Camera's RGB space?
Dinesh
Use latest public beta.
when will it be compatible with the canon eos T7i camera? :((((((
Yes, it is still valid.
I am trying to activate rawspeed support in libraw, I am following the instruction here:
https://github.com/LibRaw/LibRaw/blob/master/README.RawSpeed.txt
this doc is not updated since 2018, is it still valid?
I check the raw speed:
https://github.com/darktable-org/rawspeed.git
master branch is not updated since 2014.
XYZ output is performed by applying color conversion matrix in convert_to_rgb() function
With default dcraw_emu settings output is scaled to saturate 1% of pixels, so result may differ for dcraw_emu -o 5 (than converted to sRGB)
Hi Robert,
Much appreciated. Where would I find the Nightlies, though? I looked here and on Github and didn't see anything that recent.
Thanks, Lothar
Hi,
we created a new build that exposes the TIFF option as a C API. Not sure when it will be part of the official release but should be part of the Nightlies.
You can see how i have used it in my VB.NET program: avail here: https://github.com/totoantibes/LumixCameraAscomDriver/blob/master/LumixC...
scroll to line 1475 for the imports definitions and 1690 for the actual usage of the methods . You may have to change the calls for C# but i trust it should work just the same.
Note the new build was really to expose the -tiff option which is now avail via this statement:
Hope this helps
Robert
Did anyone figure out how to do this? I'm another one interested in using libraw, here again in C#, but I cannot figure out how to pass parameters. Would appreciate any help I can get, even if implemented in VB or another language.
Nikon D3500 is supported by current snapshot and listed in supported camera list for it: https://www.libraw.org/supported-cameras-snapshot-201910
This camera is also supported by (coming) LibRaw 0.20
You ca even use existing tools instead of coding w/ libraw or libtiff, see e.g. http://netpbm.sourceforge.net/doc/rawtopgm.html (and then easily convert PGM to TIFF w/ pamtotiff), or you can also use ImageMagick/GraphicsMagick and define the 'gray' input:
convert -size 512x512 -depth 16 -endian LSB gray:original.bayer -type grayscale result.tif (of course change the dimensions and endianness to suit your need)
why don't you want to use libtiff?
You already have sensor dump in memory array, unprocessed. Just write it to file, you do not need to use LibRaw::open_bayer() for that.
Dear Sir:
We do support all raw samples from Leaf Aptus 17 that we have.
The easiest way to check if your files are supported is to download free trial of FastRawViewer https://www.fastrawviewer.com/download and open your .mos files with it.
I can't browse mos file on my windows 10 PC.
It is installed raw image extension program.But it doesn't work.
Mos file have been shot by leaf aptus 17.
That problem is viewing dark image preview on my PC.
I hope you support leaf aptus 17 raw file format.
As soon as we consider that everything is ready
Any projected date for the final release yet?
Thank you Lexa! I appreciate the pointers.
samples/unprocessed_raw.cpp sample is also a good starting point if you need unaltered raw values.
Quote from above:
> You can use 4channels sample to split source RAW into four separate TIFF files.
(or you can use 4channels sample source as reference for your code)
OK, but it's not possible to get the R/G/B/G2 values without postprocessing, or am I confused?
RawDigger calculated statistics on unaltered RAW values, the only processing performed is black level subtraction (if not turned off by user).
I am trying to recreate the pixel statistics (min/max/avg/σ) that appear in RawDigger (per channel). Am I correct in assuming you are the authors of this software? If yes, then which LibRaw parameter was used to obtain these values?
Thanks
Well, I was originally trying to perform my analysis on difference images (subtract one image with identical parameters from another in order to remove flat field effects) but I'm getting ridiculously large values for the std dev (in the 1000s) which doesn't seem right. Am I being naive in assuming I can simply subtract the values of one raw array from the other?
To add to what Alex just said, what demosaic, when what you want is sensor PTCs?
Pages