 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | You are not logged in.
Pages: 1
Hi there,
got a Gigapixel with 2423 images. Gigapan 2.6 crashed when doing the Lens Corrections in optimization state.
Only 4gig RAM of 16 used ...
Any ideas on this?
Andreas
Last edited by Hellkeeper (2012-01-13 13:41:14)
Offline
Hi,
When doing huge gigapixels, you can work differently in optimization stage. Most of the time, because of the long focal length, you can disable lens distortion calculation.
It will still give you a good result.
Offline
the weird is that it worked on 2.5 without any problems - even with much larger Gigapixels! :-/
Offline
did some Tests ...
1) APG 2.6 with Lens Correction: crash
2) APG 2.6 without Lens Correction: http://temp.in.futureweb.at/autopano/autopano2.6.jpg
3) APG 2.5 without Lens Correction: http://temp.in.futureweb.at/autopano/autopano2.5.jpg
I just can't get a single Gigapixel to render correct within 2.6 - tested it with some of my older gigapixels with all stitched perfect within 2.5?!?!?
Andreas
Offline
We changed the algorithm in Papywizard plugin. Were you using this plugin ?
Offline
using the Gigapan importer
Offline
Issue 1122 opened
Offline
If I can provide further information - just tell me what you need!
Offline
Oh, gigapan ! That changes everything. I'll check this part with the gigapan example I have here. If I have question, I'll come back here.
Edit : confirmed. As soon as you don't use 'automatic detection' in gigapan plugin, the optimization afterward goes crazy.
Offline
great you found the problem that fast!! ;-)
Any other possibility to deactivate "lens correction" other than disabling "automatic detection" and change it in the settings?!
Last edited by Hellkeeper (2012-01-17 09:52:06)
Offline
@AlexandreJ, any idea when this bug is fixed? Would like to use the lastest version! ;-)
Andreas
Offline
This fix is already in 2.6.2 RC2 if I remember well.
Offline
perfect - will download it right away! ;-)
thx!
Offline
Pages: 1
