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 noticed if I integrate a set and then add another light, it will redo everything instead of just reanalyzing the stars on the new light. Is there any way to avoid this?
Clearly, it may want that new light to be the new reference frame, but perhaps there is a way to just say "Just add and register the new lights and keep the same reference frame, don't redo everything".
The reason I may add more lights is:
1) I may have a session open and collected some more data that I just want to add.
2) I may do a subset to test and then want to add the remainder and do the full set.
3) I may want to create an artificial reference frame that is pre-cropped to a particular size and FOV that is different than any one light. (I do this often with overlapping panels)
4) Or I may have unselected some lights by accident and just want to select them now that I discovered my error.
Also:
I was doing an integration and I canceled it during registration to change the scale stop. When I restarted it needed to re-integrate the bias and flats, and then it did analyze stars again.
Does the change in a registration setting like scale stop require it to redo these earlier processes? If so, how do I know what changes cause this? If not, then what is causing it?
You could integrate per session, load that integration as light and then add more, though I would only add more if you have enough of those. Not sure if the current algorithm is able to do this, so I'll ask Mabula.
I noticed if I integrate a set and then add another light, it will redo everything instead of just reanalyzing the stars on the new light. Is there any way to avoid this?
Clearly, it may want that new light to be the new reference frame, but perhaps there is a way to just say "Just add and register the new lights and keep the same reference frame, don't redo everything".
The reason I may add more lights is:
1) I may have a session open and collected some more data that I just want to add.
2) I may do a subset to test and then want to add the remainder and do the full set.
3) I may want to create an artificial reference frame that is pre-cropped to a particular size and FOV that is different than any one light. (I do this often with overlapping panels)
4) Or I may have unselected some lights by accident and just want to select them now that I discovered my error.
Also:
I was doing an integration and I canceled it during registration to change the scale stop. When I restarted it needed to re-integrate the bias and flats, and then it did analyze stars again.
Does the change in a registration setting like scale stop require it to redo these earlier processes? If so, how do I know what changes cause this? If not, then what is causing it?
Hi Steven @readyjetty,
I noticed if I integrate a set and then add another light, it will redo everything instead of just reanalyzing the stars on the new light. Is there any way to avoid this?
It is on my todo list to improve this for sure 😉 it is actually part of the new save/load project feature which is coming in 2.0 stable.
I was doing an integration and I canceled it during registration to change the scale stop. When I restarted it needed to re-integrate the bias and flats, and then it did analyze stars again.
Does the change in a registration setting like scale stop require it to redo these earlier processes? If so, how do I know what changes cause this? If not, then what is causing it?
If you cancel during registration, APP should never re-integrate the bias and flats unless you restart 2)calibrate. The frame marks in the frame column should still show that you passed star analysis. However if you added new lights as well after cancelling registration, APP will indeed fall back to 2)Calibrate, because of your first question.
So we will definitely improve this behaviour soon.
Mabula
Thanks for the quick answer!
