> Maybe you are aware that hugin implements only a small number of distortion parameters from the Brown-Conrady lens model
Yes, I remember you told me here https://groups.google.com/g/hugin-ptx/c/ERSQCxkbxkw/m/hFZmxWOwAwAJ > Does hugin so far satisfy your precision requirements? At least if a panorama lacks precision it's due to either the wind or the camera not being properly calibrated so I don't think a more complete lens model would make much of a difference. It's more a matter of manipulating control points efficiently. Sometimes an iterative "optimize > select by distance > delete > optimize, etc..." converges towards the wrong objects and by the time I realize there is an issue I have to either restart by eliminating the right CPs from the beginning or just place some CPs manually. I'm mostly looking for an efficient workflow to determine early on whether there is parallax or large moving/deforming objects. Thinking of it, something that would be totally awesome is a vector map overlay, showing the distance between control points and the direction towards their corresponding one. This way you could immediately see from the first optimization if and which objects are moving relative to each other and decide what to do about that. Does that seem like a good idea to you? -- 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/UQraqx2UIADm5fmSOcuYvktOLtOpSVq6qt8yUs1ejicraO3UUj17EsnN95A1gqWM4V0ps77J-myqx3EwbB7M-fE9RdDqYQKMNZRnkyyHBak%3D%40protonmail.com.
