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.
Hi everyone, I just finished a two-night session on the flame and horsehead nebulae with my astro-modded Rebel T6. The top two-thirds of the image look pretty decent, but then I have this hard gradient and what looks like the program choked in a few areas. Does anyone have any idea what causes this? I'm currently re-running the set with a lower degree LNS (only thing I changed from my usual process) but don't have the new result yet.
Â
@ajm16143 We would need to know more about how you process the images to be able to help you solve this. What OS are you on? What version of APP? Are you processing the images on the local hard disk or an external one? Does it help if you disable OpenGL in the APP settings?
@wvreeven I'm using Windows 10, APP 1.082, and processing on a local drive. I just reprocessed the data and it seems that the problem is in my first session as the second looks fine. I'll try disabling OpenGL on them and see what happens.
@wvreeven Disabling OpenGL didn't do anything to help. I ran the first set of lights without any calibration frames and the red bands show up, so it must be something in the lights. I checked all of them in APP and don't see anything strange in any individual frame.  Â
@ajm16143 Can you upload a small sample of your lights and calibration files to
https://upload.astropixelprocessor.com/
using username and password upload2 and create a directory there called ajm16143_artifacts with the files in there? Then we can have a look and see if we can find the cause. Thanks!
@wvreeven Thank you, I uploaded them as instructed. What's interesting is I ran the same files through Deep Sky Stacker and don't see the artifacts so not sure what I did that's introducing them in APP.
I loaded the Lights, Flats, Darks and DarkFlats in tab 1 and then went straight to tab 6 and clicked the Integrate button. Everything else I left at their defaults. The result is this:
Â
A few comments: I see that your Flats and DarkFlats are 0.3 second exposures. With a DSLR camera you should take Flats of at least 1 second to give the shutter enough time to open and close because otherwise you run the risk of getting the shadow of the shutter in your Flats which will introduce other artifacts which will be hard to get rid of.
Also, your Bias and DarkFlats have the same exposure time. When Bias correction is applied, the effect of the DarkFlats will be reduced to zero, which may very well be the cause of the issue.
So, next time make sure to take longer Flats. If necessary dim the light source that you use to take them or, if that's not possible, use a white t-shirt or blanket over the opening of the telescope to dim the light. Also, either take very short Bias exposures or leave them out all together.
@wvreeven Thank you for testing that. Not sure what setting I did that aggravated it, but glad to know the data is good.
I think the bias issue was a mistake on my part uploading, they should have been 1/4000 shutter speed as that's what all the ones in my computer were shot at, but I think I mistakenly uploaded the dark flats to both folders. I will definitely take your advice on longer flats. Â
