May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
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 would like to make a suggestion for a future release. It would be helpful to be able to use the quality score to determine which lights are included in an integration. I realize one can set an arbitrtary number of lights to include, but that is just a pure number of lights. It would be better if one could take advantage of the quality scores that are assigned to each light. So, for example, to eliminate all lights from the integration whose quality score are 20% less than the quality score of the reference light. The 20% figure is only an example, and that would be a parameter the user could set.
Jean
Hi Jean @jpiquette,
Thank you very much for your suggestion. We have on our issue/todo list noted that we will further improve this. For instance, now the % selector only uses APP's quality estimation. Going forward, you will be able to select which metric controls the % to stack and we will also allow new formula to put in for frame selection.
We will work on this after the 2.0 stable release.
Mabula
Hello Mabula @mabula-admin,
Just to be clear on what I am suggesting...The current % to stack refers to the % of the total number of lights. So if there are 200 lights available and I set the % to 80%, then 160 lights will be stacked. Thus 40 lights are rejected.
My suggestion is that a % threshold based on the quality score of the reference light be used to reject lower-quality lights. So in the above example, suppose the quality scores of 199 of the 200 lights are within, say, 5% of the quality score of the reference light, and just a single light has, say, a 25% lower quality score than the reference light. And suppose I set the threshold % to 20%. Then only a single light would be rejected in this example.
Jean
Hi Jean @jpiquette,
Thank you very much for clarifying that, I understand it. Basically it would mean that the % slider will work either absolute with the number of frames or relatively to the measured metric. I will add it to our open issue to make sure that we add this going forward as an option. Thanks,
Mabula
