Hi David,
I have finally tested the 0.31beta on FreeBSD and it looks pretty ok. Maybe
it could be good to add a note on the build.txt file to also use the
options "-I/usr/local/include -L/usr/local/lib" to compile it on FreeBSD.
Thanks!
Carlos E G Carvalho (Cartola)
http://cartola.org/360
201
> TGA may be nice compression wise, but I don't think this format is as
> widely known as TIFF or PNG, so I'd opt for using the latter. Note that
> this is pretty straightforward when using (for example) the freeimage
> library (as opposed to using functions from libtiff or libjpeg directly).
Hi David,
I think I may have seen it, and meant to reply one day, but then I forgot...
>
No problem :)
>
> Anyway, I will look into adding your MCE support for the next version -
> thanks for those.
>
Since the project has been renamed to "MXE" instead of "MCE" we'd probably
better call it
On Tue 24-Apr-2012 at 17:49 -0300, Carlos Eduardo G. Carvalho (Cartola) wrote:
And I guess this is not only on linux. In general it is used like
this. I guess a better next number would have been 0.3.1 to do
what you meant. Just a suggestion, not a complain, ok? Thanks for
your valuable job!
And I guess this is not only on linux. In general it is used like this. I
guess a better next number would have been 0.3.1 to do what you meant. Just
a suggestion, not a complain, ok? Thanks for your valuable job!
Cheers,
Carlos E G Carvalho (Cartola)
http://cartola.org/360
2012/4/24 Bruno Pos
On Tue 24-Apr-2012 at 03:06 -0700, David Horman wrote:
Anyway, I will look into adding your MCE support for the next
version - thanks for those.
Just one incredibly minor point: your last two releases were 0.3 and
0.31. Packaging systems for Linux actually use these numbers to
decide which
Hi Bart,
I think I may have seen it, and meant to reply one day, but then I forgot...
Anyway, I will look into adding your MCE support for the next version -
thanks for those. Just curious, why is -lz necessary in the build script?
I will add seam saving/loading soon as well, but I will use TGA
Hi David,
Have you missed the contributions I posted earlier [0] (probably) or are
you just ignoring it (unlikely)?
[0] https://groups.google.com/d/msg/hugin-ptx/JPiViZQ-Ycw/4ygfvPVq4hgJ
--
Bart
On Tuesday, March 27, 2012 1:01:56 AM UTC+2, Monkey wrote:
>
> Hi all,
>
> Previous discussion:
Hi David,
Thanks for the reply!
Ok, I tried multiblend with my another panorama on several systems. Maybe
you will find this useful:
Ubuntu x64 - works with any number of levels
Ubuntu x32 - works with 1 level, doesn't work with 2 levels.
Windows Vista x64 - works with any number of levels
Window
Hi Evgeny,
Memory usage is definitely an area where multiblend needs improvement.
At the point it's failing, it's trying to malloc 164mb to store the one of
the channels of the output image. This isn't much compared to the ~1.4gb
it's already using, which makes me think you're using a 32-bit bu
Hi, David,
How much memory does it need for blending with L levels?
I have a huge wide cylindrical panorama 72076x2278.
When all the images are loaded, multiblend consumes up to 1.4 GB out of my
total 4 GB.
The program only works with 1 level (-l 1). Otherwise, I get the following
error:
"
72076x
Some pseudowrapping bugs cleared up (including one that *created* a seam in
the middle - oops!) - now at version 0.31beta.
Windows binaries: http://horman.net/multiblend/multiblend0.31beta.zip
Source for Linux/Mac/FreeBSD etc:
http://horman.net/multiblend/multiblend0.31beta.tar.gz
David
On Tu
12 matches
Mail list logo