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'm curious if there's a fix for this or whether I'm doing something wrong. This happens every time I use APP for this particular workflow. Details:
My camera is the ZWO ASI2600MC Pro, and my filters are the Askar Colour Magic D1 and D2 set. I run APP on a Macbook Pro 16-inch, 2023, Apple M3 Pro processor, and 16GB RAM on Sequoia 15.4 I'm stacking OSC data taken both with and without filters, and my workflow is to bring in all of the frames (filter and no filter) initially. I stack the non-filtered subs first, with all the D1 and D2 frames deselected in APP. Then I deselect those and select D1 (H-a and OIII) subs, extract Ha with the proper algorithm in APP, stack. Then I select the D2 (OIII and SII) subs and extract OIII from D21 and D2, stack. Then I select only the D2 subs and extract "H-alpha" (SII) to stack, and when going to integrate (and all the previous steps), APP throws a message (attached) every single time.
Is it something in the multiple selecting, deselecting, etc, plus changing the algorithm in between, that gets APP confused for some reason? Is this an error which others are seeing as well?
Thanks in advance for suggestions.
-Kevin
Hi Jon.
I am still on beta-37 ... but I strictly adhere to an advice I read: to quit and restart APP for each integration.
What I read is indeed that "APP gets confused", by not completely resetting all internals for a new integration.
With this strict quit&restart I did not have any errors.
Hi Jon @macejk,
I am not aware of the problem. Can you check for me if it still happens in beta39 and let me know if that is the case or not?
If the problem exists in beta39, it would be very helpful if you can upload your data to our server including a documentation of your processing workflow, so I can repeat your steps and then find, analyse and solve this issue.
@michaelacg, I process and test a lot and I can always simply clear APP with the clear button in 1) Load and successfully process another set. The clear button internally removes all processed information, or at least it should, it is there for that purpose. If it does not work as expected we will need a clear example so we can test and solve it 😉
Mabula
Hi Mabula.
I did not know the clear button - just followed the advice I have read somewhere (forgot it, where), because this helped.
--> I will switch to use the "clear button" ... and let you know, if I see any problem.
Ah, okay Michael @michaelacg 😉 let me know if the clear button works as expected then !
Thanks !
@michaelacg Hi Michael-
I would always quit APP (or at least use the CLEAR button) in the past before I started doing narrowband imaging. When doing NB, it's extremely inconvenient, especially with several nights of imaging on a given target, to have to load everything (lights, flats, darks, bias) in 3-4 times to separate out the broadband, H-a, OIII, and SII data. It's MUCH more convenient to load everything in, select/deselect as needed to pull out the channels and do the integrations, but usually after 3 rounds of this (BB, H-a, OIII), APP craps out with an error message by the time I get to the SII.
Perhaps this will be resolved in the new APP with its new narrowband routines.
This probably isn't the place to ask this question, but based upon the pricing infographic I'm seeing at the top of the APP pages, I'm guessing that, as a renter, there's no "small fee" upgrade path to be able to continue renting the new version?
-Kevin
Hi Kevin @macejk,
Thank you very much for your feedback. That "craps out with an error message by the time I get to the SII" has never been reported to us and is thus not on my issue list. I have added it now with your problem description so I will try to test, analyse and fix it 😉
It would be great if you can let me know if the behaviour at least now is better with the new algorithms, since you can immediately put out 4 extractions from 1 data set.
"This probably isn't the place to ask this question, but based upon the pricing infographic I'm seeing at the top of the APP pages, I'm guessing that, as a renter, there's no "small fee" upgrade path to be able to continue renting the new version?"
For Renter's there will never be an upgrade fee 😉 Only the yearly subscription. We did have to increase the price of the yearly subscrption now. We have not done that for many years, last time was before the covid-19 pandemic I think.
Hope that answers your question?
Mabula
@mabula-admin Hi Mabula-
Thanks for your reply, and I did not mean to disparage APP in any way, truly. I love APP, and it's an integral part of my work in AP ... I literally could not do AP without APP! I also have a knack for finding small issues with software - error messages at least - either because of something intrinsic to the code or something I'm doing wrong within the software. Usually the latter.
I very much look forward to trying out the new version of APP, as it sounds like it can greatly speed up my flow. I may wait until the manual is out, however. APP is SO much a part of my flow that anything that changes significantly, and which I don't understand, might slow me down unless I can consult the manual along the way. Plus I just renewed my renter license back in September.
-Kevin
Dear Kevin @macejk,
No problem at all, I did not take it in a bad way at all 😉 I was merely surprised about this issue because no on had brought it forward yet. Thank to you it is on my issue list now, so thanks 😉
Glad to read that APP is so valuable for your workflow ! Thanks for renewing !
Mabula
