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.
Edit by Mabula :Â this issue is fixed in the 2.0.0-beta29 release.
first time I've seen this but it happens when everything is finished and it tries to save the final image. Any help would be greatly appreciated.
@shanebdye2gmail-com I've seen this happening when bad calibration files are used. More specifically, when only a master bias was used with a DSLR camera.
Which calibration files do you use? Do you get a popup indicating that there was a calibration error earlier in the processing pipeline?
Actually I was just processing lights. It seems to not like the fits files as it only does it with them and it does it with files that i previously processed successfully.Â
I converted a set of fits to tiff with pipp and then processed in app fine.Â
Can you tell about the lights? What camera did you use? What ISO or gain? Temperature? Exposure time? Did you use a filter? Which telescope?
120 3" lights w/asi294mc @ 120gain. non cooled with ambience temps below 30*.Â
evo72ed w/.8 reducer on cgem. No filter.
For the sake of clarity, I've been using beta version 13 and only recently updated to beta version 20 less than a week ago all on Windows 11 Home. Experimenting a little i uninstalled 20 and reinstalled 13 and no problems. I'm thinking about reinstalling 20 again just to verify because I'm willing to bet in my ignorance i screwed something up along the way. This software is amazing but my skill level is limited! 😀
Maybe try beta26, which is the latest version, instead of 20?
Hi @shanebdye2gmail-com & @wvreeven
In the latest APP versions, our dependency to read/write FITS files was upgraded, maybe this is related to this issue, since beta13 worked. It will be best if I can see a FITS files on which this occurs, to see if we can implement a workaround. If the error occurs due to FITS headers from the original FITS files, it should be noted, that they probably are not created correctly. But once I can analyse such a file, we can properly get to the bottom of this 😉 Can you share such a FITS file with me Shane?
Thanks
trying to upload a fits file but not having any luck :/ says file type not allowed
Â
Hi Shane @shanebdye2gmail-com,
Please accept my apologies, indeed, FITS is not allowed to upload to the forum directly.
But, please upload it to our data server here:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
Please make a folder with your name and issue like: ShaneDye-FITS-issue
and upload the the fits file there and let me know once done 😉
Thanks!
Â
Hi Shane @shanebdye2gmail-com,
Can you please upload such a FITS file that gives this issue with the instructions given in my previous post? It will help to solve this quickly, but the problem is clear as well. The FITS saver errors with a clear message, so I will address that and it should be fixed in the next release 😉
Mabula
Hi all @shanebdye2gmail-com @wvreeven
I have fixed this issue properly now for the 2.0.0-beta29 release. All Fits headertag values will be checked for NaN and Infinite values and will be set to 0 when encountered with a single warning to the user that there is a data problem somehow.
Mabula
