UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
This is probably a simple fix but this is my first session with processing narrowband.
Veil Nebula. L-Enhance. Processed extract Ha and extract OIII. I’ve combined in the combine RGB tab and assigned Ha to Red, O3 to green and blue. After calculating I get a decent image but large cyan/turquoise cast on the image I can’t seem to normalize. Where do I go from here? Thank you!
Also, is there really that big of a difference between splitting and combining channels vs just processing all the data taken w/ L enhance as you would with no filter?
@nsblifer For what it's worth, I actually processed my L-eXtreme data using the Ha-OIII Color algorithm on tab 0 and it turned out fairly well.
Splitting the channels I'm sure gives you a lot more flexibility but you could try the "easy way" and decide if you really want to go down the channel splitting path.
-- Rich
