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.
My recent set of images, taken with ASI294MC-Pro camera using NINA, show significant banding when processed via APP. I have over stretched these to highlight these artifacts.
Any advice as to what may be causing this is appreciated.
Well I guess that's bias noise. You can calibrate out with bias frames. I have a 294 and I don't think I have much bias noise - lots of amp glow though. When I capture I have the offset set to 8, this setting was automatically selected by my capture software AstroImager (Mac product)
Thanks for that comment I'll check it out. I have also been advised that the culprit could be USB-3 bandwidth, where too many devices are calling for access at same time.
Cannot check properly until some clear skies return - and who knows when that will be ;-((
I don’t know who told you that but that’s not how digital communications works. All transferred data is verified to be valid and complete. What you see is in the image you took. Bad communications would cause lost data. Not noisy data.
Hi Frank,
I take it that we are looking at a stacked image in your screen-shot and not a single frame? The nebula signal looks pretty weak to me so I assume you are not integrating that many frames and/or they are of short duration?
Have you tried examining your individual subs using a hard stretch with viewer in a) linear, and b) l-calibrated mode? When switching to the l-calibrated mode, much of the noise and other unwanted artifacts in your linear subs should be removed. If this is not the case then I would carefully review your process for capturing and stacking your calibration frames. Also try experimenting with the Cosmetic Correction options in 2) Calibrate as this may help. Have a look at the early part of this video tutorial:
Another thing you might look at is the power supply to your camera. Is this internal battery or a converter? I had a problem a year or two back which I eventually tracked back to low input voltage to my camera. If camera is unable to draw sufficient power then I think you can get strange patterns in the lights which will not calibrate out. Do you see any differences between images taken at start of your session versus the end?
best of luck
Mike
It would indeed be interesting to see how a single sub looks like and if you have the proper calibration data. The noise seems very high, what gain and other settings were used?
