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.
I may have found another bug. Â
Today I was stacking some subs for a mosaic. So I stacked all my Blues and used Bias, Dark, Flats and a Bad Pixel Map (B D F BPM). Once the integration is complete my light frames are accompanied by the following codes: B D F BPM CA STAR REG NORM. All is perfectly normal so far. Now I am going to stack teh next set of subs. I am using the same Bias, Darks and BPM masters. So I go back to the 'LOAD' tab. I hit 'all - clean - all' next to 'light' to clear out all my light subs. Then I remove the old flat master and the previous integration, so that I only have a BPM, a master dark and a master bias. I add my new set of lights, and then load the new master flat. At this point, my lights all now read 'B D F BPM STAR NORM'. I cannot trust this, obviously. So now what I have to do is 'all - clean - all' for the lights and reload them. All is now good with just 'B D F BPM' next to my light frames.Â
If I load all the masters before loading all the light frames, then this 'B D F BPM STAR NORM' malarkey doesn't happen. So I can make it all work as it should. However, it would be nice not to have this potential 'gotcha' in the system.
I may have found another bug. Â
Today I was stacking some subs for a mosaic. So I stacked all my Blues and used Bias, Dark, Flats and a Bad Pixel Map (B D F BPM). Once the integration is complete my light frames are accompanied by the following codes: B D F BPM CA STAR REG NORM. All is perfectly normal so far. Now I am going to stack teh next set of subs. I am using the same Bias, Darks and BPM masters. So I go back to the 'LOAD' tab. I hit 'all - clean - all' next to 'light' to clear out all my light subs. Then I remove the old flat master and the previous integration, so that I only have a BPM, a master dark and a master bias. I add my new set of lights, and then load the new master flat. At this point, my lights all now read 'B D F BPM STAR NORM'. I cannot trust this, obviously. So now what I have to do is 'all - clean - all' for the lights and reload them. All is now good with just 'B D F BPM' next to my light frames.Â
If I load all the masters before loading all the light frames, then this 'B D F BPM STAR NORM' malarkey doesn't happen. So I can make it all work as it should. However, it would be nice not to have this potential 'gotcha' in the system.
Thanks again, I have been fixing several issues like this in the upcoming version 1.057.
Indeed, it has to do with backing up processing details, restoring and cleaning up the data. To do be sure, I'll check this behaviour first thing tomorrow, so I am sure it's fixed in the next release.
Cheers,
Mabula
After you have them all loaded, one idea might be to ignore the suffixes and just do calibration like you normally would have to do first anyway, and you should see that they have been updated to just CA?
I may have found another bug. Â
Today I was stacking some subs for a mosaic. So I stacked all my Blues and used Bias, Dark, Flats and a Bad Pixel Map (B D F BPM). Once the integration is complete my light frames are accompanied by the following codes: B D F BPM CA STAR REG NORM. All is perfectly normal so far. Now I am going to stack teh next set of subs. I am using the same Bias, Darks and BPM masters. So I go back to the 'LOAD' tab. I hit 'all - clean - all' next to 'light' to clear out all my light subs. Then I remove the old flat master and the previous integration, so that I only have a BPM, a master dark and a master bias. I add my new set of lights, and then load the new master flat. At this point, my lights all now read 'B D F BPM STAR NORM'. I cannot trust this, obviously. So now what I have to do is 'all - clean - all' for the lights and reload them. All is now good with just 'B D F BPM' next to my light frames.Â
If I load all the masters before loading all the light frames, then this 'B D F BPM STAR NORM' malarkey doesn't happen. So I can make it all work as it should. However, it would be nice not to have this potential 'gotcha' in the system.
Thanks again, I have been fixing several issues like this in the upcoming version 1.057.
Indeed, it has to do with backing up processing details, restoring and cleaning up the data. To do be sure, I'll check this behaviour first thing tomorrow, so I am sure it's fixed in the next release.
Cheers,
Mabula
@gnomus, thank you very much Steve 😉Â
@gregwrca, thank you for suggesting a temporary workaround 😉Â
I have located the issue and it will be fixed in APP 1.057.
Internal tracking of calibration, star analysis, registration and normalization parameters was off for frames that had no parameters at all. The marks showed up nevertheless when other frames had parameters due to a bookkeeping error in my code.
The fix now also properly updates the marks for the calibration frames if you remove a master frame using the right-mouse button menu in the frame list panel.
Cheers,
Mabula
