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 would like to see a way to integrate OSC masters with mono on the combine RGB tool, with the ability to use sliders for the weights and the ability to put both mono and OSC lights and calibration frames in the tab 1 load at the same time, and the ability to do that without splitting channels.
@imnewhere Just a small question about your first sentence. If you are using the "combine RGB" tool then technically speaking you're not integrating but you're combining color channels. Is that what you meant? If yes, then this already is possible. You can load an RGB image into the "combine RGB" tool. APP will then detect that it is an RGB image and will ask you to specify the channel name for each color channel in the order of R, G and B. Then you can add mono data as well.
Is that what you meant? If yes, can you try for yourself and verify that this works? If no, can you rephrase your question please?
@wvreeven I meant the ability to combine an RGB image from an OSC camera without splitting the channels. I would like to be able to register, normalize, and stack all of my OSC subs at the same time I do my L, R, G, B, Ha, Sii, and Oiii files. It will fail on normalization. It somehow also generally messes up on integration, giving a really interesting, but not really usable result. I've attached the result combining data from a Pentax K3 DSLR and an FLI PL9000 through LRGB filters.
It looks like that should even be possible due to how we are prompted to select a channel and a session. Having them all stacked and registered at the same time would be awesome. Let's say I am running both of my 10RC scopes at the same time on the same mount after dragging one of the big mounts out. Then let's say I am running a 294 OSC on one doing 6 hours on one target, and on the other a 294 mono in bin 1 mode and doing 2 hours of luminance and 4 hours of Ha. It would be amazing to be able to combine that all without splitting the channels on the 294 OSC, basically layering it over an OSC set that defaults to all channels contained in it locked to each other.
A good for instance would be combining an OSC master with maybe a luminance master or various NB masters, or even with mono R, G, and B channels. It will work as it is set up right now if you don't normalize and you are using pretty much the same resolution and optics by splitting channels on the RGB and skip normalization.
So, in the Combine RGB tool add in these, with OSC not split and all 3 channels locked together:
OSC + LRGB
OSC + L
OSC + RGB
OSC + Ha
OSC + Oiii
OSC + Sii (I don't see this being used often TBH)
OSC + HOO
OSC + SHO
OSC + HSO
OSC + HaL
OSC + OiiiL
Â
I meant the ability to combine an RGB image from an OSC camera without splitting the channels. I would like to be able to register, normalize, and stack all of my OSC subs at the same time I do my L, R, G, B, Ha, Sii, and Oiii files. It will fail on normalization. It somehow also generally messes up on integration, giving a really interesting, but not really usable result. I've attached the result combining data from a Pentax K3 DSLR and an FLI PL9000 through LRGB filters.
Integrating OSC and mono data doesn't work at the moment, despite of the fact that the APP user interface does allow you to load those data at the same time. This is something on Mabula's TODO list for a future release. Not sure if that will be the next release though.
You can integrate the OSC data. Then integrate the L, R, G, B, Ha, SII and OIII data. Then take the integration results and load them as lights. Next go to tab 4 and click register and then click save registered frames. The registered frames you can load into the Combine RGB tool without the need to split the channels.
@wvreeven I hope you are stillavailable
When you say integrate both{rbc osc and mono]Â is the integration in fits or tiff?
Dr Stuart Meyer
@sm3612aol-com I don't think he has been around due to health issues, but it still hasn't been implemented so the workaround for now is the method I posted in this topic as a reply: https://www.astropixelprocessor.com/community/main-forum/adding-mono-rgb-to-osc-data/#post-31576
You can save your final result as both fits or tiff with no problem. I save mine is a fits and then take it into PI to run deconvolution, then bring it back to APP to do any light pollution//gradient removal, and then star color calibration if needed, then I save it as a 16 bit tif to finish things up in Photoshop.
