Just installed APT 1.1 beta 10 on my 27" i7 iMac.Loaded a fairly big tour (19 pano's 8000x16000px)set export to low res for testingWhile exporting to flash my computer almost comes to a grinding haltEven simple things as browsing or reading email become almost impossibleI switched to another computer to post this message.Before this I restarted the computer, set preferences to use 3 cores instead of 8It is rendering for more than an hour now, hope it finishes soonHans

Like the number of cores used, the memory has a big influence on the speed of the software. What's more, in beta 10 we set up the export to be monothreaded when the image do not fit in memory, so be sure to max up this value.What file type do you use? tiff, psd are huge in memory

You can try to rollback to beta 7, wich is the one just before the new image handling system. But I don't know if this version can handle such a big pano.

Adrien F wrote:Like the number of cores used, the memory has a big influence on the speed of the software. What's more, in beta 10 we set up the export to be monothreaded when the image do not fit in memory, so be sure to max up this value.What file type do you use? tiff, psd are huge in memory

You can try to rollback to beta 7, wich is the one just before the new image handling system. But I don't know if this version can handle such a big pano.

Adrien,

I've rather lost track of what Kolor's plans are for APT regarding the ability to handle very large panos - gigapixel images - and very large tours comprising many large panos.

Is the mono-threading export for larger images - a change introduced in beta 10 - a long term 'solution' or merely a temporary 'fix' to overcome the excessive output times experienced with some earlier versions?

I think I found the couse of the problemI started the project in version 1.0.9 and opened it in 1.1b10When starting a project from scratch there seems to be no problemJust finished a smaller project and try the big one fresh next week(sigh, so much work down the drain)

mediavets wrote:Is the mono-threading export for larger images - a change introduced in beta 10 - a long term 'solution' or merely a temporary 'fix' to overcome the excessive output times experienced with some earlier versions?

This is a 'temporary fix' as you call it. Multithreading tasks raises its pack of specific problems we try to overcome. However, instead of letting the whole software monothreaded, we decided to let the user benefits from multithreading when this later is profitable. While we look for long term acceptable solutions.