Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion merge enblend and multiblend code?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
kevin360  
View profile  
 More options Apr 29 2012, 8:01 am
From: kevin360 <kevin...@yahoo.com>
Date: Sun, 29 Apr 2012 05:01:22 -0700 (PDT)
Local: Sun, Apr 29 2012 8:01 am
Subject: Re: merge enblend and multiblend code?
Is there a way to register multiple blenders like you can feature
matchers?  In the Image tab I can select between different feature
matchers quickly by using the drop down menu for "Settings" under
"Feature Matching".  On the Stitcher tab it would appear I should be
able to do the same thing for Blender because there's a drop down menu
there too, but in the preferences I can only register a single
blender.

What about adding support for that?  Then someone could quickly switch
between blenders and also commandline arguments.  So you could have a
regular enblend, an enblend with --fine-mask set, one with the old
primary seam generator selected, one for multiblend.  Then the user
could quickly select between them just like they can the feature
matcher.

On Apr 28, 5:03 pm, Bruno Postle <br...@postle.net> wrote:

> On Thu 26-Apr-2012 at 20:22 -0700, kevin360 wrote:

> >Has there been any consideration to merging the enblend code and the
> >multiblend code together?  This could either be to actually take the
> >code for multiblend and put into enblend and it's selected by a
> >commandline switch, or enblend could have a commandline switch that
> >would cause it to just call multiblend and pass multiblend the
> >commandline arguments enblend was called with.   This would make it
> >easy to select between the two, just by passing a commandline switch
> >to enblend.

> You can already switch Hugin from using enblend to using multiblend
> in File -> Preferences -> Programs -> Enblend -> Enblend executable.

> The Hugin Windows and OS X installers can include multiblend (if
> they don't already), and if/when multiblend gets added to Linux
> distributions it will probably end up being added as a Hugin
> dependency.  So there is no real reason why enblend and multiblend
> should be merged, it is good to have alternatives and switching in
> Hugin is easy enough.

> --
> Bruno


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.