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'm trying to process two sessions of data, I've done this workload with settings before with APP without problems and wondering if you've run into this error yet with the new release?
2 multi-session with nband filters, master flats and master darkflats for each and single master dark. I've run the workload twice now, mostly the same settings, failed both times.
If you haven't seen this before, I can run again and capture the full console/log activity -- also, wasn't sure which forum section to post this:
Encountered error in module:
ConverterWorkerColor
Error message:
java.lang.ArrayIndexOutOfBoundsException: 1575
Cause:
1575
kE.a(Unknown Source)
kE.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
I broke out the processing to single session and removed Master Bias (Since I had darkflats this wasn't needed) and it worked for each. So not sure if it was having the Master Bias included or trying to do multi-session that generated the error.
Ok reduced the error surface -
I setup another run with same settings - two sessions (multi-channel, multi-session).
I'm using darkflats, and when I include a Master Bias I get the error above. When I omit the Master Bias, works fine (even in multi-channel, multi-session).
SOOOO, might be nice to have a user UI block or something, if you add dark flats, grey out the Master Bias and vice-versa, or give a popup indication this will cause a conflict - idk.
Thanks
Yes, there are a few ways to look at this as a programmer (as always); most common errors are captured in APP for sure, however some errors you don't want to catch as it would give a false security so to say, the program continues with wrong data. I will definitely agree that it would be very nice for the user if it did show some kind of warning if possible (@mabula-admin knows all about that), But as you found out, there seems to be a problem with the bias data somehow. We can always have a look at the bias to check if you prefer.
@vincent-mod
Thanks Vincent -
What is odd though - I went back and tried another process - without a master dark flat (just a pile of dark flats so it could build the master dark flat).
It wouldn't work! It gave me an error that I needed a master bias!
Very odd. I added the master bias and it worked. So - it seems, if you already have a master dark flat, you can not add a master bias. If you have no master dark flat but just dark flat subs, it requires the master bias.
With my ASI1600MM-C I always use a master bias and a master dark flat and never experience issues. I also always use a master dark and I created a dark library with different exposure times exactly for this. The only subs I add are the lights and the flats. This always works for me.
Hmmm that's odd.
Btw, pretty sure you aren't supposed to use master bias with the 1600 - there is some issue with super-fast frames like a bias with the 1600, that's why folks use darkflats instead.
I'm doing all this with the 183 which doesn't have that issue - but using darkflats anyway, someone recommended it - can't remember...
Thanks, yes I heard about the bias issue with this camera but my pics don’t seem to be affected by it. I’ll keep it in mind though.
Thanks for the tests, I hope Mabula can pop over to have a look here as well soon.
