June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
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 have a weird one going on here. I am working a 4 panel mosaic and I have tried everything from 2000 stars to 4000 stars and having cosmic ray/noise reducer clicked on the analyze stars tab, and on the registration tab I have tried scale stops set at 1-10, 1-15, 5-15, both triangles and quadrilaterals, both with dynamic distortion on and off, and enabling flip the x and y descriptors. I can consistently get 3 of the panels to register with each other, but that 4th one seems to not be happening. I have tried to set the Ha from that one as the reference frame and it will register against the Sii and Oiii, but not against any of the subs from the other 3 panels. If I let it automatically select the reference frame it will not register the ones from the panel that needs to go in there. I have a screenshot with the opacity turned down so I could match the panels up at 100% zoom, and they do match up when I do that, but I need them to register and do that in APP. Any idea why this is happening? I can upload the masters or even the zipped sets of lights for each panel if I need to.
Here is the only thing I have gotten to register and stack using triangles. It isn't anything I can work with though.
Mm, is there any big difference with the subs of that one panel perhaps? Maybe a difference in calibration data or anything else?
All the subs were calibrated the same. I think I figured it out though, for some reason that one panel barely had any overlap because the guidecam locked on to a star that moved our center slightly, and with only running an 8% overlap that must have been the issue. I threw in some subs from another integration of this object that pulled in more overlap and it integrated using quadrilaterals and dynamic distortion correction as normal. There is overlap, but not enough for APP to be able to pick up even though I can get it to work manually in Photoshop.
Hi @imnewhere,
Okay, if too little stars are present in the overlap area things can be rather difficult, sometimes you need to increase the margin as well to have it work then 😉
Mabula
