Something simple I'm doing wrong with 360 pano: sideways/upside images?

[clepsydrae]

I've successfully stitched panos and aligned stacks and such in the past with hugin, but I'm newly on version 2020.0.0.2f576e5d5b4a (Kubuntu 21.10)

I open hugin, add 36 images (taken with canon 10-18 at 10mm, portrait orientation, on EOS-100D, exported from Canon software to 16bit TIFF). These are just me turning in a circle, nothing too crazy, plus a couple extra images higher/lower than the horizon. I set the Lens type to equirectangular.

Focal length shows as expected: 10mm, multiplier 1.62.

I find CPs with CPFind+celeste. It finds ~1600 CPs. They look very good, in general. Maybe 10 CPs in the clouds (which I removed manually once, but not on other attempts) -- generally good, no crazy CPs.

I optimize (tried Positions and View, Positions/View/Barrel, and Everything without translation). I go to View->Control Points to check things out and roughly half of the images are now turned sideways, upside down, etc. These are all images that had sensible CPs in them. They still do, but all the CPs are of course sideways now (still in correct positions). There is only visual gibberish in the panosphere.

Any tips as to what I'm doing wrong? Everything seems to be working perfectly until the optimization. Thanks!

[Luís Henrique Camargo Quiroz]

 

   Hi,

   This seems very strange to me. If the images which remained in a horizontal position also have sensible CPs, as the turned sideways have, then at least there must be some big errors, or else the initial and final image from your circle are missing CPs in between. Please check this, and maybe try some manual CPs yourself (more CPs) to force the circle to close.

    Could you share just the project file?

    Have you closely examined when the sequence turns from horizontal to vertical? There must be wrong CPs there, or a very close group of CPs ; spread them, trying to make the images harder to rotate.   

    Well, don't forget to reset positions before you try again. Also, check if the EXIF data and lens parameters are good.

    Let's see what happens,

    regards,

   Luís Henrique

--
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 hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/0dd2e2a6-5196-4e4c-86c7-6cb9d69e21a7n%40googlegroups.com.

--

--
Luis Henrique Camargo Quiroz
http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg
http://panoramaslh.net/

[clepsydrae]

Thanks for the response! -- Turns out I was too quick to describe the CPs as "sensible" -- I paid closer attention, did some tests, etc, and as you say, with the problematic images there were some pairs of images with clusters of CPs that were pretty close to each other. I am still surprised that it managed to rotate the images, but I can see that better CPs would solve things. Indeed, I did a run (after lining the images up roughly) with CPfind using "--celeste --prealign" and it worked well.

So, user error, as usual. :-)

Thanks.