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.
Getting this error in Normalize that essentially halts process with multiple error windows saying that same thing. Never seen this before but it has happened last few workflows. Nothing else has changed in terms of camera or image acquisition (FITS via SharpCap). It is a non-recoverable error. Help!
Â
I have also encountered this srror... any ideas?
Ross
I posted the error in this forum and in a Face Book group. Got no help. I did the following to address the issue:
- Noticed on my Windows 11 laptop that Java was not installed so went ahead and did that (I suspect a Java error is involved). This helped on one processing run and not the other where more frames involved.
- Installed APP on a MAC desktop unit (you can do multiple installs). I bring all the image files over on a Samsung portable drive and APP so far has run perfectly on the MAC. Not the most convenient solution but it works.
I suppose we could also go back to a much earlier version but then lose any "improvements" in version 2. Too bad the author did not reply to help - we cannot be alone with this bug.
This error continues to plague my processing.. I can go weeks and everything is ok and then it strikes again.. After many years of using APP and the lack of response it is about time I made the move to stacking in Pixinsight..Â
I am having the same ongoing experience. Often a restart and rerunning of APP works ok. I still think it's an external Java issue as that module has to be ended in Task Manager to clear the errors. Frustrating......
I usually process in Pixinsight and have decided to bite the bullet and learn WBPP for stacking and this has solved my problems. As I shoot Hyperstar the number of subs often exceed 200 by 50mb and neither APP or PI can do this quickly and my stacking runs are usually batched overnight. A failure in a big overnight run becomes a real set back.
Ross
