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.
@astroshed Yeah..... I've noticed his estimates on how long a release will take have become wildly optimistic. Shoot, I'm still looking forward to saving / loading projects, promised for v1.085 back in January 2021.
The problem with the APP is this: There is a company called Aries Productions. However, over the years it has become clear that Mabula is both the sole owner and the sole employee of this company. As a result, if Mabula catches a cold, work grinds to a halt, development and updates come to a standstill. For some reason, there is no one else to provide support. There used to be Vincent, who, even if he couldn’t meet all requests and expectations 100%, went to great lengths to offer support. Now he’s gone too. Issues raised on the forum either go unanswered or are attempted to be addressed by users who have some familiarity with the APP, but this support is insufficient.
Hundreds of people have purchased the app or are paying an annual subscription. A price increase was also implemented recently. The question that comes to mind is, ‘What if Mabula were to suffer a serious health issue? Would APP users be left to fend for themselves amidst all the bugs and shortcomings, without even an user manual?’
Last year in June i decided to get a renters license. I´m still very happy with APP, though Siril made a huge leap forward with the integration of the Syqon / VeraLux Scripts. I still think my pictures right after integration look better in APP than in Siril. Also, i don´t know about a better software to do mosaics (apart from PixInsight, which i don´t own).
I don´t know if i will renew my license in June. Of course i´m also concerned about APPs and Mabulas future. But then, the programm works well for me. Any improvement are highly anticipated, but for now i think i get what i paid for.
But i agree - there has to be a change in transparency.
@easylink I agree that APP is the most successful software when it comes to stacking. That’s why, in the photo shares on Cloudy Nights, I see that many people use APP for stacking and Pixinsight for processing. So, is Pixinsight really more effective when it comes to processing? Or is it simply that, due to the abundance of tutorials, the large number of supporters, and the many providers offering paid courses and webinars, people are using Pixinsight more effectively? If there were a comprehensive and detailed user guide, along with more, more accessible and more explanatory video tutorials, would APP be as successful as Pixinsight when it comes to processing? We don’t know! Because none of the things I’ve mentioned exist.
Of course, no company or software has a guarantee of the future. I am not claiming that multi-partner and/or multi-developer competitors of APP will survive forever. Please do not infer such a meaning from my previous post. But it is important to recognise that APP users currently need more support than is currently available.
We see progress "April 9 ... within 24 hours". So let Mabula work, and I am really curious and looking forward to seeing the performance and qualitative improvements.
We see progress "April 9 ... within 24 hours". So let Mabula work, and I am really curious and looking forward to seeing the performance and qualitative improvements.
I just did update the screen and did see also the new message 🍻 🍻 🍻 🍻 🍻 🍻 🍻
I agree with all the comments here, the software is good there is no doubt about that, but support is severely lacking, especially for noobs of the software, a one man band, as APP is, will always struggle to keep up, as life can and will just get in the way. There must be people out there that are very clued up on APP and could help on this forum, as moderators or something like that, as at the end of the day, the Pixinsight forum now is not monitored at all by the Pixinsight developers, this is a fairly new thing, and they stay away from it, not sure I agree with this, but there is enough people in there to all help each other.
anyway looking forward to trying this new APP version, as it’s the only stacking softer I can find that does not give me diamond shaped stars, WBPP is terrible for this.
I did already try the new APP Beta 40, and whenever I try to chose / set any save directory, then it freezes, I am using Windows 11 64Bit ( I did create a new thread for the BUG )
@artem I have also noticed this sadly, I thought it was me, but tried in 2 systems and the same in both. so have gone back to beta 39 and will wait a month or so for the bugs to be sorted, as there will be a few me thinks
@astroshed Are you refering to the individual directories (calibrated, normalized subs…) or the main save directory? Changing the mail directory works good for me (Win 11)
@easylink it seems it crashes no matter what I do at start up, the programme just does not seem happy at all, will try another re-install and see, although done that 3 times already ☹️ it may be I need to uninstall older version first 🤷🏼♂️
@astroshed Must be a problem with your configuration and the new version. I just installed it over the last one. No problems so far. No freezes or crashes. Maybe a GPU issue?
It's throwing up an error when Local Normalisation Correction 2.0 is enabled, then giving that write error at the end and not creating the stacked file..
Disabling Local Normalisation Correction 2.0 allows the stack to complete without error.
This is using the same data that previously worked in beta39.
Hi all, thank you very much for all of your concerns. All is okay with me and regular support will resume, i have been working very hard and 2.0 with the manual is very close.
I am very sorry to read about your issues with beta40. Can you please provide some more details about the bug(s) that you encounter? like which Operating System and OS version and which settings that you use?
It is clear, that the combination of Bayer Drizzle with the new LNC 2.0 has a bug. I will work on that tomorrow and will report back.
Regarding the error with choosing the save locations, I really need to know on which Operating System this happens, and which version of the operating system.
For Linux, you need to have at least GLIBC 2.34. Is this the case when you are using Linux?
The native file/directory chooser is now provided by a different 3rd party library and on all of our test systems this works really well, so any information that you can give me will help me to solve this apparant bug as soon as possible. This new version of the native file/directory chooser works much better and faster on all of our systems and it even provides CMD+A on macs which was in high demand by mac users.
Hallo Mabula, dieses Problem betrifft die Linux- (Ubuntu 26.04), Windows- und AppImage-Versionen. Beim Versuch, im Tab „Kalibrieren und Integrieren“ einen Speicherort auszuwählen, öffnet sich die Dateiauswahl nicht – der Button ist ausgegraut. Die einzige Option ist dann, die Anwendung zu beenden. Bei Verwendung von Bayer Drizzle mit LNC 2.0 wird der Stack nicht gespeichert; es erscheint lediglich eine Warnung („Beim Speichern ist ein Fehler aufgetreten…“).
My GLIBC version is (Ubuntu GLIBC 2.43-2ubuntu1).
Beste grüße.
This post was modified 2 months ago 2 times by minusman
I am on Windows and believe the issue may be that there is nothing to save when using LNC 2.0, hence the error. Disabling LNC 2.0 stacks and saves the image fine. At 28% stacking with LNC 2.0 on, i get this error;
Error message: java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
Cause: Index 0 out of bounds for length 0 astropixelprocessor@2.0.0-beta40/com.ariesproductions.statistics.c.b(FastMedianSegmentDouble.java:138) astropixelprocessor@2.0.0-beta40/com.ariesproductions.statistics.c.c(FastMedianSegmentDouble.java:101) astropixelprocessor@2.0.0-beta40/com.ariesproductions.statistics.c.a(FastMedianSegmentDouble.java:12) astropixelprocessor@2.0.0-beta40/com.ariesproductions.localNormalizationCorrection.a.a(LNC2FirstDegree.java:330)
You can OK the error, but the get this at the end of the stack;
Ok, so did another re install, and then noticed a windows update was needed to be installed, so thought may as well do it now, so did that re booted and APP seems to be working now, so not sure what was going on there, not really done a full test yet, but fingers crossed and will report back
I am on Windows and believe the issue may be that there is nothing to save when using LNC 2.0, hence the error. Disabling LNC 2.0 stacks and saves the image fine. At 28% stacking with LNC 2.0 on, i get this error;
Error message: java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
Cause: Index 0 out of bounds for length 0 astropixelprocessor@2.0.0-beta40/com.ariesproductions.statistics.c.b(FastMedianSegmentDouble.java:138) astropixelprocessor@2.0.0-beta40/com.ariesproductions.statistics.c.c(FastMedianSegmentDouble.java:101) astropixelprocessor@2.0.0-beta40/com.ariesproductions.statistics.c.a(FastMedianSegmentDouble.java:12) astropixelprocessor@2.0.0-beta40/com.ariesproductions.localNormalizationCorrection.a.a(LNC2FirstDegree.java:330)
You can OK the error, but the get this at the end of the stack;
Thank you very much. Indeed, I have identified this issue and i am working on it. I will try to release a fixed version tomorrow, I will keep you updated.
Okay, thank you very much for your feedback. As you can read above this, I am working to fix the 2 reported issues at the moment. I am able to reproduce them and thus fix them. I will try to release a fixed version for the 2 mentioned problems tomorrow.
I have fixed the issue with LNC2.0 and (Bayer)Drizzle for beta41, will try to release it later today 😉 when I have also solved the other reported issue.
