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.
Hi,
So, I stack, say, 100% of my subs, try processing it, then decide to try, say, 90% instead. As well as having to load everything up again (please can we have default loading options soon?), it seems APP has to go through everything else again - calibrating, normalising, integrating etc.
If I've already been through all this, and all I want to do is restack a smaller percent of my subs, what are the top tips for being able to speed things along a bit?
Thanks, Brendan
PS A user manual would really, really, really, really, really help
I have thought about this as well. I’m guessing all the calculations have to be kept on hand as a temp file until you exit or indicate you are done. It would be a nice feature, though. Maybe this should go into the request for changes forum?
There are a few helpful guides people have done and some YouTube videos. It’s a bit of a learning curve but I’m discovering most of the time the default options done everything I need.
Hi,
So, I stack, say, 100% of my subs, try processing it, then decide to try, say, 90% instead. As well as having to load everything up again (please can we have default loading options soon?), it seems APP has to go through everything else again - calibrating, normalising, integrating etc.
If I've already been through all this, and all I want to do is restack a smaller percent of my subs, what are the top tips for being able to speed things along a bit?
Thanks, Brendan
PS A user manual would really, really, really, really, really help
Hi Brendan,
You can simply use the stack percentage slider at the top of menu 6) Integrate to only stack the best 90% of your images 😉
As promised, APP 1.084 will be completely about save/load settings and complete projects.
And a full printable manual is promised to be there soon as well.
Mabula
I have thought about this as well. I’m guessing all the calculations have to be kept on hand as a temp file until you exit or indicate you are done. It would be a nice feature, though. Maybe this should go into the request for changes forum?
There are a few helpful guides people have done and some YouTube videos. It’s a bit of a learning curve but I’m discovering most of the time the default options done everything I need.
Yes indeed, APP 1.084 will be able to keep the status of complete projects in a saved file, so you can reload it in the next APP session. THen you can immediately continue where you were the session before 😉
You can simply use the stack percentage slider at the top of menu 6) Integrate to only stack the best 90% of your images 😉
Sure, but then it seems to through every module again, which I don't quite understand. I'd have thought all the pre-processing would still apply and it could just stack the changed percentage? I've been looking to see whether I can for example use masters to avoid integrating all the calibration files, but I have to say I find the mixture of all the files in the working folder very confusing - without a filename actually saying 'master' in it, I really don't know which is which.
I've been looking to see whether I can for example use masters to avoid integrating all the calibration files, but I have to say I find the mixture of all the files in the working folder very confusing - without a filename actually saying 'master' in it, I really don't know which is which.
MD == Master Dark
MDF == Master Dark Flat
MF == Master Flat
MB == Master Bias
And, yes, reusing masters certainly saves processing time. Do make sure that your lights have the same gain, offset and temperatures as the master dark and master bias if you use one. If you don't use a master bias then the lights also need to have the same exposure time as the master dark. Flats you should shoot with every imaging session though, if you don't disconnect the camera from the telescope, you may be able to reuse them and, in that case, the master flat.
Great advice, thank you. 🙂
I think this is a big deal and will be appreciated. The other might be a a PC Benchmark profile with estimated processing times for registration and integration of a couple data sets. Say 1-50, 50-100, 100-150 frames etc utilizing cpubenchmark.net or similar benchmark standard. Might start a thread asking for people to share their profile, benchmark and time it took them to process. https://www.cpubenchmark.net
Example:
I am working on a 4 panel mosaic utilizing 130 frames from an ASI 1600. My star count is set at 2000 (and any other pertinent setting that might affect performance greatly)
My processing times are:
Registration Time: X hours
Integration time: X Hours
My system is:
Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz 3.50 GHz, 32.0 GB RAM and Windows 10 x64 OS
Class: Server
Socket: FCLGA2011
Clockspeed: 3.5 GHZ
Turbo Speed: 3.9 GHZ
Cores: 6 Threads: 12
Typical TDP: 130 W
Other names: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
CPU First Seen on Charts: Q2 2013
CPUmark/$Price: 38.99
Overall Rank: 631
Last Price Change: $238.02 USD (2021-08-24)
John
