>I'm a hugin rookie but I'm finding on my single processor and 1GB of
>Ram and XP it can take an hour for a pto - depending primarily on the
>size I specify for the output panorama.
>16000 x 8000 pixels won't run - enblend can't allocate sufficient
>memory
>8000 x 4000 runs about half an hour or h
On Feb 24, 7:09 am, Battle wrote:
> What about parallel processing using graphics chips a la cuda?
Advanced use of GPU *that is, beyond accelerated preview dialog) is
certainly interesting, but locking to a particular vendor (CUDA) is
plain wrong ;) Now OpenCL allows both multithreading, use of
Battle
I'm a hugin rookie but I'm finding on my single processor and 1GB of
Ram and XP it can take an hour for a pto - depending primarily on the
size I specify for the output panorama.
16000 x 8000 pixels won't run - enblend can't allocate sufficient
memory
8000 x 4000 runs about half an hour or
On Thu 25-Feb-2010 at 16:35 +0100, Frédéric COIFFIER wrote:
Second problem with Hugin: I can't modify enblend options in the
Hugin interface. If I select the "Options" button in the last tab,
I can see that "-z -v" options are set. But if I change these
options, I validate and I reopen the op
Hello,
I'm using the last trunk version of Hugin and official enblend 4.0 (Linux
platform).
I'm trying to render an old .pto file. In this .pto, I used the "-z" option of
enblend to get the LZW compression :
#hugin_enblendOptions -v -z
First problem with the PTBatcherGUI: without the verbose
