Enblend

Bug #1384674
Comment #1

Comment 1 for bug 1384674

Revision history for this message

Yuv (yuv) wrote on 2014-10-23: Re: [Bug 1384674] [NEW] enblend running out of temp space: poor diagnostics and configuration possibilities

Hi Richard,

Thanks for reporting.

On 14-10-23 07:27 AM, Richard Z. wrote:
> this is mostly a duplicate of
> https://bugs.launchpad.net/enblend/+bug/1220523.

Let's find out.
(1) what system are you on? the bug being filed in Enblend and
hugin(Ubuntu) leads me to believe it is Ubuntu, but there is a new
version of Ubuntu out every six months, and it would also be helpful to
know on which architecture you are on.

(2) where did you get Enblend from? which version is it? `enblend -V`

if the version of enblend on your system is one with the image cache
activated like in the bug report you point to, it is obsolete. I have
been away for a few years from enblend, but I think I have seen a
message in the flow saying that the image cache will be phased out
because it does not play nicely with other features of enblend.

if you built it yourself, look at the comment preceding the last block
of commands in
<http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Building_Enblend>.

> I would like to add that the diagnostic messages and documentation could
> be a lot better in this situation.

Nobody is perfect, sorry for that. Patches are always welcome. In a
similar spirit, you will forgive my pun, but there is too much analogy
between enblend's diagnostic messages and your bug report:

I would like to add that the diagnostic messages in your bug report
could be a lot better in this situation too ;-)

> Instead of "enblend: No space left on device" it would be much more
> helpfull to say *which device/dricetory* as this does not appear
> documented anywhere.

Instead of jumping to the conclusion that this is most likely a
duplicate of a bug that has been declared invalid (which would lead the
developers to declare this bug invalid too for the exact same reason) it
would be much more helpful to say *which system/enblend version* as this
does not appear documented anywhere.

> Furthermore, is this device hardcoded in the source code or is it
> configurable somewhere? Again, did not find anything in the
> documentation.
>
> Finally, this just happened to me with
> $ df /tmp/
> Filesystem 1K-blocks Used Available Use% Mounted on
> tmpfs 1028148 924 1027224 1% /tmp
>
> and trying to stitch together 31 images. It would seem that similar
> situations may become increasingly common in the near future.

`df -h` would have been user friendlier. So you have 1GB of /tmp space.
Have you tried the option "-m 1000000MB" ? How many megapixel each
image? What bit depth? 1GB of image cache would not be enough to stich
31 of the images I used to stitch a few years back.

Anyway, I hope you take this reply with humour. If you want to help
solve the problem, look at the Wiki page linked above, follow the
instructions to build your own version of enblend without image cache
and report back how it does. I see that there has not been any newer
version of enblend in the Hugin PPA
<https://launchpad.net/~hugin/+archive/ubuntu/hugin-builds> and maybe it
is time that we put one out there.

Thanks for bearing with me.
Regards,
Yuv

Hi Richard,

Thanks for reporting.

On 14-10-23 07:27 AM, Richard Z. wrote:
> this is mostly a duplicate of
> https://bugs.launchpad.net/enblend/+bug/1220523.

Let's find out.
(1) what system are you on?  the bug being filed in Enblend and
hugin(Ubuntu) leads me to believe it is Ubuntu, but there is a new
version of Ubuntu out every six months, and it would also be helpful to
know on which architecture you are on.

(2) where did you get Enblend from?  which version is it? `enblend -V`

if the version of enblend on your system is one with the image cache
activated like in the bug report you point to, it is obsolete.  I have
been away for a few years from enblend, but I think I have seen a
message in the flow saying that the image cache will be phased out
because it does not play nicely with other features of enblend.

if you built it yourself, look at the comment preceding the last block
of commands in
<http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Building_Enblend>.

> I would like to add that the diagnostic messages and documentation could
> be a lot better in this situation.

Nobody is perfect, sorry for that.  Patches are always welcome.  In a
similar spirit, you will forgive my pun, but there is too much analogy
between enblend's diagnostic messages and your bug report:

I would like to add that the diagnostic messages in your bug report
could be a lot better in this situation too ;-)

> Instead of "enblend: No space left on device" it would be much more
> helpfull to say *which device/dricetory* as this does not appear
> documented anywhere.

> Furthermore, is this device hardcoded in the source code or is it
> configurable somewhere? Again, did not find anything in the
> documentation.
> 
> Finally, this just happened to me with 
> $ df /tmp/
> Filesystem     1K-blocks  Used Available Use% Mounted on
> tmpfs            1028148   924   1027224   1% /tmp
> 
> and trying to stitch together 31 images. It would seem that similar
> situations may become increasingly common in the near future.

`df -h` would have been user friendlier.  So you have 1GB of /tmp space.
 Have you tried the option "-m 1000000MB" ?  How many megapixel each
image?  What bit depth?  1GB of image cache would not be enough to stich
31 of the images I used to stitch a few years back.

Anyway, I hope you take this reply with humour.  If you want to help
solve the problem, look at the Wiki page linked above, follow the
instructions to build your own version of enblend without image cache
and report back how it does.  I see that there has not been any newer
version of enblend in the Hugin PPA
<https://launchpad.net/~hugin/+archive/ubuntu/hugin-builds> and maybe it
is time that we put one out there.

Thanks for bearing with me.
Regards,
Yuv