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.
Hello,
I just updated to beta33. Like new features!
However, when in Load Tab, I enter the Object Name (as usual). Load my frames.
Go to Integrate Tab - it asks me for the name again! It used to be propagated from the Load tab.
I give it a name, integrate and after that the Object Name in the Load tab changes to the name from my my raw light fits files.
Something fishy is going on...
Hi @maxthebuilder,
Excellent, thanks for the feedback!
Thank you very much for the Object name behaviour. We did change something in the beta33 release... we now try to use the OBJECT tag from your FITS files. But your explanation makes it clear we need to adjust it a bit better still. I would propose that if the user changes the OBJECT field himself, we just let it propogate as before. Otherwise, we suggest the OBJECT tag name to the user like we do now. Would that work well?
Mabula
Mabula - yes, that would work - thank you!
Not a huge inconvenience, but the same thing is happening to me as well, also with Beta34.
I populate the name in tab 1) and do the usual, then I am again prompted to set the object name almost immediately after I press integrate in tab 6).
I wanted to just chime in and say yes, this would be a huge QOL change. Every time you hit the integrate button, it doesn't matter what you have in the object name field, it asks you to enter it again. A change back to the previous behavior would be very welcome and thanks for working on this.Â
Hi @maxthebuilder & @wheeljack & @menesesc83,
I will roll back those changes in beta33 for the object name in the next release 😉 Will try to release it before next monday !
Mabula
Hi @maxthebuilder @wheeljack & @menesesc83,
APP 2.0.0-beta35 has this fixed, please see the release note, the behaviour is like in versions prior to beta33, but if the user does not provide a deepsky object name manually APP will already get the object name when you load fits files with the FITS OBJECT tag present. If the name is provided manually, or found automatically, APP will not ask again for the deepsky object name when you start 6) Integrate. I think this is the best behaviour. To be clear, if you enter a deepsky object name manually, APP will not automatically overrule it with the found FITS object tag.
- FIXED & IMPROVED OBJECT NAME recognition from FITS OBJECT tags in light frames
Versions 2.0.0-beta33 & 2.0.0-beta34 would always ask the user for the object name when you start an integration, this is not wanted behaviour and it was introduced in beta33 where we have started to use the FITS OBJECT tag to get the object name of the imaging project. This change makes the behaviour now as prior to beta33 with the following improvements: if the user does not enter an object name in 1) Load in the Enter DeepSky object name: field, APP will put an object name there when light frames are loaded that have the FITS Object tag present, so the name is automatically found and the name will be put in the Enter DeepSky object name field. The other improvement is that if APP finds the name automatically or if the user enters a name manually, 6) integrate will never ask for the object name since it is already provided. These 2 improvements ensure that the behaviour is similar to version prior to beta33 and it does enhance user experience by finding the object name automatically if the user does not provide it manually.
- Â
Hi Mabula,
Thanks for working on this!
I tested - better but, sorry, I still don't quite like it.
So, I enter the name in the LOAD tab - it propagates to the INTEGRATE. This is working fine. But...
I would like to still have a confirmation dialog in INTEGRATE (as before).
I often do more than one integration run on the same target.
I change some parameters (# of frames, LNC, MBB, drizzle, etc.) and need to be able to change the name accordingly and to my taste.
Thanks!
Max
Hi Max @maxthebuilder,
Okay, I assume that you have tested it with the 2.0.0-beta35-test1 version that is available in the downloads section?
I would propose to solve that last nuissance, by having the field to enter the deepsky object name also visible in 6) Integrate, just above the integrate button. Then if you need/want to change it when it is already poulated manually or by APP, you can simply change it above the Integrate button and click integrate. Then other users that don't need to change it, will simple click integrate and they will not need to see the popup window for the object name. That should be best for user experience overall I think?
Mabula
Hi all,
I have changed it now again based on Max's @maxthebuilder feedback:
- FIXED & IMPROVED Deep Sky / Comet Object name recognition from FITS OBJECT tags in light frames
To start with, we have changed the label on the field to enter the object name to Deep Sky / Comet object name from Enter DeepSky object name and we have changed the color of it. Versions 2.0.0-beta33 & 2.0.0-beta34 would always ask the user for the object name when you start an integration, this is not wanted behaviour and it was introduced in beta33 where we have started to use the FITS OBJECT tag to get the object name of the imaging project. This change makes the behaviour now as prior to beta33 with the following improvements: if the user does not enter an object name in 1) Load in the Deep Sky / Comet object name: field, APP will put an object name there when light frames are loaded that have the FITS Object tag present, so the name is automatically found and the name will be put in the Deep Sky / Comet object name field. The other improvement is that if APP finds the name automatically or if the user enters a name manually, 6) integrate will never ask for the object name since it is already provided. These 2 improvements ensure that the behaviour is similar to version prior to beta33 and it does enhance user experience by finding the object name automatically if the user does not provide it manually. Finally an identical field to enter the object name is added to menu 6) integrate, just above the integrate button, so you can change the object name now there as well, which is useful if you want to create multiple integrations with different names for your own convenience. Both fields to enter the object name will mirror each contents automatically.
Just tested beta35 - perfect, thank you!