/h, --help show this help message
/b, --batch run batch immediately
/p, --parallel run batch projects in parallel
/d, --delete delete *.pto files after stitching
/o, --overwrite overwrite previous files without asking
/s, --shutdown shutdown computer after batch is complete
/v, --verbose show verbose output when processing projects
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAEBXXD9ApW63eJqYrxA4wJoGYGdW-zRBoF5%3DXxQhp5ZOWwShMA%40mail.gmail.com.
Each .pto files is ony 6 files with 5 MB each. But a real lot of .pto files.I am using --parallel with as many .pto files as there are cores.Performance:
Is that the right setting for best performance?
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c8837042-9a20-46b0-a18f-e55d1addb68b%40googlegroups.com.
Running as many batches in parallel as there are cores is the most permanent setup I found.- fast SSD.- lots of RAM,Hi Thomas,you nailed it.- 64 bit Windows,
I have
I just posted a bounty today for a command-line option to "shut down PTBatcherGUI when done" at this list.An option for the temp folder would be nice too.
JanOn Tue, Jul 23, 2013 at 5:58 PM, T. Modes <Thomas...@gmx.de> wrote:
Am Samstag, 20. Juli 2013 21:01:03 UTC+2 schrieb Jan Martin:Each .pto files is ony 6 files with 5 MB each. But a real lot of .pto files.I am using --parallel with as many .pto files as there are cores.Performance:
Is that the right setting for best performance?
The single programs are not designed to run in several instances parallel.
They (nona, enblend, enfuse) are using as much threads as there are cores and consume a lot of memory.
For the first point you can limit the number of threads to one in the Hugin settings. But this does not solve the problem with the memory usage.
So I would not recommend to run several instances parallel (except you have a lot of free memory, a very fast hard disc and a 64-bit version).
Thomas