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.
Hello,
(I actually solved this problem. So it's just an FYI)
Last night I shot Abell 33 from my Bortle 8 yard.
ASI2600MC and RC6 at 950mm f6. Antlia ALP-T filter.
It's a low target in my location (50dgrs max).
The lights were noisy.
Integrated with APP with my usual (standard) settings.
APP didn't report any errors but failed to detect/register stars.
The final integration was a mess.
Tried different Registration settings - didn't help.
I was puzzled since it never happened to me before.
PI integrated the same set of lights without a problem.
To tell the long story short:
-- switching from Adaptive Airy Disk to Adaptive Edge helped
but then I still couldn't extract Ha/OIII
-- then I discovered the Cosmetic Correction options which I never used before.
Enabled all three of them with defaults and it worked with the Adaptive Airy!
I am glad I was able to resolve this.
Hi @maxthebuilder,
Thank you very much for sharing this.
In the 2.0.0 beta's several things were improved in star analysis to make it more robust for more datasets. In your case, you do not need to enable cosmetic correction to make it work, allthough if it does that is fine. But in 3) Analyse Stars, you would need to increase the new cosmic ray/noise reducer a bit. The registration would fail if APP sees noise or cosmic rays as stars. By increasing the cosmic ray /noise reducer lower-limit area size to 6-10, probably all will work fine ;-). This is more efficient than increasing the cosmetic correction I think in terms of speed. In cosmetic correction, hot pixels would be removed (thus noise) so it makes it very likely that your registration issue was caused by noise in combination with small stars in your data as well.
Mabula
I continue in this thread so as not to do the same thing in duplicate.
I had indeed enabled the "cosmic ray / noise reducer" option but the result had been the same.
What had not occurred to me was to increase its value.
I have repeated the process again with "lower-limit area size" equal to 8 and the result, now yes, has been as expected.
Thanks, Mabula and Vincent.
