Not sure how the compatibility works, but I own a Sony A7 III and a Canon EOS R. If I can scrape any data to help add each of those to the support list, I'd be glad to try.
The only way to get the accurate number for that is to look it up in the sensor data sheet. Raw file may contain virtual pixels, and may not contain all the physical pixels.
OK, Thanks for the explanation.
If you would write the formula to compute (estimate) the pixel pitch then, would you use raw_width or width ?
raw_width seems to be more the good one but for canon it gives result pretty far from the vendor value:
pitch = 22.3/6288 * 1000 = 3.55 (while it is given to be 3.7)
At the opposite, for the Sony it gives better result.
Single pixel size error in raw_width will result in distorted picture (like synchro loss on old analog TV), so raw_width/raw_height values are indeed right in LibRaw.
Visible (non masked) area is a matter of taste: LibRaw specifies 'as much as possible' (full visible area), while in-camera JPEGs (and, so, vendor advertized image size) may be slightly less than full area.
I see. I think I did not compile it with USE_JPEG. Thanks!
Just checked with master branch from Github: I do not see any problems with file you provided.
Note: the file is compressed with lossy (JPEG) compression, one need to build LibRaw with USE_JPEG compile-time define to support this kind of DNGs
RAW files from (most/many) cameras contains 'black mask', visible image are is less than full raw data (sensor area)
LibRaw is targeted to general purpose/mass market photographic cameras (see the list above), not special application ones.
However, it will decode any standard photographic raw file, so if some multispectral camera records DNG files, LibRaw will able to read it.
But, have you already sampled on other multispectral cameras?
Most likely no.
We do not have raw files samples from this camera.
Hi! Does this library support multi-spectral cameras such as the Mapir Survey 3?
LibRaw::open_bayer() designed exactly for this
Look into samples/openbayer_sample.cpp for details.
Current public snapshot supports Nikon Z6 and Z7, sorry these cameras was missed from release announce
https://www.libraw.org/news/libraw-snapshot-201903
When the Nikon z6 z7 release the firmware？
Sony A7-3 is supported in current snapshot: https://www.libraw.org/news/libraw-snapshot-201903
EOS-R support is expected in next snapshot/release, whatever comes first.
Not sure how the compatibility works, but I own a Sony A7 III and a Canon EOS R. If I can scrape any data to help add each of those to the support list, I'd be glad to try.
Mhhh ok.
So I will keep my estimation using sizes.width I guess.
The only way to get the accurate number for that is to look it up in the sensor data sheet. Raw file may contain virtual pixels, and may not contain all the physical pixels.
In astrophotography, Pixel size is a value often needed ;).
I don't see any practical sense in getting the exact pixel pitch value. Any approximated value is good enough
OK, Thanks for the explanation.
If you would write the formula to compute (estimate) the pixel pitch then, would you use raw_width or width ?
raw_width seems to be more the good one but for canon it gives result pretty far from the vendor value:
pitch = 22.3/6288 * 1000 = 3.55 (while it is given to be 3.7)
At the opposite, for the Sony it gives better result.
Not that easy :).
Single pixel size error in raw_width will result in distorted picture (like synchro loss on old analog TV), so raw_width/raw_height values are indeed right in LibRaw.
Visible (non masked) area is a matter of taste: LibRaw specifies 'as much as possible' (full visible area), while in-camera JPEGs (and, so, vendor advertized image size) may be slightly less than full area.
I would expect that the Sensor resolution width would match the raw_width, or the width value.
But I may be wrong.
For example
For Canon EOS 200D:
Sensor resolution width = 6026 pixels
Libraw:
width: 6022
raw_width: 6288
For Sony Alpha 7S:
Sensor resolution width = 4278 pixels
Libraw:
width: 4256
raw_width: 4288
What accuracy did you expect?
The resolution value, given in the link I gave you don't match with any field of libraw: width, iwidth nor raw_width.
Where I can find the explanation of the field ? ==1 (Canon APS-C?), == 2 (FF ?)
EDIT: I found it.
enum LibRaw_camera_formats
{
LIBRAW_FORMAT_APSC = 1,
LIBRAW_FORMAT_FF = 2,
LIBRAW_FORMAT_MF = 3,
LIBRAW_FORMAT_APSH = 4,
LIBRAW_FORMAT_1INCH = 5,
LIBRAW_FORMAT_FT = 8
};
Thanks Alex.
I will try this way.
For many (but not all) cameras LibRaw parses sensor physical size type (full frame, APS-C) into imgdata.lens.makernotes.CameraFormat
You may use this field and pixel dimensions (raw_width, raw_height) to estimate pixel pitch.
I don't think so, I would like the pixel pitch:
https://www.digicamdb.com/specs/canon_eos-200d/
Pages