Re: [hugin-ptx] 360 degree panorama *very* distorted
On Monday, August 20, 2012 3:13:18 AM UTC+3, Luís Henrique Camargo Quiroz wrote: Hi Marcus! Have you checked if the first and last images have control points linking them togheter? Yes. Many times I do my first optimization of yaw and pitch only, leaving roll=0, perhaps this could help you; further optimizations can/should consider roll, of course, but your values seen fine I did that. First only yaw for all except my position anchor image, then only pitch, then both yaw and pitch, then yaw, pitch and roll. Then I deselect yaw, pitch and roll when I optimize the other values, then deselect the other values and re-optimize yaw, pitch and roll, etc. HAHA! please, turn off the translations X, Y and Z, they should be used only for flat images, aka mosaics. Why? I thought they were for if I move the location of the camera between taking the pictures, which I indeed did (although not by very much in relation to the distance of what I took pictures of). Anyway, doing the whole optimization from scratch for the fourth time, now leaving x, y and z zeroed, seemed to have fixed it. Cheers, Marcus -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] 360 degree panorama *very* distorted
On Monday, August 20, 2012 7:25:58 AM UTC+3, Groogle wrote: On Sunday, 19 August 2012 at 15:57:27 -0700, Marcus Sundman wrote: Hi, This is probably something simple, but I really can't figure out what I'm doing wrong. In hugin I have 15 images connected using 421 control points (mean error 0.2px, max 2.4). After the optimization the images range from yaw=-133.7 to yaw=173.4. That's ~307 degrees, but why not 360? It's difficult to say without knowing how you took these images. The yaw values in the image tab suggest that you did not space them equally. That could be part of the bug, of course. They are not spaced equally. Some are even completely on top of each other (but with different exposure, for exposure fusion). Clearly something has gone wrong with the control point detection, something that the detector doesn't recognize. Try looking at the control point window to see the control points between adjacent images (i.e. start with images 0 and 1, then move on until you get to the end (14 and 0). Nope. Before I even started to optimize things I went through *all* control points for all 120 combinations of image pairs (including pairs of the same image). Some bad points I removed, some I refined, and then I also added some points. The final image becomes extremely distorted. After changing the field of view to 360x80 the stiching produces this: ... What does the fast panorama preview look like before and after? It looked the same before, just a smaller part of the image. Anyway, doing the optimizations a fourth time from scratch fixed it for me. I don't know what the problem was but now it's gone. :) Cheers, Marcus -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] 360 degree panorama *very* distorted
Hi, This is probably something simple, but I really can't figure out what I'm doing wrong. In hugin I have 15 images connected using 421 control points (mean error 0.2px, max 2.4). After the optimization the images range from yaw=-133.7 to yaw=173.4. That's ~307 degrees, but why not 360? 307 degrees is close, but now when I press Calculate Field of View on the Stitcher tab it gives 180x76 which is nowhere close to 360 degrees horizontally. The final image becomes extremely distorted. After changing the field of view to 360x80 the stiching produces this: https://lh3.googleusercontent.com/-kANvDRS4djc/UDFuiSY4NAI/ACY/ZHbUS-XaFcc/s1600/DienteDeInca_blended_fused.png This is supposed to be a landscape, but is so distorted you can't even see that. The image list looks like this: https://lh5.googleusercontent.com/-jPTWT3bvgHk/UDFuqXKOfUI/ACg/TYIq-RCOD9E/s1600/image-list.png Any ideas? -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: 360 degree panorama *very* distorted
Btw, I'm using equirectangular projection for the stitching. -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: coding style
On 5 Aug 2009, at 06:48, Yuval Levy wrote: Unix/Linux line ending (Windows and OSX users have to adapt) OSX has used Unix line breaks natively from the start. There are almost no apps that use old-style MacOS line breaks any more, aside from holdouts like Filemaker Pro. Since Windows and source distributions generally never meet, I wouldn't be too worried about them. Marcus --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] New to Hugin
Hi. I'm used to stitching with both PTMac and PTGui, but out of interest I decided to give Hugin a try. Downloaded v0.7.0 and it all looks very intuitative. I loaded some images taken with a 10.5 fisheye on a Nikon D2X which I successfully stitched in PTGui, just as a test. No joy at all! In 'Assistant' tab I enter 'Full frame fisheye' and 10.5 focal length and 1.5 multiplier. Press 'Align' and it runs through the control point selection process and comes up with a mess. (132 CPs with very bad fit Optimizer might have failed) It also decides to change the lens to 10.25 Fallen at the first hurdle it seems. I'll stick to the software I know but if anyone can get me started it would be good to know. Its just annoying! Thanks, Marcus --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
