 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
increasing the Cache divisor brings up another problem! :-/
http://temp.in.futureweb.at/apg/apg3b2_render1.JPG
any idea how to render this pic?
Last edited by Hellkeeper (2012-10-31 20:06:58)
Offline
The cache division gives a balance between size you can effectively render and the amount of overlapping we can manage. Changing this value will influence both limit in a different way.
The width here is 650K, so you need to have 1024K in width as limit. You also have a lot of overlapping. Perhaps more memory will be needed.
Nevertheless, I would advise you to wait for next beta, in which we solved a bug in the antighost cache limit calculation. With that bug out, you may be able to render this kind of nice beast on a not too big hardware.
Offline
Hi Hellkeeper
Why not downscale the input files to 50% ?
Because of the bayer pattern of most of our sensors, we should do this as a standard.
You get really sharp images and a really sharp gigapano, lose only marginal image information.
And you can avoid a lot of problems. Try it out.
It's not the size that makes the difference, it's the quality ;-)
Offline
Hi,
more Memory would be a bit of a Problem - as our HP z210 Workstation only Supports 16GIG of (non-ECC) RAM ... unfortunately! :-(
But I managed to render the Pic ... did some testing with cacheBlocSize in regedit - after some time I found out that the Image will render when setting it so 12MB ...
Why does setting the CacheBlocSize to AUTO in APG not determine that it will work with 12MB - would help if it would! ;-)
@lumelix: guess this would be an option too - espacially because APG is blowing up my Gigapixel Images about by the Factor of 2-4 ... :-/
(the latest Gigapixel I made should have about 40 Gigapixel - but has 153 Gigapixel)
Andreas
Last edited by Hellkeeper (2012-11-05 14:29:17)
Offline
alright - this is the Picture that made such big Problems: http://www.gpix.at/Gpix.at-Gigapixel_gp … eview=true
Some Problems still exist:
1) It's about 4x larger than it should be! :-/
2) Got some stitching Errors (black spots): http://www.gpix.at/Gpix.at-Gigapixel_gp … 1635093266
3) colours/brightness is unequal in some parts of the picture
4) Mountains behind haze ... but that's something I cannot change I fear
5) initially it was recognized as 360° Picture ... had tu manually fix that (never happened at older Versions of APG :-( )
as for problem 2: It would be great if the APG Editor got a "detect gap" feature ... I click on the "detect gap button" - APG will show me to the next "gap" - so I can fix it manually. It's nearly impossible to find all gaps by just looking at the picture ... on large pictures this would take you a really long time - searching with high zoom level ... and APG Editor isn't the fastest it you work with that large pictures! ;-)
So still some work to do on this pic! 
Andreas
Last edited by Hellkeeper (2012-11-06 16:47:20)
Offline
Hellkeeper wrote:
@lumelix: guess this would be an option too - espacially because APG is blowing up my Gigapixel Images about by the Factor of 2-4 ... :-/
(the latest Gigapixel I made should have about 40 Gigapixel - but has 153 Gigapixel)
The sharpness is ok when zooming out one click and perfect when zooming out two clicks.
4 times too big render and "spherical" detection: eventually wrong type (fisheye) and focal lenght ?
You can set the render output in percent, so use 50%
Last edited by lumelix (2012-11-07 13:55:44)
Offline
