MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
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.
Hi,
About 2 weeks ago I posted
  Problem calibrating with demosaic narrow band data
and within about 5 hours Mabula had explained my problem and how to fix it. So I can't fault the service I get here!
Now that's great, but the more I thought about it, the more I realised that there were aspects of the problem that I didn't understand so I have a supplementary question. It may be academic but part of the fun of our hobby is understanding the technology which is in any case key to best exploiting it.
I will briefly restate the original problem, albeit with different data
My setup
Target M42 170x15sec 125gain
Capture RedCat 51. Optolong L-eNhance Dual Narrowband. ZWO ASI183MC Pro
Processing MacOS Mojave. APP 1.083 or 2.0.0-beta12
Calibration Full set BPM,MF,MD(300sec),MDF,MB
My problem is that when I debayered with the algorithm Ha-OIII color my integration looks like this (maximally overstretched to enhance the effect).
Clearly horrible amp glow even though I thought my calibration was fine.
Mabula explained that amp glow isn't linear in time, which does make sense, so dark scaling won't work; I need to make my MDs with 15sec darks.
So, I have a solution, BUT if I integrate with the Adaptive Airy Disk then I get this.
which looks like the amp glow has gone! I appreciate that comparing stretched histograms can be misleading so I saved my images un-stretched and then in photoshop carefully stretched both in exactly the same way and the result was the same.
Naively, I thought that as dark noise isn't "coloured", it has not been subjected to any optical filter, its subtraction ought be more or less the same regardless of the debayering method. Clearly I am mistaken, but I should really like to know how I appear to get away with scaling with AAD but not when I use the correct Ha-OIII color?
I'll inform Mabula on this one. 🙂
Thanks Vincent, have you had a chance to let Mabula know yet
Nick
I have, he didn't have time yet unfortunately. If he doesn't come back in a few days I'll check.
Thanks Vincent, I know you guys are very busy so I'll be patient.
Nick
Dear Nick @nickwest
Sorry for the delay in my response.
Did you try to provide matching darks for your lights frames? Was the result better?
I have no clue why AAD is not showing the amp-glow versus Ha-O3 extract O3 showing it without seeing the data myself. But as I said, any issue relating the amp-glow will be solved if you would supply 100% matching darks for the lights and disable dark-scaling.
