On 13 July 2011 22:46, dbur <[email protected]> wrote: > I just tried it again and now I find it won't go beyond 4095. (Ver > 2011.0.0) > > If I set 4096 it goes to 1 > If I set 5096 it goes to 1000 > If I set 6096 it goes to 2000 > If I set 8096 it goes to 4000 > If I set 8191 it goes to 4095 > If I set 8192 it goes to 1 > > Sounds like MOD 4095 arithmetic in the data entry box? >
Yeah, I think there is something like that because of some deficiency in config handling in wxwidgets. But anyway, it's not necessary to give hugin so much memory. Hugin itself doesn't really need that much . You should, however, add -m 7000 to the enfuse and enblend default arguments (it's in preferences -> programs), because these tools are most memory demanding. This number is better to be smaller than your RAM (ie. not -m 15000 for 8GB machine like karmadillo suggested). The -m switch basically means "you can use up to x MB of memory, if you need more, use enblend's swapping routines to swap not needed images to disk". The memory swapping routines implemented in enblend should perform better than the ones provided by an operating system (which may kick in if you set -m parameter to be bigger than RAM available) and if you leave some space for OS (that's why I recommend it to be smaller) it doesn't end with whole system being unusably slow, only enblend/enfuse should be slowed down. If you are sure you won't go out of memory often you can use enblend build with OpenMP. It is multi-threaded (therefore faster) but it doesn't have these custom memory swapping routines. Lukas -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
