Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
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.
Looking for help with error message when calibrating
not sure if this helps but I am experiencing a similar (but not exactly the same) error with beta 37 which I have not seen before:
This occurs (sporadically) after a normal integration sequence when I go back to save the calibrated lights. The lights save fine but then the console seems to keep on doing 'something' in the background for some time and eventually this error is produced.
It doesn't seem to have have any real consequences (at least for me) as the calibrated lights are saved OK before any of this happens...
I was using an M1 MacBook, and I've figured out what happened—100% user error on my part. Scale master dark was selected for the calibration, which requires the master bias. I had mapped the master bias file to the bad pixel map by mistake.
Regarding your last post, I may be wrong but my understanding is that a Master Dark used for Scaling must be created with Dark frames and Bias frames, not using a Master Bias file????
I was using an M1 MacBook, and I've figured out what happened—100% user error on my part. Scale master dark was selected for the calibration, which requires the master bias. I had mapped the master bias file to the bad pixel map by mistake.
TY to all who considered this.
Hi Kevin @kevinkalikimaka, that is great. Thank you very much for your feedback. I did implement a fix for this error and it should not happen again with 2.0.0-beta38 or later 😉
@jhart that is not correct, to have scaling working on the masterDark, the MasterBias must be present. The MasterBias is subtracted form the MasterDark and then a noise analysis on the subtracted MasterDark determines the scaling factor(s).
This post was modified 12 months ago by Mabula-Admin
not sure if this helps but I am experiencing a similar (but not exactly the same) error with beta 37 which I have not seen before:
This occurs (sporadically) after a normal integration sequence when I go back to save the calibrated lights. The lights save fine but then the console seems to keep on doing 'something' in the background for some time and eventually this error is produced.
It doesn't seem to have have any real consequences (at least for me) as the calibrated lights are saved OK before any of this happens...
