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 am working with Beta 2 and culling frames -- I sorted on quality from worst to best and double-clicked on a frame, then have been using the down-arrow key to select the next one. Several times during this session, I have right-clicked on the frame selected in the frame list (and showing in the previewer) and selected "delete". Assuming that the correct one would be selected, I didn't check the bright-red text (after all, I was sure I wanted to delete the selected item!). Imagine my surprise when I got back to the frame list and the offending frame was still there, but one of the good ones was missing.
You'll have to take my word for it that the correct frame was selected and was the one on which I was right-clicking. Once I was alerted to the problem, I started noting the file names before doing the selection, which allowed me to reject deletion when APP chose the wrong one(s). It is an intermittent -- certainly when I click "No, keep my files" in the confirmation dialog and repeat the process, the correct frame is always selected.
Please allow me to suggest that this one be flagged red-hot. As a software developer, I put the ones that destroy user data right at the top. If you're unable to repro and need a video or something, please let me know.
Thanks!
It does not seem to be choosing the preceding or succeeding frame for deletion. Perhaps the one that would be in the same position in the unsorted list, or sorted in a different order?
ETA: If I go back and left-click on the already-selected frame, and then right-click, it seems to reliably select the correct one.
Hope this helps.
Hi Rick @rickwayne,
Thank you for reporting this. I will have a good look at it 😉 But yes, you do need to first select the frame with left button before you can apply the right click to remove/delete that particular file from the list. That is how it is currently implemented. I will see if I can make it work more intuitively with direct right mouse click.
Mabula
Well, that makes sense from a programming standpoint. But, yeah, from a user-experience one, if the frame is already highlighted in the frame list and the user right-clicks on it, I don't think it's too unreasonable for them to expect that that frame be the one to which the context-menu action is applied!
Thanks for looking into this Mabula. Other than that, so far, so very good on the beta. I did have one odd result -- one channel in an LRGB integration coming out black until I deselected everything but those frames and did a re-integration -- but that conceivably could have been operator error. I will attempt to repro that one and post it (along with the data) if I can do so.
Really excited to see version 2 coming along. I assume that this will mean those of us with "owner" licenses will need to pay for it, I for one will not hesitate to do so. APP has been excellent value for my investment so far.
