On Tuesday, May 19, 2015 at 12:14:12 AM UTC+2, Bruno Postle wrote: > > > Usually g & t are not optimised at the same time because they tend > to cancel each other out - you end up with some rotation and > asymmetrical scaling. Have you tried optimising 'v' angle of view > instead? > > -- > Bruno >
Yes, I've noticed that optimising g and t causes an odd rotation as well. Optimising for the field of view does seem to do the trick. Thanks! I'm not sure why I didn't. Perhaps I originally optimised all the values and noticed that the solution improved a lot if I removed the field of view optimisation (which is seems to be a weakness of the autooptimiser). It's interesting that I've always got very good solutions with a fixed field of view and have it compensated by r, g & t instead. My use for Hugin is by the way not to stitch images, but to track fireball paths across the sky, like this: http://norskmeteornettverk.no/bilder/2015/harestua-20150428-grid.jpg In the linked image the grid was created from a .pto file (with huge g and t values!) and the circles mark stars where they ought to be according to the .pto file. -- Steinar -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/6242d713-2124-4738-b4f5-f03b1ab013b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
