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.
Recently when combining a R, G, B, Ha, and OIII, I noticed that in the RBG combine the results were messed up. Searched around and discovered that my camera-imaging software were giving me a bayer pattern of GRBG, and not RGGB which was what I had APP set to.
Â
I changed it to GRBG and ran everything again, and in RGB combine the sliders did not change the colors thy were assigned too. I figured out which was which and the image came out decent just complicated.
Â
More research shows that the native pattern for my camera is GRBG. Should I be setting APP up for that pattern all the time?
Â
If the capture software does that then yes. It might be interesting to notify the developers of that software to this issue or switching to another capture program.
I did contact them with the same question, and they said that FITS inverts the RGGB to GRGB when writing, Sounds like Smoke and Mirrors to me, but I will do some testing to figure it out.
Main question is what is APP looking for when you just leave the setting at supported?
Â
The supported just takes what the FITS header mentions it is and processes it accordingly.
