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,
I stack up to 2-3000 frames sometimes including saving calibrated frames so I can get plain alignment on one shot color cameras. So I start to run out of my internal solid-state drive space even though I have a 2 GB drive.
Niw I have an external hard drive that’s fairly fast (200mb/sec 14 Tb drive) so I’m trying to decide which of these two scenarios is faster:
1) keep all the source files and write the the calibrated frames on an external hard disk and use the internal drive only for the integration working storage.
or
2) keep all the source files and space for the calibrate frames on the internal solid-state drive and use an external hard disk for the integration working storage.
I’m assuming option number one would be faster because I’m expecting the integration working storage to be worked a lot harder and that the source files are essentially only read once or a small number of times. Is my assumption correct?
@readyjetty If you're looking for performance during processing then simply copy all files over to your internal drive, process using the internal drive and copy the results back to the external drive.
I guess I should’ve been more clear: My internal drive is a very fast NVMe 2 TB SSD and cannot be upgraded and all the files and stacking procedures requires more than that.
So I either need to put them all on an external hard drive or split them and I’m asking if I split them should I use the internal very fast NVNe SSD as the working file space or for the source files, because I can’t use it for both.
This is just my thinking for your situation. If you had a smaller stack, say 100 light frames, then the performance difference would probably go unnoticed either way. But considering you have up to 3,000 light frames to stack, I think you would see faster results if your light subs were stored on the SSD and you did the final integration to your external drive.
That is a lot of light frames that APP will have to access individually, so over the course of the entire process, keeping the light frames on the SSD would seem to work better. Then if my thinking is correct, APP would only have to write one integration file to your slower external drive.
