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 exports, next newbie question ...
When loading the frames, I can (or need) assign a channel/filter as the first dialogue after selecting the frames on my disk.
- What is the consequence, if I select e.g. for OSC data "RGB", what if I (wrongly?) assign e.g. "Green"?
- Do I need to choose the same channel/filter for the flat frames as I choose for the corresponding lights?
- What shall I choose for Ha-OIII filter with OSC camera, when integrating with algorithm "Ha OIII color" ?
I guess "RGB" ... as there is no "Ha-OIII" choice.Â
What happens, if I choose e.g. "Ha" ? - What, if I'd chosen "Ha-OIII extract Ha", so integrating to a mono channel. Must I use "Ha" as channel/filter?
What, if I choose something else?
Is there a documentation, what is the result of this channel/filter selection? With respect to
- algorithms?
- naming?
- anything written into the FITS header?
- "pairing" of lights and calibration files?
NB: I know (think to know 😉 that the sessions in the next dialogue are important to pair the lights/flats and also allocate the Bias/darks to the sessions with same gain/exposure time.
Thank you and best regards.
MichaelÂ
Hi Michael @michaelacg,
Thank you again for your questions.
First of all, the question for channel/filter assignment will only pop-up if you enable multi-channel/filter mode in 1)Load. So if not needed, you can simply disable it, just like the multi-session mode.
Yes, the lights and flats need to be assigned the same name, otherwise they won't be matched in the calibration workflow.
The consequence is only for you own and internal APP book keeping. You can assing any name for your own convenience and APP will simply use that name for internal bookkeeping to match the proper calibration frames with the proper light frames. Choosing a certain filter/channel name does not affect algorithms or other automatic features.
If you load Ha-O3 data, it makes sense to simply call the filter Ha-O3 since that is the filter used, right?
We have on our list to implement that if you select one of the narrowband demosaic algorithms like H-alpha or extract O3, that that filter is then assigned in the filter header tag in the resulting integration.
Let me know if this answers all of your questions.
Mabula
Â
