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.
"Set new reference frame" takes forever (never completes). I'm registering a 2x2 mosaic with a narrow (~10%) overlap, shot with a William Optics FLT 132 scope and an ASI6200MM camera through LHOS filters. 203 light frames.
This worked okay on a previous integration of 3 panels, "set new reference frame" took a couple of minutes. Due to narrow overlap, I shot four luminance frames which span the middle of the mosaic, and re-assigned one of those as the reference frame. I used normal registration, not the "mosaic" registration function, but it shouldn't matter. This problem occurs before that.
Today when trying to register my 2x2 mosaic with 203 light frames APP seemed to go off on an endless loop after analyzing stars, then choosing "set new reference frame". It never completed and showed very low (< 1%) CPU activity. I finally killed the process. (APP version 1.083.4, Windows 10, Intel i9 CPU, 64 GB RAM)
I then upgraded to APP 2.0.0-beta38. I told it to analyze 3,000 stars, same problem. "Set new reference frame" never ends. There is no way to cancel. So I killed the program and tried again by analyzing only 500 stars, then setting the reference frame manually. Still waiting for APP to respond after >1 hour, during which CPU usage is again minimal, <1%. the command never completes. (APP version 2.0.0-beta38, Windows 10, Intel i9 CPU, 64 GB RAM)
So I'm stuck. Unable to set a reference frame manually. Any idea what the problem is?Â
Edit: "Set new reference frame" worked quickly, and as expected when I invoked it using the popup menu on the light frame (versus the button in the "Register" panel).Â
