> > USB 2.0 > > I'll copy to local disk and retry. Thanks for the input. >
I don't think it matters much, unless you keep your swap file there. I didn't notice you mentioned how much ram you have installed? That would be the bottleneck for sure. In any case, you can run enblend withe the -v (verbose) argument and see how much memory it needs for each seam. I saw it go up to 8500mb for my last pano (47000x12000, 75x13mp) so if you have less it will take ages while it swaps. Though I'd be very much interested in a way to speed up or optimize the process. BTW, I'm just in the process of installing Vista x64 on one computer, is Enblend 64 bit ready? On Jul 29, 5:09 am, Nicolas Pelletier <[email protected]> wrote: > Update, still goes about same speed. What I don't like is seeing enfuse work > for hours, with 1.3 to 1.8 gigs of ram, and nothing more than 2-4% cpu (out > of 25% for a single thread). > Any advice for speeding this up? > > And the question is still open for those who make gigapixels panorama... how > log does the whole process take? > > Thanks, > > nick > > On Mon, Jul 27, 2009 at 9:34 PM, Nicolas Pelletier < > > [email protected]> wrote: > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
