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.
My first clear night since October produced calibrated images with quality scores between 10 and 30. Isn't this amazingly low?? I seem to recall my 'good' images being scored in the 400 to 500 range.Â
I've made a few changes to my setup since my last session. Did I miss something? Or has the scoring system/values changed recently? I'd love to know how it's calculated, so I can try to troubleshoot it better.
(Didn't find the info in the FAQ or a search, so perhaps others are wondering too.)
My first clear night since October produced calibrated images with quality scores between 10 and 30. Isn't this amazingly low?? I seem to recall my 'good' images being scored in the 400 to 500 range.Â
I've made a few changes to my setup since my last session. Did I miss something? Or has the scoring system/values changed recently? I'd love to know how it's calculated, so I can try to troubleshoot it better.
(Didn't find the info in the FAQ or a search, so perhaps others are wondering too.)
Hi @cheetah , perhaps you can share an image ? So I can give you a proper answer. And please share the exact details of your optical setup (focal length, OTA etc..)
The quality scores are relative. There is no absolute score to indicate what a good score is actually.
The score is calculated with a special formula that consists of star density, noise and star shape.
Simply said, star density and star shape are relative in terms of imaging scale in pixels. If you register frames of different image scales, this will become clear.
In relative terms, frames with stars with a large FWHM value in pixels will get a low score. But it does not mean that the frames are bad, it could simply mean that you are shooting with a very long focal lenght.
Later today I will try to update this post with the exact formula 😉
Kind regards,
Mabula
Thanks for the quick reply!
I didn't finish the processing, since the scores are so low and I assumed there was a larger problem. The .fit files are too large to attach, so I don't have a way to show you an image right now.
I'm shooting with an ASI1600mc-p, on a 6" newtonian 750mm, with a mpcc coma corrector. Subs are 30 second unguided, from the edge of a small city. Nearly a full moon, but no light hitting the OTA.
If the weather holds, I'm going to attempt the same target and will try guiding. Maybe that makes more of a difference than I had thought...
I may have found the problem. My OTA needed collimating...badly... We'll see what happens with the next images I take.
