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.
[Solved] Integrated image doesn't have the right color - solved the canon1200D wasn't yet supported in APP 1.041, it is in 1.042
I started to use the workflow on one of my CR2 RAW image sets, taken with a modded Canon 1200D. When I look at the integrated image, the colors don't look right as if I would have choosen a wrong bayer pattern. In APP in step 0 I have set "supported" since this camera is listed. Could someone point me to the right direction ?
Just to share my first humble result with APP ;-). I have processed my Canon 1200D RAW-s with the latest version, "supported" gives the correct colors now after integration. This is a stack of 47x50s exposures with a Tokina 300mm telelens on a Sky adventurer. No calibration frames applied so far. I have done some noise reduction and removing color aberration halo's from stars in Photoshop CC.
The most effortless processing sofware I've ever seen !
I have some additional questions about the Tools part en finetuning details, but I should post it on the workflow subforum I suppose ?
Just to share my first humble result with APP ;-). I have processed my Canon 1200D RAW-s with the latest version, "supported" gives the correct colors now after integration. This is a stack of 47x50s exposures with a Tokina 300mm telelens on a Sky adventurer. No calibration frames applied so far. I have done some noise reduction and removing color aberration halo's from stars in Photoshop CC.
The most effortless processing sofware I've ever seen !
I have some additional questions about the Tools part en finetuning details, but I should post it on the workflow subforum I suppose ?
Â
cheers,
Janos
Â
Hi Janos,
Great ! Thank you for sharing 😉
Yes, post it on workflow and I'll help you out there.
We can start with a vignetting correction or light pollution removal to remove illumination differences in the field of view.
Indeed the correct CFA pattern for both 1200D & 1300D (or REBEL T5 & T6) is actually GBRG.Â
Pixinsight uses dcraw for CR2 conversion and dcraw internally is cutting corners... APP uses the whole sensor which PI with DCRAW does not. So the reason for PI to report it as RGGB is because DCRAW has removed an uneven amount of lines from the top of the whole sensor.Â
So this is basically an implementation issue induced by DCRAW, not by PI 😉
(I have written the CR2 conversion myself and have read & studied the dcraw code ... dcraw is great but it skips corners...)
