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.
We can load (master)calibration frames separately for each session, but the session information is lost for BPM in the frame list. Therefore, BPM-1 is always selected, even when BPM-2 is loaded for a particular session.
I found on another forum that this is due to the fact that BPM-selection (contrary to all other calibration frames) is done off the "Camera" or "Instrument" tag. Problem is, when combining two sessions, shot with different camera's of the same make&model (for instance my friend's ASI2600MC and mine) this tag contains the same factory information.
Workarounds are to manually update the camera-name in the fits-header, or to calibrate and save each session separately before restarting APP, loading all the calibrated frames, and continuing to step 3) analyse. Both seem extremely cumbersome, and also quite unnecessary. The whole point of multi-session processing is to not needing to do that.
