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 have a five session project where four of the sessions were shot with the L-eXtreme filter and 1 with just UV/IR. My goal was to end up with three master lights: one for the UV/IR session done with Adaptive Airy Disk and two from the L-eXtreme sessions done with both extract Ha and extract OIII. I have everything neatly loaded into APP with channel/sessions assignments and "integrate per channel" selected, so I was expecting that APP would ask me which sessions I want the chosen algorithm to apply to. Instead it normalizes and integrates all of the channels with the chosen algorithm. So I end up with unwanted integrations of either my L-eXtreme sessions done with AAD or my UV/IR session done with extract Ha or OIII. I realize that changing the algorithm requires re-normalizing, but then I would have expected to have the option for the normalization to be done by channel also. It seems that I'm going to have to deselect lights appropriately for each pass rather than using multi-channel magic. Am I missing something?
No that works like intended, however is indeed not what you want. In your case you need different APP sessions to use the algorithm of your choice and then later register and normalize those results in 1 new session. Good one for me to ask Mabula about though, might be nice to make that easier if possible. The sessions are needed when you have different flats per session for instance, but for the same type of data.
