nasty enblend error

[Jan Martin]

Hi all,

I got a new PC (AMD Phenom II x6, 16 GB RAM, Nvidia GeForce GTX 550 TI, Ubuntu 10.04.3), so I followed
http://wiki.panotools.org/Hugin_Compiling_Ubuntu to the letter to build enblend with GPU compiled in.

While the installed enblend 4.0-753b534c819d does OK, but has no GPU support,
my compiled enblend 4.1-48edb6264ad8 creates the following blending error.

Both when run with or without the --gpu option.

Anyone to the rescue please?

Thanks,
Jan






Alternative image link:
http://www.diy-streetview.org/data/development/20110917/enblend_error.jpg


--
http://www.DIY-streetview.org

[kfj]

On 18 Sep., 10:41, Jan Martin <janmar...@diy-streetview.org> wrote:
> Hi all,
>
> I got a new PC (AMD Phenom II x6, 16 GB RAM, Nvidia GeForce GTX 550 TI,

> Ubuntu 10.04.3), so I followedhttp://wiki.panotools.org/Hugin_Compiling_Ubuntuto the letter to build

> enblend with GPU compiled in.
>
> While the installed enblend 4.0-753b534c819d does OK, but has no GPU
> support,
> my compiled enblend 4.1-48edb6264ad8 creates the following blending error.

> ...

what error do you mean? I suppose it might be you're missing the nadir
image? Probably the same bug I've been complaining about recently. Try
removing masks, changing image order, or stitching with --fine-mask -
or revert to an older version and put up with the lack of new
features.

Kay

[Jan Martin]

This error:

http://www.diy-streetview.org/data/development/20110917/enblend_error_marked.jpg

There is no nadir image at all.
There are no masks.
Changing image order does not help.
--fine-mask does not help.

Jan

--
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 hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--
http://www.DIY-streetview.org

[kfj]

On 18 Sep., 11:18, Jan Martin <janmar...@diy-streetview.org> wrote:
> This error:
>
> http://www.diy-streetview.org/data/development/20110917/enblend_error...

now I see what you mean. Have you tried if it maybe has something to
do with the new blending algorithm? You can switch back to the old
algorithm by adding this parameter to your enblend CL:

--primary-seam-generator=nearest-feature-transform

Kay

[Jan Martin]

I can confirm, that
--primary-seam-generator=nearest-feature-transform
solves this.

It's the new blending algorithm causing this error.

Jan

Kay

--
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 hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--
http://www.DIY-streetview.org

[kfj]

On 18 Sep., 12:43, Jan Martin <janmar...@diy-streetview.org> wrote:
> I can confirm, that
> --primary-seam-generator=nearest-feature-transform
> solves this.
>
> It's the new blending algorithm causing this error.

apart from the new seam generator suffering from the odd hiccough, I
have a feeling that enblend has slowed down altogether, even if used
with the old seam generator. Did you notice a slowdown as well?

Kay

[Rosomack]

Hi Jan,

On 18 Wrz, 12:43, Jan Martin <janmar...@diy-streetview.org> wrote:
> I can confirm, that
> --primary-seam-generator=nearest-feature-transform
> solves this.
>
> It's the new blending algorithm causing this error.
>
> Jan

would you be so kind as to file a bug report along with the image set?

Some bugs may crop up, it's a new algorithm after all. We weren't able
to test each and every possible case, since each pano is different.
It should work well for most cases, but if something goes wrong you
can always fall back to the tried and tested NFT algorithm.

Regards,
Mikolaj