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.
How do I stop being frequentkly asked for Licence info?Â
Hi Trevor @woldsweather,
That should not happen after activation of the license on a computer. Which APP version are you using? On which operating system?
Mabula
I have found that changing the amount of RAM in the system automatically causes the license to need re-activating. I found this whilst experimenting some performance issues and was removing and re-adding memory, a better solution would be to record the UUID of the system as this would only change when changing things like the CPU
@mabula-admin Can't get to PC for a few days. Constantly probably not accurate. Maybe once every month or two.
Hi @stastro and @woldsweather,
Okay, yes, the amount of RAM in a computer is used to identify a computer for our license management, so users can use APP on 3 separate computers. Simon, is the UUID a general property of any operating system installation or computer and can any operating system retrieve that property from the computer as far as you know? If so, we can change the computer identification for license management accordingly.
Mabula
Hi @stastro and @woldsweather,
Okay, yes, the amount of RAM in a computer is used to identify a computer for our license management, so users can use APP on 3 separate computers. Simon, is the UUID a general property of any operating system installation or computer and can any operating system retrieve that property from the computer as far as you know? If so, we can change the computer identification for license management accordingly.
Mabula
The UUID would be the operating system (and is generated on a number of factors including date/time), so say for example you have Ubuntu and Windows installed on the same system, each operating system would have its own UUID, and a re-install of the operating system would generate a new UUID. But this would leave you in the following scenarios
1. Windows/Linux Dual boot system wold need a license for Windows and Linux.
2. A re-install would need a re-activation, but this is not an issue as you would not be able to re-use the old one anyway since you re-installed the operating system.
Challenges:
1. If you build a new system, and clone the disk from the old system, the UUID is also cloned, so you could end up running two instances on one license.
2. If you build a new system, and move the boot drive from the old system, no new UUID is generated and would not cause a license issue.
Suggestion:
1. The ability to choose a license slot (1, 2 or 3) when applying the license file, as I have been playing around with CPU and Memory, it ended up clearing the license from my working system, the ability to replace a system in a particular slot would be a good option.
2. The UUID of the operating system could be a good solution, especially if like me, I experiment with different memory configs and CPUs with the same OS installed.
To find the Universal Unique Identifier (UUID) for a Windows installation, you can open an administrator command prompt and type the following command: wmic path win32_computersystemproduct get uuid. I need to find the non WMIC equivalent since WMIC is deprecated in newer versions (24H2), for Ubuntu you would get this from cat /sys/class/dmi/id/product_uuid
3. New UUID - Needs new license
The only problem would be the cloning, but then how many people would actually clone a system and keep both systems running, that's pretty much an outlier right there.
Â
Regards
Simon
Â
