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.
I often use Dual NB filters on my OSC set up, and use the Extract Ha and Extra Oiii options to create Ha and Oiii integrated subs. I then use these in the RGB combine tool.
When I use Ha, Oiii and Sii filters, the RGB combine tool knows to assign the right channel/filter.
Given APP has just done the extraction for Oiii and Ha, and naturally the next step would be to combine, still using APP, you would expect the software to know to assign the right filter to make HOO processing that little bit easier. It's a small change, but a welcome improvement for the inexperienced.
I may be missing something, but APP does add a filter tag when you've used extract-Ha or OIII right? In the RGBCombine tool you can then select the algorithm you'd like to use, which is just a preset, if we make assumptions there I'm not sure that will work for everyone. Your point is that APP would then automatically select HOO I think?
When you load the raw FITS from an OSC, you assign a filter - it defaults to RGB, but you can change it.
So this means I have both Oiii and Ha on this same labelled filter.
When you go to Extract the Oiii or Ha, this filter doesn't get changed. The filter for my Oiii extracted image is "RGB", the filter for my Ha is the same "RGB" (or in my example, I loaded and assigned ALP)
For example, I named the filter ALP to represent the filter I used on my camera at the time. When I go to extract the Ha or Oiii at Integration, I have to knowingly insert Ha or Oiii into the filename otherwise there is no indication at all what the FIT file is when I load them into the RGB combine tool. See attached screenshot. The only reason I know it's Ha is because I named it Ha.
The simple request here is that - given APP created this extracted file, it should include/alter/update the Metadata to now reflect the Filter or some other field that RGB tool could reference so that people aren't making mistakes. Here, in the screenshot, you can see the channel description is (relatively) useless at this stage, and filter is set to Custom.
A user, at this stage, given APP created this file, and we're doing an action from APP itself on a file itself produced, I should just be able to add these automatically to this tool and it knows what filter/colour to assign where.
Â
