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.
Hi Mabula,
with rev. 2.0.0.39 I can select f.e. Multi-NB extract H-a + Oiii. In the documentation is noted that automatically 4 files are generated in Register 6. But I get only on file and this is the classical Multiband Color.
Also if i choose f.e. Multi-NB extract Oiii I get also a classical Multiband Color with no separated Oiii Mono image.
Whats wrong ?
Thank you
Werner
here an example. Both files are made with a OSC (QHY268C) and the Optolong L-Ultimate (Ha+Oiii)
Selected Multinarrowband extract in Tab 0
Two Multinarrowband files loaded
after ingetration in Tab 6 I get only one file ... here TEST.fits (NOT 4 files). Test.fits is a multicolor file, no Monofiles !
Are you trying to do the operation using already stacked and debayered FITS?
Try on the raw fits files and see if the issue persists.
/Stefan
Hi Sefan,
yes, normaly my workflow is that I extract NB-Channels if I´m starting postprocessing and if I´m ready with all sessions. I have tried with unstacked raw files and this works.
Seems to be a bug that stacked files can not be extracted.
CS
Werner
I dont think it is a bug though. The difference between stacked and raw fits is that the stacked is already debayered.
Split chanels in the stacked files and stack B and G channels to make a master Oiii.
until 2.0.0.38 it has worked so far because this was my workflow for years.
I agree with @digitaliz-se. You seem to be trying to combine already extracted NB files. The multi-band extract feature is for extracting NB portions of OSC files. Your HO1 and HO2 are presumably already NB files and are ready for combining in the RGB combine tool.
The files beginning with HOxxxx are stacked OSC files made with a dual-narrowband filter, so they are RGB. In the past until 2.0.0.38 it was possible to extract different narrowband from stacked files like "extract Oiii" etc. As a result I got a mono file with f.e. Oiii or Ha.
If this is not a bug in 2.0.0.39 than I have to change my workflow in the future. But how I said ... in older versions it has worked.
Hi Werner @wstumpferlgmx-de,
Thank you very much for sharing your issue. And thanks everyone for your suggestions as well.
All the Bayer/X-Trans algorithms in 0) COLOR SETTINGS (or the old RAW/FITS menu) will only affect data that needs to be demosaiced/debayered.
All stacks/integrations will always be already debayered/demosaiced and so the algorihms in 0) Color Settings will do nothing. I can not see how older APP version would do so either.
I also see from the filenames in your screenshot that the files are run through GraXpert? The output is very likely only 3-channel RGB data instead of 1 channel CFA data that needs to be debayered.
Let me know if this makes sense and/or solves this.
Mabula
