mediavets wrote:APG recognises the lens as a fisheye with a 35mm equiv. focal length of 15mm on D800 in DX mode which shoulkd be good enough.
mediavets wrote:klausesser wrote:Destiny wrote:Even though, I had a RMS of 3.86 with Quick Optimise and a 3.66 with Full Optimise stating its was Very Good, however the final stitch was NOT Very Good...
No surprise: 3.66 is far from being "very good". "Very good" is around RMS 1 or 1.5 - at least with higher resolution than an average fisheye pano.
Irrelevant I think -
Destiny wrote:So, a question for you Klaus.. Do you achieve an equally good results using a Fisheye as with a normal prime lens...??.
klausesser wrote:mediavets wrote:APG recognises the lens as a fisheye with a 35mm equiv. focal length of 15mm on D800 in DX mode which shoulkd be good enough.
No. Not at all.
ItÂ´s still 10,5mm on a D800. No matter the used sensor size: a 10,5mm stays a 10,5mm - on which camera ever.
klausesser wrote:Maybe hereÂ´s a problem: it IS a 10,5mm on a FX simulating to be a DX. A problem can occur when there are confusing data in the EXIF:
IF the D800 tells an application to be a DX because itÂ´s in DX-mode - the application MIGHT BE thinking it must change the focal-values . .
but the question is: what are the EXIFs telling the app??
Do the EXIFÂ´s KNOW AT ALL itÂ´s a FX simulating a DX? Do the EXIFs tell the app itÂ´s a FX simulating a DX?
Does the app UNDERSTAND this informations? HOW do the apps interprete a FX simulating a DX?
In my experiences there are two kind of EXIFs: 1) from the camera-body, 2) from the lens.
Now the camerabody is a FX by the EXIFs, the lens is a DX by the EXIFs.
I donÂ´t know how Nikon "translate" the FX to DX via the EXIFs to an application.
mediavets wrote:Do you see any problems here?
Users browsing this forum: No registered users and 1 guest