We did huge testing of smartblend here on all plateform ( from 1 to 3 gigapixels ) under laptops and desktop 32 and 64 bits. Many time it worked directly without any issue. But sometimes it could crash. The cause is identified under windows. We use file mapping for manipulating big panorama and it appears that this technic is really system hungry. That's a know issue since smartblend was integrated into autopano. Now, with support of motorized head, it becomes really an issue because creating big panorama is far simplier with these hardware. So for the moment, we don't have a real solution but it only happen when doing really large panorama on small configuration ( 32 bits OS with 2 Giga RAM and the system beeing used for something else for example ).
So we have advises on how to achieve gigapixels rendering with smartblend ( BTW : multiband should always work ). - be sure you have a lot of free space on the temp folder. - do you use a lot of cache size ( 128 MB ) is enough in most case. It won't accelerate much the rendering in fact. - reduce the number of core to use ( each core can use from 100 to 400 MB depending on the panorama ) - If you have 4 GB RAM and a 32 bits OS, switch the OS to the 64 bits version. You can then use the 4 GB. That's expecially true for windows ( XP / Vista / Seven ). - if the system hangs a lot, that's normal, it doesn't say that the rendering has crashes. It's a common problem with file mapping, because these functions have a high priority in the system. So if you analyse the load, you can see that quite all the time is spend in the system and not in the application in fact.
Anything that doesn't correspond to such case should work in fact. Typical case we tried here and timing : * Laptop, vista 32 bits, 2 GB RAM, 200 GB free drive ** 1.5 gigapixels, jpeg, smartblend : 12-14 hours ** 1.5 gigapixels, PSB, 16bits, integrated layer, smartblend : 2 days * desktop, linux 64 bits, Q6600, 4 GB RAM, 500 GB free drive ** 1.6 gigapixels, jpeg, smartblend : 3-5 hours * Laptop, mac 64 bits, Macbook pro 4 GB RAM, 150 GB free drive ** 1.5 gigapixels, jpeg, smartblend : 6 hours
We did quite 20 renderings, only one crashed during smartblend on the first configuration. But the same configuration did the same panorama the second time when we launched the rendering again ...
So after having tested a lot, we have a pretty strong idea of what to implement for smartblend 2. This is the big project for end of the year after the HDR.
What's next
We will now concentrate during 3 weeks on only 2 topics : - documentation, new videos tutorial, new features dedicated explaination BTW : you can see the new layout on the wiki. I also would like to introduce a full main category for papywizard. Every comment is welcomed to the documentation sub-forum here : http://www.autopano.net/forum/viewforum.php?id=21 - feature definition and scheduling for next APP/APG/APT release
Je constate que malheureusement le problème de "zoom" dans la fenêtre de l'éditeur de panorama n'est toujours pas résolu dans cette version (APG MacOS 64). Dommage.
Last edited by JarJar on Fri May 15, 2009 11:15 pm, edited 1 time in total.
JarJar wrote:Je constate que malheureusement le problème de "zoom" dans la fenêtre de l'éditeur de panorama n'est toujours pas résolu dans cette version (APG MacOS 64). Dommage.
C'est un problème Qt et nous avons fait remonter les informations mais nous ne pouvons le corriger nous même.
Super ! Je la teste de suite ! Vivement smartblend 2 !
Pour des panoramas de 10 images (fisheyes zuiko 10mp chacune), sur macbook pro récent (4 Go de ram, OSX 10.5.7), tu conseille la version 32 bits ou 64 bits ?
I was really longing for that update... unfortunately, I think I will still have to go back to version 1.4.2 Which is a pity, because the GPU acceleration is fantastic. However: - Why is it so ugly? The file browser is not readable at all, all file names are skrewed. The fonts in the interface remind me windows 3.11 (is it only a pb with linux? Version 1.4.2 was absolutely fine :s I'm using the linux32 version) - I understand that extensive HDR features are for the wealthy people that can afford autopano Giga. However, the basic things in 1.4.2 were quite ok, and I used them quite a few times. Now I can't reload my previous pano with version 2.xx
Bref, c'était mieux avant
NB: this post might sound complaining, and to some extent it is, but it is really meant for improving the software, which I really like, as it introduced me to the exciting world of panoramic pictures You guys are doing a nice work, I just can't wait more to use version 2.00 in production stage!!!
Sony a100, Fujifilm f100fd, keynux YMAX MV sous ubuntu 8.10.
Actually, I dunno if that can help, but the browser pb appears everywhere a file name is displayed: when listing the image names, or in the list of project names when processing the panoramas. So it does not seem to be tighten to the file browser per se. Version 2.00 used to crash when opening the panorama editor, this does not seem to be the case with version 2.01, cool
J.
Sony a100, Fujifilm f100fd, keynux YMAX MV sous ubuntu 8.10.