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 Mabula,
Last night, 2019-03-24, I completed a second night of M101 in Ha. The first night was on 2019-02-17. In total I have 3.1 hours total integration time. Today I tried creating a stack that combines both nights. I do know about APP's multi-session and have used it with success in the past but I've used it only in the context of matching Lights and Darks by temperature in a single night. Now I have two nights, and I am running into problems. You may have guessed that I don't have a cooled camera.
I've attached a screenshot. Explanation follows:
Each night I capture a new set of Bias and Flats. Those I load and assign a session name of '20190217' and '20190324'. The Darks span the temperature range of 19.5F to 22.5F on the first night and 27.5F to 31.5F on the second night. Since the temperature range is large I divide the Dark frames into four sessions: '20190217_19F5_20F0_20F5', '20190217_21F0_21F5_22F0_22F5', '20190324_27F5_28F5_29F0_29F5', and '20190324_30F0_30F5_31F0_31F5'. The last step is to load the Lights. I know their temperature so I assign them to the proper session.
The problem is this: the Lights know about the Darks but don't know which Flats and Bias to use. The reason, as best I can figure, is that I can not assign more than one session to the Lights. I would like to put a check mark on both '20190217' and '20190217_19F5_20F0_20F5' but the check mark controls are behaving like radio buttons.
Is there another way of accomplishing this besides purchasing a cooled camera?
Thanks,
Brian
Â
Hi Mabula,
I found a workaround. In computer parlance I had to flatten the file system. This meant that I had to make duplicate copies of the Bias and Flat frames so that at the end there was just four sessions not six: '20190217_19F5_20F0_20F5', '20190217_21F0_21F5_22F0_22F5', '20190324_27F5_28F5_29F0_29F5', and '20190324_30F0_30F5_31F0_31F5'.
Enjoy your Sunday evening!
Brian