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 seem to have a red block on some light frames and when stacked - creates a red wiggle / line.
I'm not guiding so I am expecting some shift between frames, however the red block is not picked up by the 'bad pixel map'.
Any suggestions on how to remove this red block during APP / stacking? as it really is making the images unusable.
(attached - light / bad pixel map / integrated image)
See attached files.
Woops missed your post, sorry.
So are you using darks as well? This seems a hot pixel, did you leave integration in automatic setting?
Yes - full set, darks / bias / flats / dark flats ... I asked in another thread and I think you said that if I did use a full set - then APP would apply the right combinations etc.
Integration - I chose the option for > 20 frames ... as I had 80+ lights.
Thanks
Interesting, maybe in this case you then would need cosmetic correction as well. This can be found in tab 2, calibration a way down. You switch on the hot pixel kappa checkmark. You then load 1 sub (and your BPM and MD) with that red pixel, zoom in on it and select "l-calibrated" from the dropdown menu on top of the APP window. Do you see it go away? If not you can reduce that kappa to 2.5 and check again (select l-calibrated again). This is a fast way to see if you can resolve issues like this before doing an entire integration.
If it correctly removes that pixel and the rest looks ok, you can try another integration.
ps. you mention not guiding, so you can't dither then either, that is where issues like this will also get solved (although I think walking noise looks different, maybe this is related?).
