2026-10-09 APP 2.0.0-beta48 has been released !
This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.
2026-10-03 APP 2.0.0-beta47 has been released !
This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂
And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.
Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.
RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.
I've getting the following dialog come up (Encountered error in module Integrator)
Encountered error in module:
Integrator
Error message:
java.lang.NullPointerException
Cause:
null
pj.a(Unknown Source)
pj.a(Unknown Source)
pj.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
And then it just bombs out on me. All steps pretty much with defaults except on one frame Star Analysis failed and I deselected and removed that frame. I chose Mosaic Registration and accepted the dialog suggestions that go along with that.
The console just shows the following:
2:26:39 - 6) INTEGRATE: integration: total exposure time: 7020 seconds = 117.00 minutes = 1.950 hours
12:28:39 - FRAME DETAILS UPDATER: starting...
12:28:39 - FRAME DETAILS UPDATER: no new frames to add
12:28:39 - FRAME DETAILS UPDATER: rebuilding all frame details...
12:28:39 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
12:28:39 - FRAME DETAILS UPDATER: updated succesfully
12:28:39 - CONSTRUCT FRAME DETAILS LIST: starting...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
12:28:40 - CONSTRUCT FRAME DETAILS LIST: finished
Any idea of the cause? Let me know if there is anything to try, I can post a video of the whole process to youtube if it is going to help at all.
Oh, ok, so Mabula says this will be fixed in the next version:
Â
https://www.astropixelprocessor.com/community/main-forum/error-in-new-1-078-version/
Hopefully it's the same thing yes, but there indeed is a bug unfortunately that is fixed for the next release.
Hopefully it's the same thing yes, but there indeed is a bug unfortunately that is fixed for the next release.
I can confirm that it happens only on 1.0.78 (Linux in my case), I did the exact same mosaic task on my laptop (Windows 1.0.77, not Linux) and it went through and completed integration fine.
I do with there was a save state/save project, so that I didn't have to re-run Calibration, Registration etc... on the laptop, but in any case, I have a workaround until we see 1.0.79 surface.
Very interesting. I reproduced one of these crashes on MacOS as well (somewhat similar to Linux) so it might be correlated. I'll keep this in mind, thanks!