[ptx] Hugin wishlist, RFC

[Mike Runge]

Hi Sebastian,
>
>1. Band blending (or some other intelligent blending)
>
>   Even with setting every capture parameter at my camera to some fixed
value,
>I still end up having differently exposed images that hardly match up, even
>with large feathering. Adjusting brightness kills the blue sky in most
images,
>adjust color paints them pink. Adjusting both does both.
>

Really the last bis issue I have with hugin (or with panotools at all).
Not the vignetting, what I could do with e.g. gimp and a graymask, but I also
have some kind of different exposures even if the single images were take in
manual mode and within a short timeframe. Especially while tilting the cam
that can happen. Equalizing this differences with e.g. gimp is not easy and
time-consuming because it needs to be done individually for each image and I
need to find out first which picture has the 'mid-range exposure'


>3. Automatic panorama control point creation
>
>   Alexandre did a replacement to the keypoints binary (Alexandre: how far
is
>t? Can I help/review?). Though for now I am happy with my version, such a
tool
>shipping with hugin would be great. To be usable for everybody it must
contain
>some geometric matching code, though. The current matching is sufficient
for
>us, as we just get rid of the wrong control points after the first
optimization
>by deleting the worst ones, but a beginner might find this difficult. Also,
it
>must have some penalty function so that clustering of control points is
purged
>in favor of more spacious matches. (That is: the polygon area of all
matching
>control points should be large, not just a small cluster at some easy
features)
>

Well,
currently I'm running hugin on w2k and I'm not able to compile the new stuff
on my own. Hope that some of the latest auto-creation stuff will be available
soon as executable for w2k. 
I'm much more interested to see the auto-creation stuff working for
multiwrows. For single rows the actual picking solution of hugin is very
handy and I don't bother doing that for a single row. But for spherical panos
of large panos with 3 rows a lot of time is needed to set all the points.

>
>4. "Horizon points"
>

I think ptAssembler has some sort of this as well?! Not a big issue for me,
since I take my pics with a tripod and exactly know where the horizon is. But
it would be nice - sure.

>
>5. Unneccessary picture detection
Don't need that. It does not happen very often to me and doing that by hand
is good enough for me. 

>
>6. "Camera profiles"
>
Works for me, because jhead knows my cam and the multiplier. But it would be
nice to have while using converters. A list of editable multipliers/fixed
focal length would work for me.


best, mike



-- 
_________________________________________________________              
Mike Runge
Volksgartenstr. 21 
40227 Duesseldorf
	http://www.trozzreaxxion.net
_________________________________________________________