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.
Good morning! Looking for recommendations and the best tutorials for how to reduce light pollution in an image with extensive faint nebulosity? Hard to tell where the nebulosity and lp overlap
Thanks,
Wayne
Well, that means the data by itself is already very tricky to begin with. So to correct that with software is indeed trickier then as well. What I normally do is to take my integration, stretch it to the max preview setting (30%) and oversaturate the image as well. When that blows out the entire image, I just set 5 boxes around the edges and see what happens after that, if that reveals an image that is a bit more clear to correct, you can clear the boxes and place them on the right places around the image in the preview and then try again. It will become an iterative workflow.
Vincent's suggestion is a good one. I do something similar, kind of, but use a tickling approach especially if I cannot find areas of obvious nebulosity, or when the background and nebulosity are so close that large stretching doesn't work. You can choose a good region, run lpc tool and then keep adding boxes. That sometimes works for me because unlike DBE in puxinsight or gradient terminator in PS (and siril and others of course,) you don't need to undo completely the process and search for a new background.
Alternatively, you can add all boxes you thi k are correct, run lpc tool, then if some regions look wrong you can remove boxes and run again, reverse iterations I call them. With a low tolerance slider, it is likely you will always have some red boxes to remove when signal is detected.
I always check online to see where background sky vs signal is located and try to find those regions in my images as a good starting point, then refine
Checking online for where to expect nebulosity is a very good one as well indeed.
