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.
Just to clarify since the creation of the BPM in APP is full of confusion, if I want to create a BPM only, all I need are long darks and flats correct? The flats can be any length/gain/iso/offset right? It doesn’t matter what filter those flats match? BPM just needs any flat?
Bias and flat darks should not be needed since I’m not creating a master flat, correct? I would uncheck “create masters” in this case.
And finally when the BPM is created it can be used for all data (e.g. different length subs, filters, gains, offsets, etc...)? It can be used universally for any sub coming out of that specific camera it was built for?
It's not that confusing, you can simply select to create the BPM along with the calibration data you would normally already load in. So you add a good dark, a long one is preferred indeed and if your camera has any cold pixels, a nice flat. You can already make a BPM with just a long dark if you're sure your sensor doesn't show cold pixels.
The BPM can then be used for all situations in which that sensor is used yes.
@vincent-mod
Ok, so the flat isn’t needed at all then if I’m not interested in cold pixels? Just a long dark?
The confusion arises since there are many tutorials all using different methods. Some use bias, some use flats, some use flat darks. The bottom line is that one ONLY needs long darks to create a BPM if you’re only interested in correcting for hot pixels. If you want to correct for cold, then flats are also needed.
I wouldn’t think cold pixel would be very common in newer CMOS cameras. I’ll probably just skip that and focus on hot pixels then.
@vincent-mod
I wonder if BPM can replace completely darks...so to avoid to use darks...what do you think?
I did a quick test (using some low quality frames from my asi533) and for me darks continue to be a better choice in the all process...but asi533 has no amp glow and so low read noise and almost no cold pixel...
I wouldn’t think cold pixel would be very common in newer CMOS cameras. I’ll probably just skip that and focus on hot pixels then.
That's correct, cold pixels seem to be less of an issue, if at all, in the newer sensors. It never hurts to use a flat anyway though, just in case you miss one. But it won't have a huge impact.
I wonder if BPM can replace completely darks...so to avoid to use darks...what do you think?
You can yes, however a Dark is also useful in the case where you have some amp-glow. If you have that, a darks is still necessary. Otherwise you can do without, though I always test that first by eye. If you find that adding darks gives a better result still, I would use both BPM and darks.
