MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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.
I am using an ASI 294 MC Pro. I typically take color lights using just a Sky and moon glow filter and Ha using a 12nm Ha filter. I've had good success combining them into an HaRGB image in photoshop. I have been using DSS but am trying the free trial of APP. I've had some success stacking and partially processing my RGB lights but what settings should I use to stack the HA lights?Â
I've seen several posts and videos about stacking Ha, R, G, and B together, about separating Ha from Ha-Oiii images, and stripping out Ha from some other type of image and how to combine your stacked Ha image with your RGB. But I can't find just the settings I should use to stack a bunch of Ha lights. I have the lights, flats and dark flats taken with the Ha filter and the darks for this camera/temp/exposure.Â
What settings should I use on 0 raw/fits and 1 load. (and any other that should be different from rgb lights.) Any help would be appreciated but please remember I am just starting out with APP.
Â
Taylor Blanchard
Hi Norman and thanks for trying APP!
At the moment APP is not able to immediately process narrowband and broadband together. You get to the normalization stage and then it has an error, because 3-channel RGB can't be properly normalized to 1-channel data. We are going to address that so it becomes a non-issue.
In the mean time, the best thing is to load in the RGB lights with the calibration data, go to tab 2, and split the calibrated channels (checkmark lower down in tab 2, then press "save calibrated frames"). You can do the same for the Ha data (extracted with the "extract-Ha" algorithm), add those as lights, add the calibration data to that and save those as well (deselect split channels). Now you'll have calibrated mono R, G, B and Ha frames. These can be loaded in as mono data in APP (without calibration data added as that was already done) and process them all the way to the end. You'll get fully integrated stacks of all these channels and these can be easily loaded in to the "RGBCombine" tool.
If anything is unclear, I'm happy to explain further.
Vincent,
Thanks for the response. It seems clear on how to combine the stacks.
However, I think my question was too general. Speaking just about Ha lights taken with a OSC camera using an Ha filter:
ON TAB 0
Do I still set pattern to RGGB?
Should I set algorithm to Ha?
Should I still check force Bayer/X-trans CFA?
ON TAB 1
Should I check Muti-channel/Filter processing?
ON TAB 2
Your response said to check split channels so that's clear.
Do any of the other tabs need settings different from OSC broadband stacking?
Â
Thanks!
Tab 0: If the header of your files contains the flag for the pattern, then APP will apply the correct one automatically. If not, only then would you need to do this manually. If you want to extract Ha from color data that was taken with a dual-/ tri-band filter, you select the "extract-Ha" algorithm. The force CFA is only to be used when you get a grayscale result, which happens when the header is not providing correct data to APP. Normally you don't have to change these.
Tab 1: Ony when you have data taken with various filters for instance, but as this is OSC data with one filter, it's not required. When you load in the mono data (R, G, B and Ha) you can leave this selected (as it is standard anyway, so no need to change there).
Tab 2: Yes and then calibrate and save the registered frames, also in this tab.
If you have all data in mono, so: R, G, B and Ha and you load these into APP and assign their filters (usually also done automatically), then everything can be set back to the standard settings. You can load the data in, go to tab 6 and press integrate.
Got it!
Â
Thank you so much!
Â
Taylor