> > > > It feels like this should be easy using Hugin or PTGUI: At the end of the > day, I've got very accurate keypoints, and I *should* be able to get an > accurate lens model from them... right? And once I have an accurate lens > model, I should be able to get each frame's yaw/pitch/roll with sub-pixel > accuracy. And then I... er... need help. How do I use this model + a > frame's yaw/pitch/roll to get source pixel locations for the final frame, > that is pretty much what the final stitcher is doing, true? So I'd need to > reimplement my own emblend? Any easier way? >
What is the end goal? As for getting the correct lens numbers if you have a full 360, it should be able to get them at least when shot in daylight. I am not too sure with what you are doing how much the sky may have moved between your first shot and last shot or if it would even matter when figuring out the lens numbers. -- 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/c8655dfa-9822-4313-b440-9d09c3adbd95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
