On Apr 17, 3:46 pm, Oskar Sander wrote:
> The second question I have is if absolute HVFO is at all relevant or
> if I can set it to one arbitrary small number in this case.
I tried this a while ago.
It turns out that the FOV parameter on the stitch tab is an integer.
This
is annoying if you
>
>> 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 image
On Fri, Apr 17, 2009 at 16:33, Oskar Sander wrote:
> 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?)
In this case, I know in which order I shot the images: top row first
from left to right, then
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
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:
celeste_standal
On Fri, Apr 17, 2009 at 15:46, Oskar Sander 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
> these?
I find t
