The bug was what we had discussed on the hugin mailing list four years
ago: https://groups.google.com/g/hugin-ptx/c/IgglWhsUCEQ/m/6bUu_YQpCAAJ
tldr: one may generate a seam line such that pixels are included from an
image that are out of bounds wrt that image.
This fix only affects the blending st
Thanks so much for fixing this bug. What was the underlying problem?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend creates an unexplainable black area.
Status in Enblend
Fixes with changes in #2053287
** Changed in: enblend
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend creates an unexplainable bl
2021-10-21 It still happens
enblend 4.2
command line:
```
enblend -l 3 -f 25280x25280 --compression=NONE -o m.tif --pre-assemble --
m.tif
```
seems `-l 7` is better than `-l 3`
** Attachment added: "Screenshot_2021-10-21_20-18-27.moon.png"
https://bugs.launchpad.net/enblend/+bug/721136
okey so it still randomly happens quite often that I get black areas on
stitching. One set that produces black areas though will produce the
same black areas when retrying. So I now usually work around this issue
by stitching in multiple steps, so split the original ~100 pictures in 5
groups â 20 p
Okey so the enblend that takes 5 minutes without the "--fine-mask"
parameter took 9 hours with it and gave worse results and without.
Now I instead built enblend myself using this
https://aur.archlinux.org/packages/enblend-hg/ with the corrected
repository from here: http://hg.code.sf.net/p/enblen
update: the parameter "--primary-seam-generator=nft" does seem to make
the problem more rare, but right now I have a 360° panorama with a
targeted output size of 119448x6727 pixels which even though I tried
stiching 3 times always gave me black holes.
I'm currently trying the parameters @isaacq su
I just installed hugin 2018.0.0-7 with enblend-enfuse 4.2-4 from the
default repositories on my Manjaro (Arch based) Laptop, and stiched an
wideangle 360° panorama from 32 images. Have 3 large black areas in
output.
I'm now trying the last mentioned workaround "--primary-seam-
generator=nft" after
If this problem is symptom of a rounding error in floating-point
operations? Sometimes small rounding errors add up to a glitch in a game
or a pixel. For details on a place where this happens see Wilkinson's
polynomial.
--
You received this bug notification because you are a member of Hugin
Devel
I encountered this problem (a couple random gray squares in my stitched
image) with Hugin 2016.2.0.be8da0221960.
I tried the workaround in bug #1795269: add --primary-seam-generator=nft
to the enblend parameters, and that made the problem go away.
--
You received this bug notification because yo
I fixed this "hole" thing by using command
enblend --pre-assemble --fine-mask
--primary-seam-generator=nearest-feature-transform -o result.jpg *.tif
"Preassemble" is for avoiding the warning "no overlapping area between inputs"
"Fine mask" is for a better mask detection
"Nearest feature transfo
I'm attaching a set of ten test cases that reproduce this bug. They are
all small images so the whole thing runs in five seconds on this
machine.
This has been set up so correct output should be ten identical 100%
white images, on this machine I get black artefacts in every output.
** Attachment
I am now fairly successfully stitching maps using hugin on Windows 10.
One issue I have is that using enblend often generates black areas in
the stitched tiff map. When I reported it at
https://groups.google.com/forum/#!topic/hugin-ptx/OdXvko4S5F4 I see this
is a known issue.
If anyone wants to ex
just for traceability (especially since this bug seems to still be
present [I did not check it myself, just inferring from the bug status])
To explain my comments I've used a few links to pictures hosted on my own NAS
reachable through a dyn-dns domain, which is no longer available because they
For bigger panoramas I'm using a self-build enblend (since the enblend
build included in ubuntu fails with larger panoramas with out of memory
exceptions although memory is still available)
This newer enblend then will often give me black areas like those:
http://kaefert.is-a-geek.org/misc/hugin/e
Lukas,
THX for your minimal example! Admittedly, I cannot
reproduce your "foo.tif" with rev 6d6c88dcdc63, i.e.
current tip. I tried any image order, NFT, GC, w/optimizer,
and wo/optimizer. The result _always_ looked ok and
never showed any black areas. Moreover the seam line
(`--visualize'
My minimal example, a Makefile, and the output I get from 'make
test_coarse_nopt_gc' at 6d6c88dc. Now that I look at it again I'm not
entirely sure any more that this is the same bug ... I get not so much
black corners as black borders.
** Attachment added: "minimal example"
https://bugs.laun
@Lukas: (i) GraphCut is absolutely unchanged in 6d6c88dc,
(ii) after its recent re-implementation it is again WIP
according to its author.
Please run with NFT only to see whether this fundamental
step now works any better. BTW, GraphCut uses NFT as an
educated guess.
If you have a reasonably siz
For my testcase (coarse, no-opt, graph-cut) changeset 6d6c88dc doesn't
change anything. The worst artifacts only occur with graph-cut ... this
agrees with what I see in valgrind: There are a number of errors and
the backtrace always goes back to 'A_star' in graphcut. I can, however,
not find the
Check out rev 6d6c88dcdc63 or later. Switch off optimization
and -- at your discretion GraphCut -- to get reliable results.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend
On Sun, Dec 01, 2013 at 07:31:06PM -, Lukas Wirz wrote:
> If I recompile without openmp I get exactly the same output.
> Image_cache has been disabled in 842, so I can't switch that on. I'll
> spend some time having fun with valgrind.
Good idea. Valgrind will be able to find problems when you
If I recompile without openmp I get exactly the same output.
Image_cache has been disabled in 842, so I can't switch that on. I'll
spend some time having fun with valgrind.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https:/
I used to have the strong impression that it was the image_cache that
caused this... Now you are contradicting that feeling.
If you manage to change the configuration (yes/no openmp ... yes/no
imagecache) and isolate the cases where it happens, that would help
locate the problem.
Keep in min
I've been getting these artifacts for the last couple of years on at
least three different machines whenever I compiled enblend myself.
Interestingly I currently have the situation that the version I compile
myself (with openmp and without image_cache) features this bug while the
debian dist packa
Thomas,
How good a debugger are you?
This is a bug where a good programmer/debugger just has to spend a day
or two finding/fixing it.
This bug resides in the image library that allows the image to be moved
to disk if it becomes too large (I forgot its name). So reducing the
output image size wi
I seem to hit this bug on about one in three panoramas I shoot. Can I
help in any way in getting it resolved?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend creates an une
** Changed in: enblend
Status: New => Confirmed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend creates an unexplainable black area.
Status in Enblend:
Confirmed
I increased the resolution of the output and it went away too. (I had
decided not to worry about it for now)
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend creates an unex
Yes this is a long-standing enblend bug. I workaround it by changing the
order of the photos.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblend creates an unexplainable black
oops. I see that I forgot to include the commandline I used. I had
intended to include it. On the other hand. It can't be simpler
enblend t80001.tif t80003.tif -o t8a.tif
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
htt
30 matches
Mail list logo
