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,
Often I use Alias / shorcut for Bias, Flats or Dark files. These files are often shared between acquisitions. As such, I create Alias directories (Shortcuts) within a specific directory.
For example: Last night I tool M81 and M63 with the same equipment profile and filters. At the end, I created Flat, Bias and Dark for M63. Each of them are in a directory within the M63 directory. On the M81 directory I make Aliases directory that opens up the M63 ones.
The problem is that I dont see these Alias directory under APP when I "1) LOAD" my files. Its hard to explain. :). I'm hoping you get my point.
Michel
Yes I totally get it, I think you're the first one using it like that. 😉 But I can see the benefit, I would have to ask Mabula if this is possible, I'll get back to you on that.
I just checked locally on my Mac and for me it works. What I did was creating a "symlink" for the directory I wanted to link in to my working directory from the Console.
It shows up as normal directory in the file dialog in APP.
What is not working is using an Alias created in Finder, because Finder creates only a MacOS specific proprietary file pointing to the destination by the content of that file instead of a POSIX compatible symlink.
Mario.
Ah, very interesting Mario thank you for that! I didn't know this was different from a regular symlink.
Ahhhh yes, learning. I just downloaded a small app that allows you to create Symlink without the use of the terminal and it works perfectly! Thank you Mario.
