Bart van Andel wrote:
On 11 mrt, 16:45, Simon Oosthoek <[email protected]> wrote:
Simon Oosthoek wrote:
Bruno Postle wrote:
On Wed 10-Mar-2010 at 12:50 +0100, Simon Oosthoek wrote:
When I changed the projection, some projections altered the FoV in
such a way that the output got totally distorted. Switching back to
something sensible didn't always reset the FoV to sensible values.
Wouldn't it make sense to review these functions and prevent
unsensible values to be set, unless confirmed by the user?
There have been a few changes recently to make this better, but
probably Hugin does the wrong thing in a number of situations. There
are hundreds of combinations of projections, a bug report where
people could add examples that don't work well would be useful.
When I have some time, I'll see what I can do, (@anyone) feel free to
start an issue on this, I may not have time soon...
I managed to do it now anyway
;-)https://sourceforge.net/tracker/?func=detail&aid=2968662&group_id=775...
Meanwhile, wouldn't it be a good idea to put a prominent "UNDO"
feature on the windows/tabs that allow you to change aspects that have
effect on the FoV?
the more I think about it, the more I think this is really a bug and
UNDO is not the right way to fix it. The projections shouldn't
fundamentally change properties like FoV, unless I don't understand
something (I'm not into the mathematics of making panorama projections!)
Well, a rectangular projection can only display images with <180
degrees field of view (and 120 degrees for practical use), so for this
projection, the FOV field needs to be modified. This is a mathematical
restriction, so it can't be circumvented. I guess you didn't realize
this? This is exactly what Hugin will do when you switch from a Panini
projection with a large FOV (>180) to rectangular. Nothing strange
about that really.
Perhaps not strange, but when it results in a "broken" image, it is
something to be prevented as a "default" outcome of a change in
projections. Hugin is used by lots of people who have little to no
knowledge about the mathematical background in projections (like me,
even though I have the potential to learn it ;-). For people using hugin
to stitch together their panoramic holiday shots, ending up with weird
incomprehensible results is a big problem. I usually fiddle around or
start over when I get into this kind of "trouble". I also suspect this
has caused a few crashes (I think I even remember some discussions on
this list about this problem years ago), so being more careful in
changing the FoV when manipulating the projections might also be good
for overall stability.
The interface is currently not very helpful in fixing these "broken"
situations, I guess that is my main concern. How the interface can
become better is up for discussion...
/Simon
--
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
