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.
Hi! New to APP - have successfully used to mosaic stacks processed and flattened in DSS/FITSWORK. However now trying to start from raw images, darks,flats.
See the attached - the flat is a fully calibrated flat (ie already stacked with flat darks) Master from DSS that I have dropped in. I dont use biases - recommended against with CMOS.
Im concerned that the flat has a 'D' against it, which suggests that the dark frame (also a Master stack from DSS) will be used with it, which would be disastrous. Can someone explain if this is the case, and if so how to prevent it?
I also find it odd and troubling that I cant upload flat darks into APP; does APP expect me to use biases or the same darks with flats?
Hi! New to APP - have successfully used to mosaic stacks processed and flattened in DSS/FITSWORK. However now trying to start from raw images, darks,flats.
See the attached - the flat is a fully calibrated flat (ie already stacked with flat darks) Master from DSS that I have dropped in. I dont use biases - recommended against with CMOS.
Im concerned that the flat has a 'D' against it, which suggests that the dark frame (also a Master stack from DSS) will be used with it, which would be disastrous. Can someone explain if this is the case, and if so how to prevent it?
I also find it odd and troubling that I cant upload flat darks into APP; does APP expect me to use biases or the same darks with flats?
Thank you for your question and welcome to the APP forum 😉
See the attached - the flat is a fully calibrated flat (ie already stacked with flat darks) Master from DSS that I have dropped in. I dont use biases - recommended against with CMOS.
That's fine 😉
First of all, let me point out that using masterframes from other applications can be a recipe for problems (especially for DSLR data). If you have the original calibration frames, I would recommend to use those as a starting point in APP for data calibration. If you only have the masters then we need to work with that.
Yes, the D next to the flat, means it will subtract a matching masterdark from the flat. I can't see everything of the frame list, so I don't know what else is there.. but I think the dark was converted to a masterdark and then that would be matched to the flat because it has the same iso/gain and exposure as reported by metadata. And that's because the metadata of the DSS masters is insufficient.
What you will need to do to fix this:
1) clear the frame list.
2) only load your DSS masterdark as dark. Let APP create a MasterDark for APP from it by clicking calibrate.
3) clear the list again.
4) only load your DSS masterflat as flat. let APP create a MasterFlat for APP from it by clicking calibrate. Since this master was created properly by having subtracted dark flats like you indicate, this should be fine.
5) Then clear the list
6) load your lights, and the APP Masterdark and Masterflat. That should be it 😉
I also find it odd and troubling that I cant upload flat darks into APP; does APP expect me to use biases or the same darks with flats?
APP 1.059 and lower can perfectly address flat darks. Just realize that a flat dark is just a dark for a flat, you should load them as darks. The masterdarkflat created will be matched with the flats if they have the same exposure and ISO/gain as the flats.
(I do this all the time with my ASI1600mm-cool, for the reason that you give)
But, APP 1.060 (which I am working on right now), will have a separate dark flat load button and will also create a MasterDarkFlat, so that will be easier. And the matching of masters to lights and flats will be much easier and transparant.
Currently, the calibration rules demand that a masterdark is only applied if it has the same exposure and ISO/gain value. That will no longer be the case in APP 1.060 and it will also include dark scaling 😉
Let me know if this answers your concerns and questions.
