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.
Now that Cmd-A is back (YAY, thank you SO much Mabula and team!) - this is less of an issue, but I would love it if for some of my larger projects if it were possible to rapidly load days worth of imaging folders at once.
Maybe I am lucky, but my flats generally dont need updating that often and I can collect weeks of data (arranged into folder by Target_name->by_date and it woudl be super helpful to rapidly load them up, cull the junk and start my workflow.Â
Perhaps I am unique in my challenge or maybe I am arranging my folders badly!?
Hi Paul @xthestreams,
Yes, we need to make that possible, do your frames have a tag in the fits files indicating that they are lights as well?
Mabula
Sorry to bump an old thread, but was there any progress here? I don't have any issues with tags either coming from capturing in NINA or ASIAIR. Coming from another product that has a bulk import feature, I build a folder structure like this:
- Root folder of Target
- session_1
- LIGHT
- FLAT
- DARK
- BIAS
- session_2
- same format, continuing for each session needed. Each folder contains its relevant subs.
- session_1
I'm not even sure the folder structure is needed per-sub either (but likely per-session), because the FITS headers always contain the filter or type of sub. If the folder structure is respected though, we don't have to worry about dates either, if for example, flats are taken days after our light frames.
Â
Thanks again for considering this.
Hi Bob, @tetchy1
This is not yet implemented, but for sure on our ToDo list. We will first release APP 2.0 with project save/load and a full manual after which we will work on the file/folder/recursive loading 😉 thanks for bumping !
Please know that "because the FITS headers always contain the filter or type of sub" is not accurate... it all depends on the capture software/hardware used. Especially older FITS files or FITS from professional telescope archives/teams do not always have that information, some have propietary tags... even the IMAGETYP tag used these days by many software packages to indicate LIGHT/DARK/etc is not even officialy in the FITS specification.
The implementation that we will implement will try to use a folder structure like you indicated and it will look for the relevant tags of course 😉
Mabula
Hi Bob, @tetchy1
This is not yet implemented, but for sure on our ToDo list. We will first release APP 2.0 with project save/load and a full manual after which we will work on the file/folder/recursive loading 😉 thanks for bumping !
Please know that "because the FITS headers always contain the filter or type of sub" is not accurate... it all depends on the capture software/hardware used. Especially older FITS files or FITS from professional telescope archives/teams do not always have that information, some have propietary tags... even the IMAGETYP tag used these days by many software packages to indicate LIGHT/DARK/etc is not even officialy in the FITS specification.
The implementation that we will implement will try to use a folder structure like you indicated and it will look for the relevant tags of course 😉
Mabula
Sorry, I should have clarified that my captured data from ASIAir and NINA has the right headers. I've definitely had to batch edit some FITS to fix headers from other sources though. Thanks again for the update!
Â
Hi Bob, @tetchy1
Okay, thanks for the feedback. We will try to make this happen in a logical and similar way as other applications out there 😉
Mabula
