30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.
9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp
2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!
I have created a couple of mosaic with last version 1.081, with neutralize-bg option selected in 5) normalize
The final result is good, but when i select again neutralize-BG in the view option panel on the right, the imaged becomes all white: by the istrogram seems that all pixel was pushed down to black, and the applied stretch turn all to white.
The problemis is when using "remove light pollution" operation, APP perform an automatic neutralizeBG, so is not possible to go ahead with image processing.
I check disabling neutralizeBG in 5)normalize, and the result is ok
NeutralizeBg in view after mosaic composition is ok and i can go ahead with light pollution correction
There is also a tooltip, when you hover over that option in tab 5, mentioning that you’d need to calibrate the background later on. What happens when you turn off a similar option on the right for the preview window? I think it might be a data issue in this case, preventing it from working normally.
I have a similar issue in 1.082. Integration proceeded normally and the view of the image was very good. When I selected the tool, normalise background, the whole image went white in a very similar way and I could not correct the picture. Image pixels were all scaled to 0.9999xxx or similar.
Screenshot with example of "white out". Getting this issue regularly.
I will ask Mabula why this exactly happens, I think it must be data related otherwise many more would have it. I'll come back to it asap.
I've been having this white-out too, every now and then. When viewing in registered mode, stepping through the individual exposures after alignement, this happens for a few of the exposures, not for all.
Mabula also thinks this usually happens when there is a calibration data issue. If you have the specific data, I can give it a look.