Hi Emad, On September 25, 2010 02:09:49 am Emad ud din Btt wrote: > First I load images into Autopano Pro Trial and get this first image in > very less time. Than I export its PTO file. Load it in hugin and its final > image is still intact or pre-alligned. Autopano removes CPs. I manually > add more CPs or sometimes I dont have to add any Cp. It works. Hugin > really takes hours for my 5 row panoramas for first image and still it > produces strange results.
why the whole workarounds? if Autopano Pro (APP) is useful to you, you should consider buying a license. > My intention is not to do comparison but to highlight this bug/issue. I have not run APP in a while (and not in trial mode anyway, I did buy a license), so I am not sure if you are using Hugin's optimizer based on APP's CPs, or if you are feeding into Hugin an already optimized project from APP and only using Hugin (actually: Enblend) to blend it. If you want to use Hugin throught the process, you need to understand what goes wrong where in your process. Start by running CP generation from Hugin. Don't optimize yet. Don't use the wizard tab. Look in the CP tab (where you enter CPs manually) and check if the generated CPs are plausible. Next step is the optimization. Open the Fast Preview before running the optimization and check if the positioning of the pictures in the Fast Preview looks plausible. I am pretty sure that it is not a bug with Hugin, but rather an issue with your process - wether it is one of the tools that is not configured well (CP detector); or an input that is missing, I can bet you that if APP aligns it, a properly configured and operated Hugin can align it too. Yuv
signature.asc
Description: This is a digitally signed message part.
