Black Friday & Cyber Monday Sales on Renter's & Owner's licenses - sale will end on the 1st of December 2020 at 12:00 UTC
16 November 2020 - Wouter van Reeven has officially joined the Astro Pixel Processor Team as a moderator on our forum, welcome Wouter 🙂 !
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!
[Sticky] Very strange integration result - check if you're using a FAT32 filesystem
But why is the image having this amount of vignetting? Your flats are working quite well from what I saw, so that shouldn't be the case.
ps. You use either DF or bias for correction of the flats.
OK I will re-run later this weekend. I did notice that the vignetting was bad and the flats didn't appear to take out any of the dust. I will figure that out.
Interesting thing is that i did some post processing and then cropped and the banding did not appear. This is only a couple hours of data, so I need to get more but it is getting there.
I have been away for awhile. Purchased a rental license today for APP. This will give me a year to figure things out.
I processed the M101 again today and left the Bias frames out of the mix. Still had the horizontal banding. I was looking things over and noticed that I had 40 each of flats, and dark flats. I then remembered that I had mistakenly taken my first set of F and DF at 0 gain. I usually take my F and DF at the same gain as my lights, so I retook them. I had been selecting all forty of each, so I am running it again just using the ones that match the gain of the Lights, to see what comes of it.
Trying to fully understand what Mabula is suggesting for L, D, B, F, and DF.
Do I need both Bias and DF frames or just one of those? Should everything be at the same gain?
Ran the processing a second time still had the horizontal banding. I checked my MD, MDF, and MF, didn't see anything out of the ordinary with the image. Oh and this time the banding was present before cropping. At some point I am going to have to decide it is the light frames that are the culprit and try processing a different data set.
For now I am going to run with a reduced number of lights (takes less time) to see if the banding is there.
You had mentioned me sending the entire data set, I might take you up on that
Ok, an update. I ran multiple processes. Six in total. Hit a string of data sets and finally landed on success with L, D, DF, and F, no bias.
Dropped to 30 L frames, with no banding.
Did 84 frames, no banding
Then I ran with all the L frames checked frames after calibration and Normalization to see if there were any issues, but none were present. I removed any frame with a score less than 20, just in case they were causing the problems but in the end the banding came back.
Suggestions? Running tests with all the data takes up to 3 hours to perform, slow process.
More information, I went ahead and did some Tools work on the image and noticed that as I choose different stretch values that the horizontal lines would eventually turn to vertical lines. Quite bizarre.
Yes this is getting a bit bizarre indeed. We would need to have a look at the dataset to be able to really understand what is going on. If you want you can upload the data to our server;
https://ariesprodstor.astropixelprocessor.com:7001/ with username and password: appuser
Please create a directory called “tmeyers-bizarredbanding” and upload in there. 😉
I uploaded the files
what's the matter with this plz help I have those artefacts on all pics.
Stc dual narrowband filter
What's the process you went through, like what APP version, what settings did you use and what type of data (including calibration data)?
Difficult to see what might be wrong here. Just FYI, you don't need the cosmetic correction when you have proper bias, darks and flats usually. Only when there is clear residual noise present (like bad columns and still quite a few hot pixels).
This does look like a data issue somehow, I think I need to look at the data to get a better understanding.
Please upload some of the relevant subs to our server;
Go to https://upload.astropixelprocessor.com and use upload2 as username and upload2 as password.
Create a directory named “fotografiepeterkuehnlgmail-com” and upload in there. Thank you!
I sent you the pics via upload link thx for the help
Thanks Peter, I will download those shortly.
Looking at the data now. First thing I notice is that they went through Adobe Lightroom and are already stretched and not linear. It's always better to take the raw files from your camera and feed them straight into APP. Other software may change properties about the data that may cause issues and I think this might be the case, looking at just one light and zooming in to 100%, the stars look like this;
Which seems odd, they are somehow not round or fully visible. Could you try again with the raw files? Also do this with any calibration data you have, use the original files.