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.
Hello
The phenomenon I encountered is as follows.
First I loaded Light, Dark, Bias, Flat in 1)LOAD.
Then I clicked Integrate in 6)INTEGRATE.
Next I changed cold column kappa and hot column kappa in 2)CALIBRATE.
Subsequently When INTEGRATE was clicked in 6) INTEGRATE,
Processing was not started from 2) CALIBRATE.
I want to change calibrate settings and reprocess from 2)CALIBRATE.
To do this, it was necessary to clear the Light and reload the same file.
This procedure feels complicated operation.
It should not be necessary. But to be safe, if you changed something in tab 2 after song the integration already, you can run the calibration in tab 2, and then go to integrate. I think any churned in tab 2 will be incorporated during a second integration. You might be able to see what values are used if you look back through the log screen that always stays open.Â
@cwm2col
Hello Colm O'Dwyer
Â
Thank you for answer.
Running CALIBRATE reflected changes.
Then I executed INTEGRATE.
Certainly, Light reloading is not necessary, but I do not feel much difference in terms of operation.
Perhaps I think that my usage is different from what APP assumes.
