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.
Hi Benjamin @bbhar940301,
Looking at the screenshots, something is very off here... most likely there is an issue with the calibration data. Did you check the lights in the calibrated view? Simply load a light from the frame list with the calibrated view using the right mouse click menu. Probably the issue will become obvious.
Also, I see from the screenshots that you have lights of 60 seconds and 900 seconds and you are applying the same masterdark to both? That might be related to your problem as well.
Mabula
Â
@bbhar940301Â try to use COSMIC RAY option in star analysis with a value of 25.Â
APP could try to analyse hot pixels as stars.Â
APP is able to process short R, G, B and long exposure SII, Ha OIII without any problem. I use this option for my images from my remote telescope CDK600 in Chile.Â
@philippe-bernhard, thanks for helping out, indeed that could solve it as well. But I suspect a data calibration issue as well somehow.
@bbhar940301, were you able to solve the issue?




