Great news ! Following T. Modes' instructions, I've successfully stitched these image-sets into panoramas using Hugin, and it truly feels magical ! It seems the keypoint is to optimize position first, and then optimize both position and view.
During the process of stitching these panoramas, I've encountered new thoughts and questions: 1. If my input images are in clockwise order and I only want to detect and match keypoints between adjacent images, and the last image also need to match keypoints with the first, how can I achieve this? I noticed a matching strategy called linear match, but it seems can not match the last image's keypoints with the first one. 2. What does 'prealigned' mean in 'CPFind prealigned' ? When should 'prealigned' be used, and is it suitable for the case of creating 360° panorama ? I tried it out, and its matching strategy seems similar to CPFind : [image: hugin-cpfind-prealigned.png] 3.How can I automate the workflow so that I can one-click generate 360° panorama with new image sets in the future? Can this be achieved through a python script or command line? But I've found that my windows computer lacks command line tools of Hugin (e.g. cpfind, PToptimizer, nona etc) and hsi. Do these require extra installation steps? Thanks in advance ! 在2024年5月19日星期日 UTC+8 16:32:48<T. Modes> 写道： > [email protected] schrieb am Sonntag, 19. Mai 2024 um 00:31:33 UTC+2: > > > Following example comes from "Jie-Geng\14_only_ring1" in the image-sets, > the saved .pto is the attachment. > > Is it due to the image overlapping rate, control points or whatever ? > Actually I have tried manually set and check control points, and they looks > reasonable, but I don't know why hugin still can not stitch them correctly. > > The problem is that you optimize the translation parameters for all > images. This does not work. The translation parameters should only optimize > for single images, but not for all (except you know exactly what you do) > I did the follow with this project: > 1. Reset all image positions > 2. Optimize Geometric: Positions (incremental, starting from anchor) > 3. Optimize Geometric: Positions and view (y,pr,rv,) > The results looks reasonable then. The field of view of the images is > reduced from 60 deg to 46 deg. > Not sure if this is related to your attempts or if the initial guess was > wrong. I could not check this because your test images does not contain any > EXIF data. > > BTW, does anyone could share the imageset that can be used to create 360 > panorama easily with hugin ? > > E.g. your example set SSARCandy/libray works fine with Hugin. (I started > with a HFOV of 30 deg because the EXIF data are missing.) > > -- 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/1012db23-cd5d-488c-a5fb-71786f998417n%40googlegroups.com.
