View Single Post
  #3  
Old 19-08-2020, 03:54 PM
irwjager's Avatar
irwjager (Ivo)
Registered User

irwjager is offline
 
Join Date: Apr 2010
Location: Melbourne
Posts: 505
You seem to have some excellent signal there - you really hit the ground running with the new ZWO!

A suggestion, if I may; Instead of leaving Ha/red dominant, maybe consider doing, for example, a pure bi-color.

Start off with re-synthesising a new synthetic luminance dataset to go with the new coloring; load all channels as normal, but double the exposure time for green (since you use an OSC with a Bayer matrix, having 2x more green samples than red or blue). Set "Luminance, Color" to "L + Synthetic L from RGB, Mono" to create a new mono luminance dataset from all this.

A popular thing to do, is to synthesise a new channel from green+blue (constituting O-III) and import that as both green AND blue equally (this yields the pure cyan). You can synthesise this new channel using the Compose module or the Layer module.

To put it all together for processing, in the Compose module, import the original dataset as red, import your new "green+blue" as green, and once more import your new "green+blue" as blue. Finally load your new synthetic luminance as the luminance source. Set "Luminance, Color" to "L, RGB".

Now you're all set. Doing so, you will get the best of both worlds; the cleanest possible detail (luminance) and custom bi-color colouring.

From there, process your detail as normal (in mono). Once you hit the Color module it will start you out with the popular red/cyan bi-color rendition.

And as a bonus, as of StarTools 1.6, using the Matrix option, you can remap your color channels on the fly to choose from many other color renditions, all without having to re-composite and re-process. It does so without impacting detail or noise at all. There should also be a helpful Duoband preset in the Color module to quickly dial in some useful preset values.

Hope this makes sense and helps!
Reply With Quote