Zoran Zorkic wrote:
Probably because enblend was called with -w -f3000x1500.
Probably. The problem is that enblend doesn't correctly parse the
command line. It expects a MODE setting after -w or --wrap (which are
synonymous). This is somehow contrary to the documentation which says:
Hello Benjamin -
On Sep 9, 12:36 am, Benjamin Schnieders
benjamin.schnied...@gmail.com wrote:
Can you propose a (free) multi-thread profiler for linux? (Looking out
for one for some time now...) If so, I'll have a look at it, enough of
exploiting hugin/panotools now, time to give something
On Sep 8, 12:49 am, Benjamin Schnieders
benjamin.schnied...@gmail.com wrote:
Inspecting the enblend run with top I see that indeed enblend sometimes
uses more than 100% cpu - but never more than like 200%, usually it is
around 100% and from time to time there is a peak using somewhat more.
Hi Chris,
First of all CPU load is a silly
measure.[...] For
a user only wall-clock time matters.
sure. I did not yet take times, but the new version is definitely faster
than the old one. Of course 3 busy-waiting cpus and only one doing
something useful will stress a 4-core cpu
Tested it on some 10 remapped photos:
used enblend -v -o output.tif input*.tif
unless stated otherwise
GPU, SSE2: 108 sec
GPU, SSE2, -m 1900: 85 sec
OPENMP: 63 sec
OPENMP, SSE2: 63 sec
RELEASE: 112 sec
RELEASE, -m 1900: 89 sec
Test machine: Xp sp2 x86, e6...@3.35ghz 4gb ram, nVidia 9800GT 512mb
Continued:
ENBLEND 3.2, -m 1900: 72 sec
Test machine: Xp sp2 x86, e6550 3.35GHz 4gb ram, nVidia 9800GT 512mb,
fairly new drivers
(I just saw that google censored my cpu in the last post :D )
Old, 3.2, was crashing for me a lot lately on bigger projects, I'll
try to test it against this one
Zoran Zorkic wrote:
Tested it on some 10 remapped photos:
used enblend -v -o output.tif input*.tif
unless stated otherwise
GPU, SSE2: 108 sec
GPU, SSE2, -m 1900: 85 sec
OPENMP: 63 sec
OPENMP, SSE2: 63 sec
RELEASE: 112 sec
RELEASE, -m 1900: 89 sec
Test machine: Xp sp2 x86,
Got this after trying to blend a 360x180 from Hugin 2009.1.0.4263:
enblend: unrecognized wrap-around mode -f3000x1500
Probably because enblend was called with -w -f3000x1500.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Fine! I tried the x86 OpenMP, SSE2 version (assuming that this is right
for a core2duo).
I copied just enblend.exe into my hugin/bin directory (latest available
build).
The error I get looks not like it's a problem of MP or the like, its
about an unrecognized wrap-around mode. It won't let me
Sorry, I was too fast posting; I recognized the cause was changed
options syntax for enblend. I have to review my enblend options in
hugin. But this probably means we need new droplets for enblend, too.
regards
Joachim
J. Schneider schrieb:
Fine! I tried the x86 OpenMP, SSE2 version (assuming
10 matches
Mail list logo
