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’m using a ASI183MC pro camera for capturing images. Capture software used is astroberry and the Images are saved as FITS. The FITS header state RGGB as Bayer pattern and APP is set to use the pattern in the header.
I would expect the images to be more green, because of the two green pixels compared to only one pixel for blue and red. But the image is more blue (single image, auto stretched). So I’m not sure if the color channels are swapped in a way and if I force any other Bayer pattern it comes out even stranger. If I set BGGR then the image is more red what is expected, because just red and blue are swapped out.
Any ideas on that? I can provide a sample image if needed.
Mario.
@mkeller0815 Hi Mario, yes please provide a few example files. You can login to
https://upload.astropixelprocessor.com/
using upload4 as both username and password and create a directory called mkeller0815_bayer and put the files in there. Then I will have a look as soon as you have uploaded them.
@wvreeven thanks for the quick reply. I uploaded two light frames from two different sessions and targets. Let's see what you can find. FITS header looks okay to me but I'm not sure if there should be some color correction values like we have in other RAW formats.
@mkeller0815 Thanks very much. Can you upload a few examples of normal frames as well for comparison?
@wvreeven what do you mean by "normal" frames?
I just checked the other thread but it is about the native or / and ASCOM drivers together with APT changing the Bayer pattern during a session. But it seems that in both of my session the pattern is consistent. I'm also using the INDI lib and KSTAR for imaging what is a completely different software stack. I reached out to @daniel_n because I know he also uses the ASI183MC pro and APP but with different imaging software and he confirmed that his images also appear blueish.
I also tested my session in Siril and had the same output there. So probably it is the way this camera records data even though I don't understand why this happens.
It looks like the the blue part of the pixels get a higher offset because just the dark parts are more blue. looking at the stars in high magnification there are gray tones not blue tones. so the more signal we have for a pixel the less the effect of the "blue shift" is.
What I can try is to add a normal lens to the camera (if I have the right adapter set) and take a daytime picture of objects with well know colors and maybe even a grayscale test page to see if this also adds this blue tone to everything.
@mkeller0815 With normal I mean the ones that look green. But now that I read your original post again, it looks like ALL your images are blue! Sorry, I misunderstood that.
This is strange. Did you ask in the astroberry sub-forum of the INDI forum if anyone else experiences the same? This seems to be either camera or imaging software related. Perhaps we can help you configure APP such that it can produce natural colors from the images you took but I'd want to know the cause of the issue as well.
Yes, all images are blue. After testing with Siril I also think it is not APP related and running the "neutralize background" the image looks natural. So I can overcome this issue, but still it is strange. There is a thread in the indi.org forum
https://indilib.org/forum/ccds-dslrs/3922-right-settings-for-asi-183-mc-pro-in-indi.html#gallery-1
and the last post also states that the images have a blue tint. If we would have the data of all 4 subpixels (before debayer) of one image pixel with a color that has different values for R G and B we should see that two subpixels should have more or less the same value and this should be the green subpixels, right? Maybe I find the time next week to play a little with the astro.py library in python to get something we can look at.
