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 HaLRGB data at 1475mm FL 2.3nm pixel size and OSC RGB data at 250mm 4.6nm pixel size. Most of Blue channel is missing because the object was too low by the time it was shot. I want to integrate R,G,B channels separately by substituting B channel with Blue data from OSC camera and complement R & G data from OSC data shot at wider field. Luminance and Ha data are shot at higher resolution and focal length and I want them to be the reference; I'm fine with scaling up Blue data from OSC because the detail is in the Luminance layer. R & G data may or may not benefit from integrating with lower resolution wide field data, but worth a try.
What's the process to do that type of integration? Is checking "Integrate per channel" enough? Will it know to extract RGB data from RGB channel to combine with R/G/B channels from the other camera, or it will create 4 integrations, R/G/B/RGB because OSC subs were loaded as "RGB" channel? I want to have 5 channels as output: Ha, L, R, G, B, registered to a reference frame in Luminance.
I have an idea: check "split channels" and "save calibrated frames", then add them as light frames back into session as R,G,B channels and remove RGB channel, then integrate "per channel". Right?
Yes, You can split the channels from the OSC RGB into mono frames. Then load them back into APP together with the other mono frames from the other setup. This will register and scale everything to each other after which you can add this integrated data into the RGBCombine tool.
Registering it was tough: had to use "triangles" with start=1 and stop=15, uncheck "same camera and optics". Then it said integration is beyond currently supported size and would required 2.5TB disc space.
I'm trying to do some math. Just to match the resolution of camera1 the OSC subs need to be 2x in size. Then to match focal length they need to be scaled up additional (1075/250=4.3 times) to 35570x24200!!!
So the solution would be probably to do the reverse and chose a reference frame from camera2 (wide field) and downscale. Or maybe something in the middle - use normalization process to downscale camera1 0.5x at the price of the detail in Luminosity layer...
Yes, that's likely then required. You can manually set the reference frame in the register tab.
