June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
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.
Hi
One thing has been annoying me for quite some time:
If one file fails to register, the whole process stops. Why?
Why can't the process just continue with the files that did register? You can always go back and re-register (start over) if you want to include that file.
Several times I have experienced that I start a process including several hundred files which I know will take hours, but when I get back to the PC the darn thing has stopped . This is not user friendly!
Display a message on the screen, but please, pretty please, let the process continue with the registered files.
Hi Heno,
Yes this is indeed the case and something Mabula will change, good point.
Hello,
I second what Heno has said. It's discouraging to set the computer to process overnight a large batch of files, and then discover in the morning it didn't go because a few files failed register.
I just had a multi session fail, which consisted of data of the same subject using the same equipment over 5 nights. Lights from each night's session were previously calibrated, saved as calibrated lights, and successfully registered and integrated within each session. When I then went to integrate all the calibrated lights from the 5 sessions into one master integration, 12 of the 600 or so calibrated lights failed to register. Now, the reason I had integrated the individual sessions was to make sure that I had good lights that would register (because I have had this problem before). So I was surprised that when going to a big multi session a few of the known 'good' calibrated lights failed to register under this circumstance.
But regardless of the reason these calibrated lights failed to register in a different integration, I just want the system to continue the integration process without the lights that failed to register. A warning message that a few light frames failed to register and therefore were not included in the integration is sufficient. Thank you!
P.S. I want to say that overall I am quite enjoying APP!
