Stefan, Thanks for these comments ... I installed the extra RAM this afternoon ... I'll investigate separately how MacOSX handles overall virtual memory size ~ I THINK it is set at start-up rather than installation ... but I have never tried to override the OS defaults ... so I will investigate.
Anyway ... as I said I installed the extra RAM and the G5 now has 7Gb. Immediately on restart I launched a stitch of one of the troublesome projects - not the Village_Hotel project that has been mentioned here but a much simpler one that is just 9 images (no exposure bracketing) and Alpha Channel Masks on three of the images - the photographer's feet in the two down shots and moving person on one one of the horizontal image overlaps. I set the stitch going at Hugin's recommended maximum size which was roughly 12,080x604. The extra RAM made a huge difference in processing time ... I would have previously expected this size of stitch to take several hours but instead it took only 20 minutes or so to reach the crash point. So it is sort of, good-news/bad-news. ... adding extra RAM makes the problematic project crash faster! I just ran it with the usual defaults - tomorrow I will try the parameters that you suggested yesterday. all the best George On Oct 10, 4:27 pm, Stefan Peter <[email protected]> wrote: > Hi George > > Thank you for the info. I' sure that adding 2 GB of RAM will help you > with your current pano. But it will only shift the pano size limit up a > notch, it will not solve the problem per se. I think that it should be > possible to enblend or enfuse images of any size with a given amount of > RAM, although you may have to pay the price of increased computation > time in return. > > Instead of adding RAM to your system, another solution may be to > increase the SWAP size (sometimes dubbed virtual memory or page cache) > of your system. > I don't know how this is handled under OSX; Under Linux, you use special > harddisk partitions for this purpose (but you can use files, too). They > are created during the installation and it is recommended to use a size > of about 50% of your RAM size for swap. The background of this is, if > the swap area is to large, it may happen that a system starts being > occupied mainly with moving pages from RAM to swap and back. This is > called thrashing and results in a system that does not or only very > slowly to your commands. > > In this respect, I think it may be a good idea to check out your swap > settings. From the fact that you will have to remove 2x256MB, I suppose > you started wit 0.5 GB of main memory. If the size of the swap space was > fixed upon installation, you would have a meager 256MB if the 50% of RAM > size rule is used under OSX, too. With the new RAM size of 7 GBytes, you > should be able to extend that to 3.5 GBytes. In this case, enblend would > throw you the dreaded memory error only when the memory requirements of > all running applications and the OS exceed 10 GB. > > Regards > > Stefan Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
