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.
The error mentioned above occurs in APP 1.059 while trying to integrate H-alpha DSLR subs. It occurs with everything on default settings, but also when settings under 3) Analyse stars, 4) Register, 5) Normalize are changed. Also doesn't seem to matter if algorithm under 0) RAW/FITS is set to H-alpha or Adaptive Airy Disc. The lights are calibrated with a master flat and master bias. All @ ISO 1600.
Â
Enabling bayer drizzle seems to cause the issue... I'm further investigating the problem.
Hi @maurice_toet,
What happens if you alter the drizzle droplet size and integration scale? Do you get the same error?
The progress indicator is only at 10% so it seems to occur when the first frame of the stack is loaded. Perhaps it is usefull if you could send me one of the frames and the calibration masters, or 1 or 2 calibrated frames. Then I can probably quickly find the root cause 😉 of this...
Kind regards,
Mabula
Yes, Bayer Drizzle causes the issue. Quite obvious coming to think of it...
Hi @maurice_toet,
What happens if you alter the drizzle droplet size and integration scale? Do you get the same error?
The progress indicator is only at 10% so it seems to occur when the first frame of the stack is loaded. Perhaps it is usefull if you could send me one of the frames and the calibration masters, or 1 or 2 calibrated frames. Then I can probably quickly find the root cause 😉 of this...
Kind regards,
Mabula
I missed your post. I'll send you some files so you can have a second look.
Hi Maurice @maurice_toet,
I have found the bug... it was a combination of applying bayer drizzle and DSLR data with raw borders. In normalization, the datatype is changed to 32bits floats and the raw borders of the DLSR data weren't dealt with properly for Bayer Drizzle, causing the bug...
So this will be fixed in APP 1.060, soon to be released.
I assume you were able to create a good integration with either regular integration or Drizzle integration using the H-alpha debayer algorithm?
Cheers,
Mabula
