since version 2 my fisheye setup doesnt work anymore... tried detection with different settings, optimised after detection, but every optimisation gives more weird results. setup: nikon d300 with peleng 8mm, APP detects it correctly, but then it gets worse... APP 1.4.2 managed it much better... see screenshots
Make a pano using a set of FE images, shot in the same sequenece at the same pan head positions, that stitch easily - I suspect your troublesome example set has features that confuse SIFT, repeating elements or something like that?
Then 'Save as a template' - name it, for example 'Peleng 8mm'.
The use that template when stitching your troublesome image set - I think you may get a good result.
I'd love to see that troublesome image set if you are are able to put it somewher on the Web where I can downlaod it and have a go at stitching it.
This little known simple template feature works very well in my experience.
Last edited by mediavets (2009-05-09 12:33:39)
Andrew Stephens Nikon D40, Nikkor 10.5mm fisheye, Sigma 8mm f3.5 fisheye, Nikkor 18-55/50/35mm lenses, Nodal Ninja 5 Lite, Nodal Ninja 4 with R-D16, Agno's MrotatorTCS short. Nikon P5100, CP5000, CP995, FC-E8, WC-E63,WC-E68, TC-E2, Kaidan Kiwi 995, Bophoto pano bracket, Agno's MrotatorA. Merlin/Orion robotic pano head + Papywizard on Nokia 770/N800/N810 and Windows 8/XP/2K.
thanks for your advice, the idea with the template is good... but the problem is definitely the 2.0 algorithm:
1. detected the set (5+zenith+nadir) in 1.4.2 and got an almost good result. 2. tried the same in 2.0 and got weird stuff 3. opened the 1.4.2 version in 2.0 and found what is going wrong: after optimisation all shots have f=29.38mm - it should be 12.2mm. after local optimising the zenith has 34.52mm, the nadir 28.90mm... so the algorithm doesnt keep the focal length but tries to fit it anyway... but wrong - almost 35mm instead of 12 is quite a difference...