Hi,
I finally got around to update my system to debian 7 including a newer
version of the boost libraries. As a result I can't reproduce my
previous artifacts any more.
Sorry for my noise, I marked my ticket as fixed ... anyhow I lerned a
bit about how the blending works.
cheers, lukas
** Chan
Please work on the _tips_ of either the development branch
(currently: http://hg.code.sf.net/p/enblend/code/rev/b0b27f8c7de1)
or the stable branch (currently:
http://hg.code.sf.net/p/enblend/code/rev/881360218998),
for your version is
(i) ancient, i.e. we won't fix anything there anyhow and
(ii) i
>> Is there anything I can do to find out what
>> what causes my black areas?
> Depends on how masochistic you are. If
> the packaged version 4.1.1 or switching to the
> stable branch fixes the bug you could call it a
> day. Otherwise, use e.g. `--save-masks' or
> `--optimize --visualiz
> ... choosing nft doesn't make a difference
> with respect to my problem
You are using a pre-release of Enblend
version 4.1. Therefore, your default PSG is
NFT, I'm on the development tip and GC is the
default here, thus I had to force NFT and you
found no differences. Makes sense.
>
I think the problem I'm having is the same as
https://bugs.launchpad.net/enblend/+bug/766501 and
https://bugs.launchpad.net/enblend/+bug/785803.
Sorry for the duplication, but, for what it's worth, my example is
shorter and the bug is definitely still there (was there a few month
ago, anyway).
I
I had a look at the used seams, with and without optimization.
Obviously there is something wrong with the optimization.
The two seams I obtained are attached, the photos are the same but in a
higher resolution. Using the same resolution as before reveals the same
problem but it's a bit harder t
Hi Christoph,
I just tried blending my three photos using the options you suggested:
Disabling optimization get's rid of all artifacts, choosing nft doesn't
make a difference (with respect to my problem).
Would it be a solution for me to turn seam-optimization off by default?
Is there anything
FYI,
with enblend 4.0-753b534c819d, I too get "correct" output. Both when I put the
'11 image before or after the '10' image.
(if you load '00 and '10 first, they do not overlap and you get two seams with
'11. But if you load 00, then 11, you have one seam, and another seam once you
load '10.
Thanks for the _really_ minimal example. ;)
I tried the following spell:
$ enblend --fine-mask --no-optimize --primary-seam-generator=nft
img_7306-731700*.tif
with the tip of the development branch and got the following warning
enblend: images do not overlap - they will be combined witho
** Attachment added: "Enblend output image"
https://bugs.launchpad.net/enblend/+bug/1153546/+attachment/3568485/+files/a.tif
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1153546
Title:
bl
I might specify, I'm running a Debian 6.0.7, Kernel 3.7.1. There is
plenty of free memory.
cheers, lukas
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1153546
Title:
black artifacts after bl
11 matches
Mail list logo
