OSC processing orde...
 
Share:
Notifications
Clear all

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.

OSC processing order: RGBHOO

2 Posts
2 Users
2 Reactions
2,031 Views
 HE04
(@heylers)
Red Giant
Joined: 4 years ago
Posts: 34
Topic starter  

Hi.  Wondering: if I have RBG and HaOIII data from my OSC camers (ASI294MC), is there a difference in the end product between these two processing orders (effectively, separating channels early or late):

 

1) easier processing, late separation:

- Process RGB all the way through integration

- Process HaOIII with "HaOIII color" algorithm, all the way through integration

- Do some minor cleanup, like early cropping, remove light pollution, and maybe calibrate star colors (for RGB only)

- Normalize the two stacked images

- In "Combine RGB tool" with RGBHOO formula, load RGB stack into R, G, B channels and load HaOIII stack into Ha, OIII, OIII channels

 

OR

 

2) early separation:

- Process RGB through Calibration, split R, G, and B and process those separately through Integration

- Process "HaOIII, extract Ha" through integration, then "HaOIII, extract OIII" through integration

- Do some minor cleanup, like early cropping and remove light pollution for each stack

- Nornmalize all five stacks 

- In "Combine RGB tool" with RGBHOO formula, load R, G, B into their channels separately and then Ha, OIII separately

 

(Same question for HSO or similar processing)

 

In effect, does it make a difference at what point in the process I separate the individual channels out of the color image (and if so, why?)

 

TIA!

 

H

 


This topic was modified 3 years ago 2 times by HE04

   
Mabula-Admin reacted
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

It can make a difference in the sense that having all channels separate (your option 2), gives you the ability to process them differently if preferred. I'm not sure it would otherwise be a big difference as I think APP is still separating the RGB image into R, G and B channels in RGBCombine. I would maybe separate Ha and OIII though and load those into the tool as actual Ha and OIII, because a HaOIII stack will be combined already and then separated, I think having them processed as separate channels first reduces the noise level of both a bit better. So option 1 is the easiest and doesn't make a difference, other than I would process the Ha and OIII separate.



   
Mabula-Admin reacted
ReplyQuote
Share: