MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
I'm about to shoot an all-sky mosaic using a computer controlled equatorial mount. I can specify alt-azimuth coordinates in degrees and the software does the rest.
I was wondering what are the optimal alt-azimuth values to specify to get the best results from APP.
This is a tricky mosaic to stitch for panorama software because the camera rotates so it is never horizontal in relation to the ground. But I'm reasonably sure APP can handle that.
Another issue is that I don't really know how to uniformly spread alt-azimuth values uniformly over a sphere. But I'll figure that out. In the meantime I might just rotate azimuth from 0 to 360 and altitude from 0 to 90. It will get quite squished near the zenith. Is that a challenge for APP?
Hi @ddnum,
Indeed, APP can register widefield data 😉 with a very large field of view. For example this 180 degree mosaic, shot at 14mm focal length:
In your case, the field of view will be larger than 120 degrees, since you mention an all-sky mosaic.
In that case, you must use the calibrated projective registration mode in 4). The calibration enables a different data projection than the default rectilinear projection. A rectilinear projection will never work with a field of view larger than 120 degrees.
I was wondering what are the optimal alt-azimuth values to specify to get the best results from APP.
There aren't, but I would recommend enough overlap between the mosaic panels, with more overlap, the result will be more robust. So 20% overlap will give you a much higher chance of a good result than 10% overlap 😉
Another issue is that I don't really know how to uniformly spread alt-azimuth values uniformly over a sphere. But I'll figure that out. In the meantime I might just rotate azimuth from 0 to 360 and altitude from 0 to 90. It will get quite squished near the zenith. Is that a challenge for APP?
APP can handle that, this is a 30 panel mosaic surrounding polaris (data courtesy of Scott Rosen @scott_rosen ) shot with 2 different camera's:
Do let me know if you need assistance when you are starting to process the data 😉 . I have been working on a big upgrade of the registration engine as well to also further improve and speed-up mosaic registration and to add more data projections like sperical.
Kind regards,
Mabula
Thanks for the reply. I'm going to shoot 21 images at the vertices of an icosahedron. I'm doing the calculations to see if there will be enough overlap.
Where the images overlap does APP integrate the pixels? If each panel is a stack of 4 images does the overlapped area have the SNR ratio of 8 images? If that is the case then I can really go hard on the overlapping area knowing that it increases my SNR ratio so no pixels are wasted.