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 am having trouble registration of integrations from different sessions when I want to combine say narrowband with RGB, I'm not sure what I am doing wrong! If I use Dynamic Distortion Correction I get a very strange effect with huge distortion but apparently good registration. If I don't use Dynamic Distortion Correction the registration is not very good with the stars easily seen to not align, see attached pics. I have tried with and without same camera and optics, I have tried increasing the distortion margin to 0.01 and even 0.1, I have tried quadrilaterals and pentagons and so far I have not been able to resolve this!
I have seen this before and forgot what was the cause, aaah! 🙂 Are the frames all from the exact same camera?
Combining narrowband with RGB is a bit tricky at the moment (in the sense that we need to make that easier). What happens if you split the RGB channels and then go register all of them together?
@vincent-mod Thanks for the reply, yes, all frames are from the same lens and camera. It isn't specific to this lens, I have had the same issues with other lenses, but not all the time. I make sure I check what the registered frames look like before integration! Often if I get the strange distortion I simply disable the dynamic distortion correction and the registration works well, but in the case above it did not. Also in the case above I have split the RGB into individual channels, they register to each other fine but not to the Ha channel.
Would it help to increase the star count to get a better registration maybe?
@vincent-mod I had it set to 3000 stars at analyse stars in the above example, but I also tried 6000, this didn't seem to make any difference! Eventually I used a different version of the Ha data which would not normalize with the other data (as it was colour!) but it did register, so I saves the registered frames and used Photoshop to create various versions with Ha, RGB and UHC. I would still like to know why I get the huge distortion with the Dynamic Distortion Correction at times, this is not the only time!
So I asked Mabula about this and this kind of issue sometimes happens when the data doesn’t actually need to be corrected for distortion. Apparently the algorithm can then cause this.
@vincent-mod I usually check to see what the registered frames look like and disable the Dynamic Distortion Correction if the distortion becomes extreme. But in this case the registration was quite poor without it! Usually it isn't.
Mmm, that would likely be a data issue then. Something we might have a look at, Mabula is on a short holiday now so if you want more information on that, remind me in a week. 😉
