** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685105
Title:
enblend fails to blend large pano
Status in Enblend:
Fix
** 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/685105
Title:
enblend fails to blend large pano
Status in Enblend:
Fix
THX kaefert for trying out Enblend on large panos. You have
convinced me that we can close this issue, because enblend
fails to blend large pano is not a bug in the program. You
proved that it is plain user incompetence, using wanna-be O/Ss,
or, in summary nothing we can fix.
The sizes of more
Okey, so I've worked around that artefact problem
http://kaefert.is-a-geek.org/misc/hugin/360degree233pics_enblend-failure/artifacts-enblend-4-2/
by using gimp to cut out transperant holes where those artefacts where
and running enblend a second time with this holey panorama and those few
okey, so the enblending of my 240.000 x 8.292 pixel panorama succeed.
The resulting tiff file is a little under 2GB big and sadly does contain
lots of those http://kaefert.is-a-geek.org/misc/hugin
/360degree233pics_enblend-failure/artifacts-enblend-4-2/ artefacts. I
think this artefact problem I
btw., some info that might be useful for other users or maybe also for the
developers:
The sources of this panorama are 229 pictures of 3000x4000pixels.
The highest amount of memory used by enblend was 10GB RAM + 42GB Swap-space.
The enblend process took around 50 hours to finish stiching this
Yes, I've found that things are related to imagecache. On the other
hand, yes, I too have heard that it had been removed. But are you
running such a version? Can you check if you can make the program show
its configuration? (-V? -v?) (I don't know the cmdline options by
heart).
--
You received
couldn't find a way to do that, here is the output of --version and --help
http://pastebin.com/2n4YH8F4
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685105
Title:
enblend fails to blend
The enblend I'm running is compiled from the sources I've got on tuesday from
hg clone http://hg.code.sf.net/p/enblend/code enblend.hg
following those instructions:
http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Building_Enblend
and @ this page:
Okey, so I'm still not ready to let this one go ;)
I've followed this guide: http://wiki.panotools.org/Hugin_Compiling_Ubuntu
To compile and install those on my machine:
libpano13 2.9.19-789hg
enblend 4.2-7bcf8a1e6b3d
hugin 2013.0.0.6337
Now with this setup, trying to create a panorma with more
Okey guys! First I want to thank you all for the useful information you
gave me, especially @rew for the thing with the different lenses.
And secondly If anybody is still interested in debugging the issue of this
bugentry: Today enblend failed on me again - I've been trying to create a
panorama
Thanks Christoph for the detailed response!
But I don't think that I've hit the MAX_INT Pixel limit with my Panoramas.
I'm trying to create 360 degree panoramas with pictures taken with my Canon
Powershot SX280HS which has a 20x zoom lense.
A panorma that covers about 90 degrees of the sky
Oops! Sorry, I was off-by-one in the
exponent. 8-/ The largest _signed_ integer
(`int') typically is 2**31 - 1, not 2**32 - 1.
The latter is correct for _unsigned_ integers
(`unsigned int'). However, your calculation
still holds even with the half-as-large limit.
Another thing that would be
OK -- a few words from your chief
maintainer of Enblend/Enfuse.
1. ImageCache
Any ImageCache support has been removed
from the development branches of Enblend and
Enfuse. It won't come back unless some brave,
brilliant, ... hacker steps up and takes
responsibility for the code. Thus,
It's a makefile.
In Hugin you can select the button: Keep intermediate files. Then: enblend
yourprojectname00*.tif -o tourprojectname.tif should be the enblend commandline.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
Okey, thanks, will use with me continued tests, will make it quicker,
since the nano stuff also takes around an hour every time..
So when I compile enblend (both the version 4.1.1 downloaded from sourceforge
and the version 4.0 from the ubuntu repos) with the option
--enable-image-cache=no it
Is your userspace 32-bit or 64-bit?
A 32-bit userspace program will run out of addressable memory at 3G. So
that's unlikely to exhaust your swap. (in fact it's unlikely to start
filling your swap). But just to be sure
To allow developers to work with your images, are you willing to upload
I think I should be running 64bit
kaefert@ultrablech:~$ uname -a
Linux ultrablech 3.8.0-30-generic #44-Ubuntu SMP Thu Aug 22 20:52:24 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
I just found I was telling you wrong stuff, my total picture count of
this set is not 330 but 233 (so actually I was damn
Downloading for hours? Haven't seen that happen for quite a while. Would
probably download in one minute here... :-)
(download speeds of 11 megabytes per second have been known to occur... :-) At
those speeds, it mostly depends on the server ) (Your upgrade may take a
few hours. Please
well, I'm not at home, therefore got a painfully slow connection here, but you
can download the 15MB reduced files here:
http://kaefert.is-a-geek.org/misc/hugin/360degree233pics_enblend-failure/small/
The first few of the original files are in the parent directory, but the
upload from here to my
You scaled by 0.25, Correct? Then I can scale them back up to normal
size. Which, under most circumstances is very similar to using the
original files.
I also need the hugin project file
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed
yep, correct (I used exactly your code, the only change I made was from *.jpg
to *.JPG)
I've put the project file and a few logfiles in the subdirectory stuff
I've turned on directory listing for this directory, so you can just navigate
there.
--
You received this bug notification because you
Depending on the version of the TIFF format which is used, the limit is
either 4GB, or 18,000 PB.
If you are seeing that error, either the TIFF library you linked against
doesn't support bigTIFF, or for some reason it decided to only use the
old format.
--
You received this bug notification
I'm affected by this bug too (at least that what it seems to me)
I'm using Ubuntu 13.04 and all packages are out of the default repositories.
I have 10GB ram and 20GB swap-space, but somehow the swap didn't get filled
more than 10% when this error happened (which seems kind of strange to me)
For you, I'd think it is easiest to do:
apt-get source enblend
apt-get build-deps enblend
cd enblend-version
dpkg-buildpackage
Now you've rebuilt your distro's version with those options. Now you
have a source directory that you know compiles and you can tune to your
liking.
--
You
btw. -- is there a way to skip the nona part and directly call enblend only?
I found this name.pto.mk file and thought it might be a shellscript, but
running it like a shell script didn't work out that well.
--
You received this bug notification because you are a member of Hugin
Developers,
Okey, so I'm home again. My self-built enblend 4.1.1 failed really fast,
again with the same error:
enblend: out of memory
enblend: std::bad_alloc
But my dstat output of that time shows that the memory was nearly empty...
http://pastebin.com/raw.php?i=B9sjQaK9
So I'm gonna try the compiling
Thanks for your reply.
Finally i did it (enblend did it ;-) ).
BEFORE:
* Due to 16GB Memory and SSD-disk i used a RAM-disk for /tmp.
* Due to SSD (limited space - the big ones are too expensive for me), only
little swap-space on a normal hard-drive.
AFTER (means solution which worked for me):
So: yes it blends when you try it without imagecache and have enough
swap space available. Enblend crashes without any reason according to
your first message. Just enblend was killed is output by make.
Probably segmentation fault is somewhere in there, but lost
I personally stitch at one
On Tue, Apr 05, 2011 at 08:38:43PM -, the_mechanical wrote:
Still no output (enblend built with imagecache)
make -j 4 -f pano.pto.mk NONA='nona -t 1' ENBLEND='enblend -m 6000'
...
enblend: info: loading next image: project0027.tif 1/1
make: *** [project.png] Getötet
make: *** Datei
Just found that this is the master bug, so marked the other one bug
#685903 as duplicate. My source images are downloadable:
http://prive.bitwizard.nl/dsc_3210-dsc_3254_exposure_layers_0018.tif
http://prive.bitwizard.nl/dsc_3210-dsc_3254_exposure_layers_0019.tif
Enblend version 3.2 ran out of memory after 65 images.
It seems that it's the imagecache that should be on during the build
to make it start the big blend.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
32 matches
Mail list logo
