Yuv,
APPro beats Hugin in alignment hands down. There is no contest there. It
matters not what CP detector one uses (with exception of GeoDiasy (untested)).
Feed it the same images from two different directories so there is no
contamination, and APPro comes out on top every time.
In truth, if APPro exports a file in a format Hugin is able to read, it would
be benficial to use APPro first for CP detection and alignment Hugin for fine
tuning the alignment with the use of manual CP and then use smartblend or
enblend to "brush out" unwanted areas.
Hugin has a problem with feature creep. Normally one sees OSS projects with
this issue after it address it's core objective. In truth, Hugin met it's
initial objective (0.7.x) but for whatever reason which users don't understand
and don't have the programming experience to examine code, Hugin isn't
currently accomplishing this goal. I've tested it and posted my results to the
list.
btw, I use ubuntu, built my own LFS system in 2003, had some introduction to
C++ programing in college, wrote some interesting scripts, worked on OS400 CISC
to RISC conversions, etc. and enjoye a good GUI. I sit between worlds,
user/tester/dev/ I'm an oldie who doesn't need to prove anything, but would
enjoy just using the software.
Dale
> From: goo...@levy.ch
> To: hugin-ptx@googlegroups.com
> Subject: Re: [hugin-ptx] Re: Owie
> Date: Mon, 27 Sep 2010 00:06:12 -0400
>
> 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
--
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
