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'm not sure what happens here, but I have some images from M31 that I would like to process and yesterday everything worked fine on that stak right up to the point where APP told me that I had run out of memory. OK, stuff happens. So I restarted APP and allowed it to use more memory and everything's fine but now the same stack gets continues messages that the registration has failed on some of the frames. I've already increased # stars and enabled/disabled the things suggested in the pop-up window so I'm a bit at a loss.
Oh yeah, I'm a total newbie so I asume this is down to me.
all the best,
Hans
It might be an issue with the data itself. What system are you processing on (amount of memory, OS?) and what version of APP are you using?
Thanks
Is could be the data itself, though it has registered now. That's the thing I don't understand: why it will register one time but not another time and then, after a few tries, it does register.
I'm running APP 1.082 on a windows 10 machine using a Core i5-3470s running at 2.90 GHz and 8 GB of memory (I allow AP to use 6 GB).
I hope this helps.
Ok, so the memory is a bit on the low side. Together with Windows 10 taking up some of that, it may struggle there and that's why you had an out of memory error probably.
Why it registers some of the time, that's interesting indeed. Maybe there are some small variations in the algorithm and if your data is on the edge of what it accepts, it might be triggering such an issue. For that I would need the data to see, can you post a screenshot of how a frame that sometimes causes problems, looks like?
Hi Vincent,
Sorry for taking so long; the thing is working now so I can't take screenshots anymore. Anyway, thanks for thinking with me and I'm happy with the way it works right now. And I'm getting a new computer with more memory and a better CPU and graphics card.
all the best,
Hans
Superb, well that should definitely help. 😉
