2022-05-11: APP 2.0.0-beta 1 has been released !!!
Providing many improvements ! and a macOS M1 native version ! Please read the announcement here.
Download links per platform:
windows 2.0.0-beta1
macOS x86_64 2.0.0-beta1
macOS arm64 M1 2.0.0-beta1
Linux DEB 2.0.0-beta1
Linux RPM 2.0.0-beta1
Linux DEB HiDPI 2.0.0-beta1
Linux RPM HiDPI 2.0.0-beta1
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?).