 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Hello!
I've a problem while stitching an 360x180 Image I've shoot a week ago. I have 256 Images with a resolution of 1280x1024. I shoot in rows, but didn't count exactly how much i made. And they are not very straight because i had to make the photos without any helpings... I'm sure I have an overlap of 50-70% between each image and each row.
Ok, now to my problem: The Conrol-Points are extracted perfectly. But if the program tries to render the preview, the program hnags up on the step "Positioning". It's not the first time I'm rendering panoramas in that size and with that amount of images using autopano, so i don't have the smallest idea what is going wrong...
Any help would be very nice! 
Mefisto
Offline
Mefisto wrote:
Hello!
I've a problem while stitching an 360x180 Image I've shoot a week ago. I have 256 Images with a resolution of 1280x1024. I shoot in rows, but didn't count exactly how much i made. And they are not very straight because i had to make the photos without any helpings... I'm sure I have an overlap of 50-70% between each image and each row.
Ok, now to my problem: The Conrol-Points are extracted perfectly. But if the program tries to render the preview, the program hnags up on the step "Positioning". It's not the first time I'm rendering panoramas in that size and with that amount of images using autopano, so i don't have the smallest idea what is going wrong...
Any help would be very nice!
Mefisto
How long did you wait? With that kind of pictures (heavy overlap shot without nodal-head) positioning can take a while.
Please give some information about your hardware - that mybe related to your problem.
256 images usually need much RAM and plenty of free disk-space. And ideally a real fast machine . .
best, Klaus
Last edited by klausesser (2008-10-29 13:58:21)
Offline
Ok, some data:
OS: Linux Kubuntu 8.04.1 using KDE 3.5.10
RAM: 1GB
Free Disk Space: 30GB (should be enough 
)
I had Panoramas with almost the same amount of images and the same overlap that were made freehand and they were rendered in half an hour. For this panorama I waited over 2 hours, then i have had enough and aborted the whole prozess via the systemcontrol because i wasn't able to close the program manually...
Offline
AlexandreJ would be best here, but:
a- 30GB is not a lot.
b- keep your preview resolution small, I use 1600x1200 max.
What APP version?
Please confirm that you are talking about waiting for the PREVIEW in the PANORAMA EDITOR and NOT for the whole final panorama to render.
Offline
Seems a memory issue for me. 256 images panorama is a lot for just 1 giga. It has nothing to do with the rendering, it's the optimization stage that uses a lot of memory proportional to the number of input images. BTW : with v1.9, this has been improved a lot.
2nd though : disable lens distortion correction. It could lead to such issue too.
Offline
Ok, thanks for the help right here.
I'm waiting for the PREVIEW, not the final image. I'm using autopano 1.4.2. and it stops on the "Positioning" stage, not the optimizing stage...
I will give your tipps a try
Offline
Oh sorry : positioning stage is a part of optimization in fact.
BTW : uncheck robust algorithm in optimization
Offline
Ok, i reduced the amount of images, because i had a overlaping of over 90% very often... that is not neccessary... no i have only 150 images left, i will try it again if the other panorama i'm currently rendering is finished...
Offline
Mefisto wrote:
Ok, i reduced the amount of images, because i had a overlaping of over 90% very often... that is not neccessary... no i have only 150 images left, i will try it again if the other panorama i'm currently rendering is finished...
again: you need more RAM!! And more diskspace.
with 150 images you better have 4GB RAM for the positioning/optimizing stage (which you see in trhe preview) and about 60GB free diskspace as a minimum. Diskspace should be preferably a diskrete volume which is used ONLY for APP-temp.
What Alexandre said is vital: lenscorrection and robust algo is hard stuff for your machine.
Last edited by klausesser (2008-10-29 17:01:29)
Offline
