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'm new to APP, was using Pixinsight for longer time.
I want to find out which of my frames are trash to locate them and delete them.
I did a stack of 3 nights, and noticed that when I stacked "session 1" only in past in Pixinsight, it looked better to me than all the 3 sessions together.
How do I locate the exact frames that are bad in APP?
Also for example the quality score (green), is 1 the maximum?
I know that some of my frames don't have the best focus, but I guess they won't make the stack worse, unlike frames with bad seeing/clouds, so I would like to get rid of those.
I've closed APP after stacking, can't find any log files anywhere. (I'm on Mac)
Thanks
EDIT:
Also I've noticed that APP does some noise reduction on the stack, but I don't see an option anywhere to disable it.
I usually check each parameter one at a time. Sort them by best first
Hoover over one data pont and you will se what sub frame it is. Delete the sub frame in the list below. Either remove it from the stack or delete the file.
Â
/stefan
@digitaliz-se Do you do that after stacking? or can you do that before?
I've watched some APP tutorials but still can't figure it out.
There are a few ways to deal with this.
Your bad frames are from about frame 130 to frame 190 - so about 60 frames. That's about 20% of your 280 frames.
In tab 6)Integrate there is a slider for "lights to stack", with a default of 100%. If you drop this to about 80% then it will reject the worst 20% of frames prior to integration, based on the "quality" metric. This should solve it for you.
JC
Do all steps till step 5 (Normalisation)
Remove bad frames ad then stack.
Â
/Stefan
@digitaliz-se Do you do that after stacking? or can you do that before?
I've watched some APP tutorials but still can't figure it out.
Â
hi @pkolano,
Indeed, like John @connor231 & Stefan digitaliz-se indicate. Session 2 looks bad.
The lower the dots in the graph the worse the data is for that metric.
Logging can be enabled/disabled with the console panel. Do you have the console panel enabled? Check the CFG menu for this.
Mabula
