** Changed in: hugin
Milestone: None = 2011.4beta1
** Changed in: hugin
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679512
Title:
Enblend
Fixed quoting of TMP variable in makefile in default branch
** Changed in: hugin
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679512
Title:
Enblend
I have the same problem. Temp directory is not on C: because of low
space so i moved it to D:
** Attachment added: logfile.log
https://bugs.launchpad.net/hugin/+bug/679512/+attachment/2351868/+files/logfile.log
--
You received this bug notification because you are a member of Hugin
I installed Hugin 2011.0.0.0f9fdaf56720 built by Matthew Petroff on my
PC, running under Win 7 Prof-64 bit and 4GB RAM. The system partition is
a SSD with 60GB, so the images are located on a USB-drive with 160GB
free.
Possibly this is a hint: Interestingly the error doesn't depend on the
size of
I have no access to Windows and can not help much, but I think this
report deserves at least to be re-opened and investigated after it has
been recently confirmed by two users, one of whom even provides a
workaround.
What interest me is: what triggers this bug? if it was a generalized
bug, we
I also duplicated this error. My system is also windows 7 64-bit, though i'm
not sure that makes a difference, since i resolved this by using a script to
remove the quotes that hugin is adding to the values of TEMP and TMP
environment variables.
I suspect the windows api calls in enblend.exe
An further update. Am now now having this problem when I run the make
file from the command line.
Not sure if it relevant: I got the LZW compression is not available due to
Unisys patent enforcement error from Enblend.
Does this mean its using uncompressed files and running out of memory?
Just ran into the issue again. This time I copied the failed enblend command
from the error log and ran it on the command line.
It worked without any problems.
Is this information helpful? Enblend failed when it encountered the
first image that wrapped around the 0-360 degree boundary. Could be
enblend got the composition of the TMPDIR variable wrong.
IIRC this has been fixed or is being fixed. Please check that it still
happens on 2010.4.
It fails to make the tmp file NAME. Not that the disk fills after
writing a little bit to the temp file
** Tags added: enblend tmpdir
**
9 matches
Mail list logo
