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.
Hi,Ā
I am integrating 435 subs (from 60s to 180s) of M51 with darks, flats, darkflats. The result has strange artifacts on the sides and inside the picture (see attached). This never happened to me before.
Integration is set in full automatic, with LNC set at 1st degree - 1 iterationĀ and MBB at 5% as usual for me. All subs are correctly framed with M51 in the center (dithering apart). Version 1.077 of APP.
Does anybody understand where it comes from and how I can correct it ?Ā Ā
Thanks.
Philippe
Sorry, missed yours (it's a bit hectic here with my wife as a GP at the moment).
So, that looks a little like some kind of stack artefact, can you describe the exact settings you used? And maybe try 1.078 as well, the most recent version.
Thanks Vincent. No worry. I understand fully the hectic situation you are in !Ā
That was with both 1077 and 1078 with all in automatic (no LNC). I solved (?) by using LNC 1-3 (LNC 1-1 was not enough) but I think it is a cosmetic correction to indeed stack artefacts. Never had this before. Could it be the number of subs?Ā Ā
Maybe you are import files from external drive or USB stick ..... Try move your folder on C disk and try again .....
I've just the other day encountered something similar, and could more or less reproduce it.
I had a stack of 757 images (on an external SSD), which required a whopping 500 GB of disk space, which I didn't have available at that the time I started the integration. I got a warning, did the "test for available space" which passed, and let the integration continue, ignoring the ever-repeating warning on disk space.
I ended up with similar artifacts, very likely due to lack of disk space which surprisingly didn't seem to cause further errors for APP.
I am now running a new integration, this time with enough empty disk space. It does take its fair bit of time to complete, so no results yet.
Ā
@phfenain, did you have enough disk space with your 435 subs?
After about 20 hours of integration I have the final verdict: a beautiful stack when you actually give APP the disk space it needs to perform the stack 😉
With enough space:Ā
Ā
With insufficient space:
Ā
