Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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 have noticed more lately that I am getting a weird pattern at some corners. It doesn't matter if it is a mosaic or a normal integration. Any idea what is behind this?
@imnewhere Which version of APP are you using? If a 2.0.0-betaX version, can you try with 2.0.0-beta9?
@imnewhere What kind of data are you integrating? OSC, mono or combined? What calibration data? I think the images you show are for a mosaic. Does this also happen in de individual panels? If yes, can you post an image that shows that?
@wvreeven it only happens on mono, and then I have only noticed it on shorter sets of subs regardless of total integration, for instance the following example has 2x 600s each of LRGB. Sometimes turning off MBB and LNC keeps it from happening, but not always. OSC is fine no matter how few subs there are. It will happen on a mosaic with a panel that happens to be a lower number of subs, but that same panel will do this when set as a normal integration of just that object. I have had this happen on multiple integrations and between light pollution removal and Photoshop I can make it not very noticeable, but on other things I have to crop it down past the pattern.
If you want I can upload the calibrated subs for a few different cases where this happens.
Hi @imnewhere,
What kind of normalization parameters are you using? And which settings for MBB and LNC ?
We fixed a bug a bug with the adaptive pedestal which was responsible for some normalization issues. In this case it seams that maybe enabling LNC is causing it, which is a known problem in the current implementation. Does your problem happen with LNC disabled and advanced normalization ?
Mabula
@mabula-adminÂ
For normalization I leave things as default on regular integrations and advanced on mosaics. I found that some would end up fine if I turn off MBB and LNC, though I normally run 10% MBB and 2nd degree 3 iterations on LNC. This one I left everything at defaults for the whole run other than checking the boxes for hot pixels, cold columns, and hot columns at default.
Okay, Can you upload the data on which this occurs and give me instructions exactly on how I should process it to reproduce this problem?
https://upload.astropixelprocessor.com/
username : upload
password : upload
Please make a folder with your new like ImNewHere-normalization-issue and let me know once uploaded, I will investigate as soon as possible.
Mabula
@mabula-adminÂ
I have uploaded what gave me the attached result. It was with 2nd degree LNC 3 iterations and with MBB enabled at 10%
I did testing to see if I could get it with LNC off, MBB off, or both off and I got results that were good.
