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.
This is rather odd. I have two sessions, Ha and OIII for each. I have master darks, bias, and BPM that go to all sessions. I have one set of flats that should go to both sessions -- when I loaded them I specified "all sessions".
I've done it several times, with 1.082 and 1.083 beta, and every time the appropriate flats get assigned to everything except the Session 1 Ha frames. Doesn't matter if I re-assign the generated master flats and do it over.
What the heck?! I guess the next thing to try is to run "calibrate" to completion with only the session 1 frames loaded and the master flats, then load session 2's lights and run "calibrate" again.
Figured it out. Won't apologize for posting, perhaps someone else will see this and have the penny drop.
Some bits of my imaging chain use "H_alpha", and others call it "H-alpha". So when I allow the "FILTER" tag to determine the assignment, it doesn't match the wrongly-tagged lights. That's all it was.
Glad you figured it out. Yes, that is a tricky situation that may be hard to solve.Â
Wouter
