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.
Hi Mabula,
I had a couple hundred frames of M1 taken with a very small FoV (F/10 SCT). Â
Most frames passed Registration with stars found = 504.
About 10 frames failed with stars found = 498, 496, etc.  Numbers just under the 500 minimum.
Is there a reason we couldn't have a lower number of stars found still be a "passing grade" for registration?
Thanks!
Rowland
Dear Rowland @rowland-f-archer-jr,
I am about to release APP 1.072 😉 it has a further improvement in star analysis and it could be the solution to why some frames failed in your case.
The actual number detected, being a bit above 500 or below should not make a difference. Some images only contain very little stars and APP will register those, if the star analysis works correctly.
Some users experienced difficulties because hot pixels were mistaken for stars and then registration on those frames will fail. I think the new release will solve this and I would think this is the issue that you face as well.
You can check yourself if star analysis is working correctly on those frames, by setting the image viewer to the starmap mode. Please check if APP finds stars were there are actually hotpixels 😉
I will try to release APP 1.072 within the next 24 hours !
Mabula
Â
Hi Mabula -Â
OK, I will try 1.072 🙂
I asked because it seemed like only the images with stars just under 500 were marked as "Failed." I loaded the images and they looked OK. APP is busy now calibrating frames from last night so I can't easily re-run to see if hot pixels were selected as stars. Â
Cheers,
Rowland
It must be an M1 thing as the other day all my M1 images failed, again with an SCT.
Must be a star poor area.
Â
I ran the images again yesterday and all but 2 passed using per session setting.
Hi @rowland-f-archer-jr and @steveibbotson,
Please let me know how APP 1.072 performs, in star analysis, an extra algortihm is added to better discriminate between hot pixels and small stars. In data with a little amount of stars, APP was detecting some hot pixels as stars and that could have been the reason for registration failures.
Some other users shared their data on which APP 1.070 and 1.071 had problems due to a small star count and detection of hot pixels as stars..., and those datasets do work properly now. If it still fails, please share the data so we can further improve this 😉
Kind regards,
Mabula
Â
I will run the subs through again.
Â
I have collected a bit more data since my last stack.
It could be that with using the SCT my stars are also a bit "blobby"
I restacked last night using 1.o73 and at first it analysed and reject a few subs which I agreed with.
Ran the registration with default settings and it rejected them all.
I changed to triangles and then upped the scale stop to 8 (I think) and then manually selected a referance frame.
And with a bit of fiddling in PS.......
Â
