Jan 31 2026: APP 2.0.0-beta40 will soon be released with many fixes especially for Linux, upgraded development platform and 10-20% performance boost !
Jan 15 2026: FIXED LICENSE SERVER VPN Tunnel issue
 The issue could have prevented APP to start when using a VPN tunnel or another complicated network configuration, like using APP on a remote computer on a different continent. This issue is fixed now and APP should start normally.
Jan 04 2026: Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version. Unfortunately, Mabula was struck by a severe flu virus in the past couple of weeks and thus could not work. He is getting much better now and he has resumed work to release 2.0.0 as soon as possible. Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
Nov 28 2025:Â APP 2.0.0-beta39 has been released !
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?).
