I'm trying to learn a bit more myself, as well as hopefully help. One thing that likely will help explain what is happening: In expert interface, in the photos tab, in the radio buttons on the right, select "positions". Some of the data displayed there should help explain what is going wrong. You can also double click any row and edit the values.
If I understand correctly, yaw, pitch and roll are in degrees. They should all be near zero, but degrees are a small unit, so values like 1 to 5 may be considered near zero. X and Y should hold the major values BUT I don't yet understand what units they are in: In the test I just ran, they must be quite big units because a value of 0.1 is big. On Monday, December 27, 2021 at 7:47:01 AM UTC-5 Jon Schewe wrote: > On Mon, 2021-12-27 at 09:28 +0000, Bruno Postle wrote: > > On Mon, 27 Dec 2021, 00:33 Jon Schewe, wrote: > > On Mon, 2021-12-27 at 00:20 +0000, Bruno Postle wrote: > > > > > I did find that telling Hugin to use separate lenses for each of the 2 > images helps quite a bit. > I stumbled upon this tutorial that suggested using 2 lenses > http://hugin.sourceforge.net/tutorials/scans/en.shtml > > > This is a similar case, but you have handheld photos taken with a camera > (generally called a 'mosaic'), so you have to optimise rotation as well as > translation. > > Note also that you are assembling your images into a plane, so you need to > set the output projection to rectilinear, not equirectangular. > > > When I specify recilinear as the output projection I get a warning from > Hugin "With a wide field of view, panoramas with rectilinear projection get > very stretched towards the edges. For a very wide panorama, try > equirectangular projection instead. You could also try Panini projection.". > > Am I correct this warning doesn't apply because what I'm creating is > technically a "mosaic" instead of a "panorama"? > > > As far as applying translations and images ending up on top of each other. > I've gotten my project into a state where Hugin believes that all images > are on top of each other at the same location. To fix this I'm trying to > optimize just 3 of the images by specifying "only use control points > between activated images" and only have 3 images shown. Each of the images > has plenty of control points linking them and all of the control points > look good. However I get one image at the pole of the sphere and the other > two in the center (where they belong). See the attached screenshot from the > layout window. > > With a small experiment I managed to get into this state by telling Hugin > to optimize X, Y, Z only for the images. It ran the optimize and told me > that the average distance between all control points was zero. At this > point the project appears to be in an unusable state. > > -- 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/7217a42e-30b9-4c4f-95ba-e9838e2aa939n%40googlegroups.com.
