-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get focal length, object distance and minimum object distace (MOD) from Quattro files #59
Comments
You cannot find this data in CAMF. There are some data in the beginning of the file that lacks It may be found somewhere there. If we had an SD Quatro camera Focussing and comparing the data might find us the object distance data. Of course, reading the EXIF data in the JPEG is probably much easier, except |
BTW - why is it important? Do we need this data? |
It is needed for spatial gain correction. There are several different corrections depending on aperture and focusing. We need to know this data to be able to select the right corrections and interpolate between them. As a side note, the way to select and interpolate between corrections for Merrill and Quattro is a bit sketchy. There are comments about that in x3f_spatial_gain.c. It's all guesswork more or less. |
We also need it for later programs that use this information. I tried to The crop factor may not be a direct 1.5, for instance; it may be 1.49 or On Sun, Jul 26, 2015 at 8:43 AM, Erik Karlsson [email protected]
|
Quattro files lack the entire PROP section and the ObjectDistance and LensInformation entries in CAMF. This makes the functions get_focal_length, get_object_distance, and get_MOD in x3f_spatial_gain.c fail with a warning and return arbitrarily chosen default values.
An example:
http://www.dpreview.com/forums/post/56207560
I suppose that, in principle, this data should be possible to obtain from the EXIF data in the embedded JPEG, but should that really be necessary? Shouldn't it really be somewhere in X3F?
The text was updated successfully, but these errors were encountered: