Hi Seth,
Sorry.
you are completely right. I read the comment and saw the hash mark and
jumped too fast to conclusions.
I'll have a look again this weekend.
Harry
2009/4/16 Seth Berrier seth.berr...@gmail.com
Are you sure?
In C/C++ lines are commented out only with '//' or with '/* ... */'.
On Fri, Apr 17, 2009 at 15:46, Oskar Sander oskar.san...@gmail.com wrote:
I ran into the same problem (evidently) with the max-number of images
for CP-generation in Hugin as have been discussed here the last few
days. [...]
How do you sole these types of CP-problems, or am I alone in getting
Hi Oskar,
If you have lots of sky/clouds in your pano, you can remove unwanted CPs
from these areas using celeste:
http://wiki.panotools.org/Using_Celeste_with_hugin
You can use the command line version too which is probably more suitable
given then number of images you have:
Thanks Seb!
How do you do that practically, do you selectively pick the images to
search for control points between somehow? (How do you do that in
Hugin?)
Do you also uncheck the previously optimized images in the next
optimization run to make sure they stay put, or can Hugin handle it
just
Do you also uncheck the previously optimized images in the next
optimization run to make sure they stay put, or can Hugin handle it
just doing minor adjustments to them? I guess tension would build
up in the pano as it grows otherwise?
No, I keep the previously optimized images as well.
Hi Bob,
With regard to the 0.7 version. That one doesn't work correctly on the G4/G5
in the final stitching stage depending whether you are on Tiger or Leopard.
The early 0.8 versions don't stitch either on G4/G5 depedning whether you
have Leopard or Tiger.
If you pick one of the later 0.8
I think this may be somthing for Pablo to comment on.
I'm browsing the code to understand atooptimize modes (thinking about
the pairwise optimization, but for other parametes than y,p,r).
And came to think whether visualizing or searching the imagegraph
(that is used in the optimize) is a good
I've been browsing the code now for a while, and can't really see that
It would be a problem to make a variant of Pairwise, which invokes
autoOptimize with the parameters r p and y in which I would
like to call d and e in one case and d e r and v in
another.
Reading autoOptimize in
