Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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 have a 6 panel Ha and OIII mosaic that has been doing the mosaic registration for almost a day.  It is making progress but very slowly.  I have 8GB (16GB total RAM) allocated to APP and an older 8 core i7 and APP says it is using all 8GB.  I have not had performance problems before so maybe I don't have enough memory allocated to APP for this large of mosaic?  It appears from the task manager that APP is only using a single core for this function.  Below is the relevant output from the console.  I'm not sure why it says 2622 frames to register as I have around 300 taken with the same camera.  Thanks.
Mike
16:01:03 - Multiple View DDC: starting with params:
16:01:03 - Multiple View DDC: sameCamera = false
16:01:03 - Multiple View DDC: calibrate camera = false
16:01:03 - Multiple View DDC: save camera profile = false
16:01:03 - Multiple View DDC: registration mode = mosaic
16:01:03 - Multiple View DDC: frames to register = 2622
16:01:03 - Multiple View DDC: calculating multiple view parameters
16:01:03 - Multiple View DDC: starting no DDC mosaic calculation...
16:01:03 - Multiple View Uncalibrated no DDC Full, Not Same Camera: starting
16:59:12 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 0 RMS 0.68056
18:12:07 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 1 RMS 0.63777
19:39:31 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 2 RMS 0.60386
21:12:17 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 3 RMS 0.57254
22:27:24 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 4 RMS 0.53017
00:05:10 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 5 RMS 0.46541
01:38:26 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 6 RMS 0.35691
03:05:02 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 7 RMS 0.22756
04:32:44 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 8 RMS 0.22535
06:12:00 - Multiple View Uncalibrated no DDC Full , Not Same Camera: iteration 9 RMS 0.22535
06:12:00 - Multiple View Uncalibrated no DDC Full, Not Same Camera: iteration 9 convergence criterium reached
06:12:00 - Multiple View Uncalibrated no DDC Full , Not Same Camera: final solution RMS : 0.22535 on 23564 star pairs
06:12:00 - Multiple View DDC: starting simple DDC full mosaic calculation
06:12:00 - Multiple View Uncalibrated Simple DDC Full, Not Same Camera: starting
08:47:56 - Multiple View Uncalibrated Simple DDC Full , Not Same Camera: iteration 0 RMS 0.67787
11:31:08 - Multiple View Uncalibrated Simple DDC Full , Not Same Camera: iteration 1 RMS 0.62753
14:13:01 - Multiple View Uncalibrated Simple DDC Full , Not Same Camera: iteration 2 RMS 0.59228Â
Â
Hi @leuthold,
The most likely explanation here is that you are trying to register the mosaic from all of the individual subs, right?
If so, that is not the most accurate and definitely not the most efficient way.
First create separate integrations of the mosaic panels and then register those into a mosaic. It will be more precise and much faster 😉
2622 frames is the result of all 2-view connections between all 300 frames in your mosaic. All 2-view connections will be used in the entire mosaic calculation and therefore it will take very long !
The output that you are showing shows a likely convergence to happen within about 10 iterations, so for now, it's maybe worth it to wait for the result though...
Kind regards,
Mabula
Â
Mabula,
You are correct that I'm trying to register everything at once.  It may not be the most accurate or efficient but it is the easiest! 🙂  I'll wait it out and see how it looks.  Thanks for the reply.
Mike
What is the possibility of being able to load everything at once for all panels of a mosaic at once instead of having to integrate each panel separately? Probably low but I'd really like to be able to do that even if it took a bit longer. One of my least favorite things is integration/registration/stacking and APP does great making that easier for a single frame. Thanks.
Mike
ok ... damn. I started registering a multi-panel mosaic last Friday at 11am, it's now Monday 2pm and still busy 🙂
Now I understand why. It's indeed the easy way compared to creating seperate integrations first, I also understand there is a quality difference between these two methods.Â
Clear Skies
Â
Yes, like Mabula mentioned above, it will start doing a lot of comparisons and more complicated calculations which apparently is less precise in the end and takes forever. It would be nice to just do all in 1 go, maybe this will become better in the future, but first putting into panels is the best still.
@joost-verheydengmail-comÂ
Well that explains my current situation. LOL
Oh Well glad I am not the only one.Â
It's better after I increased memory and started using a SSD. The newer versions of APP seems to help too.
However, I've not done another 6 panel so I can't say for sure.
Hope it'll work better for you, the latest version is indeed faster due to internal optimizations.
I guess I should kill mine after 5 days. I was holding out for hope LOL
