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.
Hello
with the beta 25 version I am getting this error during calibration. Can you advise?
Thanks
deep
Edit By Mabula: solved in 2.0.0-beta29
Hi Deep , @app3sashimi
That probably indicates a problem with 1 of your fits files somehow. Does it happen with all your fits files or just with 1? Maybe that file has been corrupted?
Feel free to upload the data on which it occurs and I will have a look :
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
Please make a folder with your name and let me know once uploaded 😉
Thanks.
Mabula
That's what I thought too. But beta24 runs fine. I went back to it and it worked. I am using beta24 now. May be it should not have! I could not figure out which fit file it was complaining about looking at the log. I will try switching back to beta25 and if I see it again I will upload last 2-3 files the log shows.
Hi Deep, @app3sashimi
Beta25 has a small modification in the FITS converter to handle bad Siril data, so if this affects your data somehow, we need to know, so please let us know if you encounter it again 😉
Mabula
@mabula-admin What is the "Siril data" connection ? I am directly pulling the data from Camera. May be my ignorance 🙂 Does APP use some Siril components ?
Also is there a way to get star masks out of APP like Siril does with the Starnet++ ?
Thanks.
Hi Deep @app3sashimi,
No, we have no connection whatsoever with Siril. Some users that use Siril use APP and vice versa.
But I actually made a mistake, in beta25 nothing was changed in the fits converter, we changed something in the beta26 code which has not been released yet, relating to a data issue coming from Siril.
- FIXED interpretation Siril output data
As reported here https://www.astropixelprocessor.com/community/main-forum/problem-loading-oiii-fits-files-processed-with-siril-into-app/#post-29027 , APP could not stretch a 32bits float FITS file produced by Siril. Data analysis of the data inside the FITS file showed that the data did not conform correctly to normalized floats in the data range of 0-1. Once actually clipped to this range, the data shows correcly, something Siril forgot to do perhaps. We have added an exception in our FITS converter for Siril data to check for this data problem and apply the clipping.
Anyway, I wiill see if I can understand your issue in this case, if it happens again, please check the general console, it should point you to the problem file/image.
Mabula
Hi Deep @app3sashimi,
I have checked our code relating to the error message. This code is identical to beta24 and much earlier versions even. So your error is kind of weird, please let me know if it happens again 😉
Mabula
@mabula-admin Will do. I will install 25 back and see if I get it again.
Any thoughts on the star mask question ? I actually often go from APP -> Siril's starnet integration for the star mask thing. Would be nice to do it all inside APP.
Hi Deep @app3sashimi,
Did you encounter the issue again or not?
Yes, star masks will be possible, it is on our list 😉 to work on going forward.
Mabula
@mabula-admin I have not tried it yet. Shooting some photos this week. Will try over next couple of days. Thank you for checking.
regards
deep
@mabula-admin I have been using b25 on some data sets and have not seen that problem again. I will switch to b26 and will let you know if it happens again.
Hi @app3sashimi,
Excellent, please let me know if it does occur again and on which file it occurs then as well.
Mabula
Hi @app3sashimi,
We have found that the issue is caused by corrupt files.
I have now build in a proper detection of this issue and the user will be warned that a certain file seems to be corrupt.
Thank you very much for reporting it.
Mabula
@mabula-admin . Cool. thank you. By the way did you see my other question about saving and restoring working sessions. I asked it a while ago.
