How can I make things just work?

92 views
Skip to first unread message

Mark Roden

unread,
Jul 11, 2015, 12:05:25 AM7/11/15
to hugi...@googlegroups.com
Hi all,

I have two copies of hugin, one from 2012 and one from 2014.  The one from 2012 works perfectly well, and was able to produce stitched panoramas like this one:


That's a stitch of three images.  When I load them into 2014, I get complaints about no control points being set, and the images are entirely out of alignment.  When I load them into 2012, the program Just Works, and I'm able to make panoramas.

So how can I download 2012?  Barring that, how can I make 2014 work automatically like 2012 does?  2014 seems to just misorder the images, not find control points, and generally has a lot less of an automatic feel to it.

Thanks,
Mark

Terry Duell

unread,
Jul 11, 2015, 12:23:30 AM7/11/15
to hugi...@googlegroups.com
Hello Mark,
Hugin-2014 has a different gui to hugin-2012.
There is a basic tutorial on the new gui at
<http://hugin.sourceforge.net/tutorials/new-gui/en.shtml> which might help
you.
Which operating system are you using?
How are you using hugin-2014?
Have you tried setting the interface to "Advanced", and using "Create
control points" in the Photos tab?
If you have the project file (.pto) for the stitch you mention above, have
you tried opening that in hugin-2014 to see if you get the expected result?

Cheers,
Terry
--
Regards,
Terry Duell

Mark Roden

unread,
Jul 11, 2015, 2:21:15 AM7/11/15
to hugi...@googlegroups.com
It seems the big difference is that 2014 no longer runs cp-find to find control points, and that the correlation thresholds are set higher.

When I lower the control threshold to 0.6 from 0.8 and then manually run cpfind, everything works as expected in 2014.

My suggestion would be that, once settings have changed with respect to how points are found, offer to rerun the point finding algorithm.  It may also be worth lowering the threshold for correlation, as shots taken within seconds of each other were apparently not close enough by this metric.

Here's the panorama I was able to produce:


So it is _doable_, it's just not automatic anymore. Ah well.

T. Modes

unread,
Jul 11, 2015, 3:43:02 AM7/11/15
to hugi...@googlegroups.com


Am Samstag, 11. Juli 2015 08:21:15 UTC+2 schrieb Mark Roden:

When I lower the control threshold to 0.6 from 0.8 and then manually run cpfind, everything works as expected in 2014.

My suggestion would be that, once settings have changed with respect to how points are found, offer to rerun the point finding algorithm.  It may also be worth lowering the threshold for correlation, as shots taken within seconds of each other were apparently not close enough by this metric.

The correlation threshold in the preferences is not used by cpfind. It applies only to the cp tab. So changing this threshold has no implication for cpfind and changing it is pointless for cpfind.

You can configure Hugin to automatically align the images after loading: go to preferences, tab assistant and tick option "Align images after loading". Then the images are automatically aligned after loading. I think, this is the option you want.

Mark Roden

unread,
Jul 11, 2015, 9:15:37 AM7/11/15
to hugi...@googlegroups.com
Ah, got it.  

In the spirit of making things easy for the user, then may I suggest that there be a dialog when you first ask that asks if you want to align images after loading?

My problem was, when I went to go align them, the program said that there were no control points.  So the alignment task should also be running cp-find instead of bringing up the manual interface, or at least offering to.

Finally, when I load up on my mac, I get a series of error messages about various debugging services that need to start up, and a failure of a submodule.  I can post those messages if you'd like.

Mark

Carl von Einem

unread,
Jul 13, 2015, 3:41:55 AM7/13/15
to hugi...@googlegroups.com
The current Hugin version 2014.0.0 actually aligns images, I saw that on
a friend's Mac when I showed him a basic workflow for partial panoramas.
He had no old preferences so the Assistant ran in a way intended by the
software developers.

It's often a good idea to "dive into" a new program version
(particularly one that is reported to fancy some major changes) with
default settings.

Either rename Hugin's prefs (open the folder /Users/<your
account>/Library/Preferences/ and rename the file "hugin Preferences" to
e.g. "hugin Preferences.txt") while the application isn't running or
just open Hugin's preferences dialog and reset every tab. The first
option has the advantage that you can look up your old settings.

Carl

Mark Roden wrote on 11.07.15 15:01:
Reply all
Reply to author
Forward
0 new messages