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.
I am imaging M57 with different filters, both narrowband and wideband.
When I integrate my Ha 3nm channel only, I get a good result, with good dynamic range showing gradients and details (see attached image).
But when I add to the project the other two channels, which has a significantly stronger signal (Green and Oiii-7nm) - I get a very bad integration of the original Ha data (integrated separately of course) - it is "flat" with almost no gradients and details
(see attached image).
My understanding was that I should get an identical outcome of this channel, but it seems to me that the Ha processing is somehow influenced by the other channels (normalization perhaps?) that were added. I cannot figure out what I am doing wrong that is causing that and what I should do in order to change that. Your assistance is appreciated.
Thanks,Â
Assaf
(P.S. I am working with version 1.083 beta)
@assafh Please try at least the latest stable release (1.083.4 for Windows or 1.083.2 for Linux/macOS) or the 2.0.0-beta1 and see if the issue remains. Many bugs were solved since then, including bugs that may explain the behaviour you see.
