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 am slowly working through a mosaic project & last night managed to capture a 2nd session of data for the target.
Running two sessions data through APP was a breeze but I did stumble upon a weird naming convention issue.
On the first integration of my data I chose:
Multi-Session Options > Integrate per session & all
this produced:
Integration 1 Session 1
Integration 2 Session 2
Integration 3 Session 1 & Session 2
very obvious and nothing wrong there.
Now I was not happy with the output of Integration 3 and made some changes in the Integration tab before running the Integration again.
This time I just chose:
Multi-Session Options > Integrate all
this now produced a frame name:
Integration 4 Session 2
Initially I thought that I had made an error but looking more closely, the associated filename for this Integration does in fact include the text 'session_1_session_2' and when loaded in the viewer it is both sessions combined.
Possibly the 4th Integration should have also name the frame 'Session 1 & Session 2' or even just 'All Sessions'
Don't get me wrong, the software itself worked like a dream, very simple, this is just more of an aesthetic point really.
Regards..,
Kirk
Hi Kirk @1cm69,
Thank you for sharing this. Can you please indicate on which APP version this occured? I know that this was a bug/or resembles a similar one in an older version.
The frame name should have been Session 1 & Session 2 to indicate both sessions were integrated.
Kind regards,
Mabula
Hi Mabula,
v 1.070
regards..,
Kirk
Hi Kirk,
Thanks, will check this particular issue before the next release 😉
Mabula
Hi Mabula and Kirk,
I thought I would tack my observations onto your post, Kirk. No need to start another topic.
Background: My camera is not cooled and does not have an integrated temperature sensor. In order to temperature-match my darks against lights I designed an Arduino-based, high-precision ambient temperature logger. At the end of a session I use the log to segregate my lights and darks into subfolders having names like 'temp_19.5F' and 'temp_20.0F'.
To make this work in APP, I create custom session names like 'temp_19.5F' and 'temp_20.0F'. It appears as if APP has a problem handling '.' (period). The final integrated stack looks correct but the file names are misleading (see attachment).
I am using APP 1.071
Thanks,
Brian
Hi Mabula,
I've chosen an abbreviated naming convention that APP handles and I like better:
examples "19F5" for 19.0 Fahrenheit, "20F0" for 20.0 Fahrenheit
works well and easier on the eyes.
Thanks,
Brian
