June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
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.
When creating a bad pixel map with my ASI294MC Pro something strange happens. The Amp glow is recognized as a hot pixel and if my Lightframe calibrated with it, disturbing pixels on the previously not see.
🙃Â
Hello Mabula, should I do without the Bad Pixel Map in this case?
Good question, I'm not sure if the BPM should include things like amp-glow actually, @mabula-admin knows all about that. But as a general rule, if the calibration frame causes a problem in the end-result, it's better to leave it out.
Hello Mabula, did you have a look at Bad Pixel Map?
Hi @minusman,
I have tested this on data that I have of a ZWO asi183mm which has very strong amp-glow.
I am seeing the problem that you have as well, allthough not so prominent, shown first is MasterDark, then BPM:
This was with APP 1.068 and a hot pixel kappa of 2.0.
I get the following calibration result (data provided by Yves van den Broek @yves_van_den_broek ) , first is shown an uncalibrated frame, then calirbated with a MasterBias, MasterDark and the Bad Pixel Map and with the Adaptive Data Pedestal on. The Adaptive Data Pedestal is needed here.
So this is fine I think.
Is the BPM in your case messing up data calibration of the light frames?
Can you show an example/screenshot ?
The issue most likely has to do with some changes that I made in the Bad Pixel Map creation. I should be able to adjust here. So I will have a look and test if I can improve this.
Mabula
Â
Hello Mabula, I once processed another record of dark frames with cooling turned off. Since the problem hardly occurs.
I will again make new Darks and flat frames for security.
When creating BPM, do I need a Master Bias or Master Dark Flat? If I omit it comes a warning.
