Beginner DSLR tests: noise, gradients and low-contrast results – looking for advice

Yngvarr_75bigCatAstroandrea tasselliTony Gondola
40 replies413 views
Yngvarr_75 avatar

Description

These images are early test shots made to understand DSLR astrophotography workflow and limitations.

Equipment & settings

  • Canon EOS R8

  • Sky-Watcher Star Adventurer GTi (polar alignment ~1.5′)

  • No autoguiding

  • Acquisition via StellarMate / INDI

  • 30 s exposures

  • ISO 1600

  • Dark frames applied

Both targets were very low above the horizon (~20°).

Image 1 – M42 (no filter)

📷 VeraLux_Stretch (Grandi).pngVeraLux_Stretch (Grandi).png

  • 97 × 30 s, ISO 1600

The nebula is visible but looks very washed out and lacking contrast or “character”.
I would appreciate advice on whether this is mainly:

  • an exposure strategy issue,

  • a processing workflow issue (contrast, HDR, local enhancement),

  • or simply due to target altitude and sky conditions.

Image 2 – NGC 2238 (Optolong L-eNhance)

📷 NGC 2238 (Grandi).pngNGC 2238 (Grandi).png

  • 194 × 30 s, ISO 1600

Strong red background, visible diagonal banding and very weak nebula signal.

I’m trying to understand:

  • whether 30 s subs are too short for a dual-band filter

  • how much total integration time is realistically needed

  • optimal ISO choice for the EOS R8

  • whether the diagonal pattern could be walking noise

Additional issue
When capturing RAW FITS with StellarMate, the sensor is detected as ~6188×4100 px but files are saved as 6000×4000 px, producing black borders after stacking.
Any insight on INDI cropping or whether CR3/cRAW would be preferable is welcome.

📷 NGC_2238_Light_001_c (Grandi).pngNGC_2238_Light_001_c (Grandi).pngNote on optics
I’m aware that I’m currently imaging without a field flattener, and I’m already evaluating the purchase of one.
I understand the expected consequences on the frame edges (field curvature, star elongation and vignetting), so those issues are known and not the main focus of this post.

andrea tasselli avatar
I suspect the raw frames aren't calibrated before stacking. If it is so then do it. If it isn't then you have serious issues there. I know nothing about INDI or StellarMate. I use PCs. Sorry.
Yngvarr_75 avatar

Unfortunately, the images are calibrated. I did WBPP in PixInsight and I also tried in Siril (just for M 42), but the result is the same... I've noticed that the images are strangely bright, so much so that stretching them actually darkens them.

andrea tasselli avatar
Do NOT use WBPP. Obviously the calibration is wrong on multiple levels but I suspect flat correction is the main issue here. Without access to both the raw lights and the raw calibration frames is hard to say. ISO1600 should be your base operating ISO as far as Canons are concerned. 30s it's OK for M42 but for the Rosette you'd need to push it to 60s at least and best would be 180s using a LP suppression filter. Do not capture anything below 30deg for even acceptable results.
Concise
Tony Gondola avatar

You really need to calibrate with flats, bias and dark frames with flats being the most important. There’s plenty of info out there about how to do it properly. Also, your 2nd image does have a ton of walking noise. This will be hard to eliminate with your setup because you’re not guiding. The best you can do is randomly change your pointing by a small amount every few frames which will be a real pain. Lastly, don’t shoot low elevation targets. I’m in heavy B8 light pollution and I really try to restrict myself to a minimum elevation of 60 degrees. That really helps with background and gradients.

Helpful Concise
bigCatAstro avatar

Igor Fulvi · Dec 31, 2025 at 07:27 AM

Description

These images are early test shots made to understand DSLR astrophotography workflow and limitations.

Equipment & settings

  • Canon EOS R8

  • Sky-Watcher Star Adventurer GTi (polar alignment ~1.5′)

  • No autoguiding

  • Acquisition via StellarMate / INDI

  • 30 s exposures

  • ISO 1600

  • Dark frames applied

Both targets were very low above the horizon (~20°).

Image 1 – M42 (no filter)

📷 VeraLux_Stretch (Grandi).pngVeraLux_Stretch (Grandi).png

  • 97 × 30 s, ISO 1600

The nebula is visible but looks very washed out and lacking contrast or “character”.
I would appreciate advice on whether this is mainly:

  • an exposure strategy issue,

  • a processing workflow issue (contrast, HDR, local enhancement),

  • or simply due to target altitude and sky conditions.

Image 2 – NGC 2238 (Optolong L-eNhance)

📷 NGC 2238 (Grandi).pngNGC 2238 (Grandi).png

  • 194 × 30 s, ISO 1600

Strong red background, visible diagonal banding and very weak nebula signal.

I’m trying to understand:

  • whether 30 s subs are too short for a dual-band filter

  • how much total integration time is realistically needed

  • optimal ISO choice for the EOS R8

  • whether the diagonal pattern could be walking noise

Additional issue
When capturing RAW FITS with StellarMate, the sensor is detected as ~6188×4100 px but files are saved as 6000×4000 px, producing black borders after stacking.
Any insight on INDI cropping or whether CR3/cRAW would be preferable is welcome.

📷 NGC_2238_Light_001_c (Grandi).pngNGC_2238_Light_001_c (Grandi).pngNote on optics
I’m aware that I’m currently imaging without a field flattener, and I’m already evaluating the purchase of one.
I understand the expected consequences on the frame edges (field curvature, star elongation and vignetting), so those issues are known and not the main focus of this post.

Have you tried using the EKOS internal guider for StellarMate? It’s very powerful and will allow you to dither.

Also, I would avoid shooting objects that low in the sky, you’ll be shooting through atmospheric soup. I usually shoot objects that are at least 35 degrees in altitude.

Well Written
Yngvarr_75 avatar

Obviously, they were just test shots and I was aware that shooting low on the horizon would create a mess, and for M42 in the end, it was exactly what I expected, but the bitter surprise was with the Rosette Nebula; I didn't expect such a mess.

I only took 8 darks, do you think that's too few? So flats are important? And to think I hadn't given them much thought.

I don't have a guide telescope, but I still enabled dithering (only for the Rosette Nebula, M42 doesn't have dithering).

What causes it and what is 'walking noise'?

Thank you for your help! You are guiding me through the first more serious steps into astrophotography... the Seestar S50 was really just child's play, I actually spent more time in front of PixInsight than in front of the telescope!🤪

bigCatAstro avatar

Alright, to answer your questions in order:

Calibration frames are always going to be an important part of your imaging session. When imaging with a DSLR, it’s even more important to have great calibration frames since the sensor isn’t cooled and Canon cameras also tend to have horizontal banding. The general guidance for calibration frames has been to take at least 20 frames each for flats, darks, and biases. I usually shoot 40 of each, but that’s my preference only.

You don’t need a guide scope to use the EKOS internal guider. It uses virtual GPS in order to guide. It should be fairly straight forward to implement. This is a feature I wish NINA had.

Dithering is something you might hear debate on whether you need to or not. Personally, I’ve always had to dither and have never had success without it. Essentially, dithering is just moving your camera a few pixels to randomize your fixed pattern noise (e.g. hot pixels, etc). Dithering doesn’t get rid of noise—it helps to balance out noise so it can be averaged out during stacking. The rain-like noise on one of your example frames exhibits the classic walking noise pattern. Now, this is where the debate comes in since you can avoid dithering by having excellent polar alignment, superior calibration frames, and a high quality cooled camera. You can also do dithering the old fashioned way by moving the mount a little in each direction between frames.

Well Written Helpful Insightful Engaging Supportive
danieldh206 avatar

For DSLR Tony Hallas has great info. https://youtu.be/PZoCJBLAYEs?si=oovINxcZ_5aQWDjc

Flats and Bias calibration frames are extremely important calibration with Canons. Because the sensor temperature changes with a DSLR darks are tricky. More import than darks is dithering. With a DSLR you have to dither a lot! Dithering is the best noise reduction method with DSLRs. Tony Hallas explains in more detail in the YouTube video link. The software and mount you are using making dithering easy.

The R8 is a newer Canon and looking at some graphs ISO400 or ISO800 might be the sweet spot. You have to experiment. https://www.dxomark.com/canon-eos-r8-sensor-test/

With newer Canons there are new noise reductions features that need to be turned off. You have to dig through the menu settings to turn off.

Helpful
andrea tasselli avatar
Obviously, they were just test shots and I was aware that shooting low on the horizon would create a mess, and for M42 in the end, it was exactly what I expected, but the bitter surprise was with the Rosette Nebula; I didn't expect such a mess.

I only took 8 darks, do you think that's too few? So flats are important? And to think I hadn't given them much thought.

I don't have a guide telescope, but I still enabled dithering (only for the Rosette Nebula, M42 doesn't have dithering).

What causes it and what is 'walking noise'?


*Let me impress this on you: Correct flat capture and correction is THE most important part of calibration process and one that DOES need to be made on-site for DSLRs. I have shot a LOT with a variety of DSLRs and THAT what the most critical part, always. And yes, walking noise is a trap a lot of people fall into when starting and dithering is a sure-fire solution to that. The are other ways for sure but more involved and requiring multiple sessions to give the best results.
Yngvarr_75 avatar

I understand the things I was underestimating. Thank you.

To make flats on the spot, I read that some people use tablets with a white screen with a few sheets of paper in front of them. Is that a good idea? How many should I take?

As for the Rosette Nebula, I had set dithering every two shots, whereas for M42 I hadn't, yet it seems to have been much more disastrous, especially in terms of noise, with the Rosette in particular.

andrea tasselli avatar
I understand the things I was underestimating. Thank you.

To make flats on the spot, I read that some people use tablets with a white screen with a few sheets of paper in front of them. Is that a good idea? How many should I take?

As for the Rosette Nebula, I had set dithering every two shots, whereas for M42 I hadn't, yet it seems to have been much more disastrous, especially in terms of noise, with the Rosette in particular.

Yes, that, or shooting an evenly lit part of the sky at dusk (when the sun is just down or before it rises). Don't fuss too much on the histogram reading but avoid shoot too bright or too dim.  I can't comment on the Rosette as it seems to me that something else is at play there.
Arun H avatar
I am suspicious that any kind of dithering was done at all. By that I mean - you might have enabled a dither box somewhere - but in the absence of auto guiding, is dithering actually happening? In all the acquisition software I am aware of - NINA, Voyager, SGP - standard dithering is basically done via not the acquisition software but by the auto guiding software which sends the appropriate dither command to the mount once communicated to by the acquisition software. It then reports back to the acquisition software when mount has settled so acquisition can begin again. There are exceptions to this - when using high end absolute encoder mounts with tracking models, for example; in these cases, there is no guiding and dithering is done by direct communication to the mount. This is obviously not the case here, so my suspicion is that there is no dithering happening despite you checking a box. Which would completely explain the walking noise. Dithering is very effective at eliminating walking noise and the fact that you are seeing it to that level in your stack is highly suggestive of dithering not happening or being set to such a minimal level that it is not doing anything.

other than that, the advise here is good. The biggest problem with non cooled cameras is that calibration is highly non controlled. You can never really match the temperature of the lights and the darks which means elimination of fixed pattern noise, the basic purpose of dark frame calibration, is very inexact.
Helpful Insightful Engaging
Tony Gondola avatar

Actually, in NINA for the guider you can select “Direct Guider” and NINA will dither the mount without autoguiding software running. I did that on a regular basis in the early days and it seemed to work.

Well Written Concise
Arun H avatar
Tony Gondola:
Actually, in NINA for the guider you can select “Direct Guider” and NINA will dither the mount without autoguiding software running. I did that on a regular basis in the early days and it seemed to work.

yes - that was the exception I was referring to. You use direct guiding in NINA if you are not guiding but using a mount with a sky model and no guiding. I use direct guiding when I am using my Mach2 with a sky model, and in this case, guiding is unnecessary.

Unless the OP explicitly enabled the equivalent of direct guiding, if such a thing is even supported in the software he is using, my guess is that no dithering actually happened.
bigCatAstro avatar

Arun H · Dec 31, 2025 at 09:16 PM

Tony Gondola:
Actually, in NINA for the guider you can select “Direct Guider” and NINA will dither the mount without autoguiding software running. I did that on a regular basis in the early days and it seemed to work.


yes - that was the exception I was referring to. You use direct guiding in NINA if you are not guiding but using a mount with a sky model and no guiding. I use direct guiding when I am using my Mach2 with a sky model, and in this case, guiding is unnecessary.

Unless the OP explicitly enabled the equivalent of direct guiding, if such a thing is even supported in the software he is using, my guess is that no dithering actually happened.

I believe in EKOS (the OP is using StellarMate) it’s a checkbox option called “non-guide dither pulse” in the guide tab.

Astroberry had the same option since it used EKOS as well, so I would assume StellarMate has this option too.

Well Written Concise
Yngvarr_75 avatar

Yes, in the EKOS planner there is an option to select dithering and it lets me enable it even without guiding (by selecting after how many shots to apply the correction); whether this actually works or not, I couldn't say.

Yngvarr_75 avatar

Let's also take the topic from a different angle. Since I already have a DSLR and had read online that 'it could be done' with astrophotography as well, I went for it, also encouraged by the successes with the simple Seestar S50. But now I realize that maybe a DSLR isn't the best choice. Would all these problems I've encountered with DSLRs be resolved with astronomical cameras like yours (perhaps less expensive for now)? I was looking at something like the ASI585MC (maybe the Air series) or the ASI533... what do you think?

Obviously, I don't think (having now understood the world behind astrophotography) that changing cameras is the solution to all problems, but at least it might help avoid the ones I've encountered so far.

Engaging
andrea tasselli avatar
Astronomical cameras will provide for a much cleaner results with a much higher sensitivity but you'd still need to do your own homework and carry out frame calibration, signally flat correction but would allow you to avoid to a great degree issues such as walking noise following the right procedures.
AstroÅmazer avatar

I shoot with a Nikon Z5, a ZWO ASI858MC Pro and a ZWO ASI533MC Pro and a SW SA GTi and a ZWO AM3. Here are my observations:

  1. It is no use getting darks or biases from the Z5. Even when I get raw files, the bias and the darks are statistically the same. Since the Z5 does not have a BSI sensor, I am certain the EXPEED system is not giving me raw data. So I have stopped using darks and biases. The first black point correction takes care of the statistical noise floor.

  2. There is a faint circular pattern in my red and blue data and a faint vertical line when I use biases/flat darks in calibration. Looks like the capital letter Phi. It is very faint. I am assuming the line is the divide between the 2 registers where the sensor data is being simultaneously read. Not sure what the circular pattern is. Generally, unless I am shooting dust clouds like the Mandel Wilson 3, this is lost in denoising. Also another reason I stick to lights and flats only now with the Z5.

  3. If the payload is more than 8-8.5 lbs, no use dithering with the SW SA GTi. You will lose too much time waiting for it to settle. But I can get <1.2” guiding with proper balancing. Look into off axis weights. I use a small rig clamp and 100/200g weights to counter the asymmetric shape of the MILC.

  4. If you are using clip on filters and Z system lenses or telescopes without field flatteners/reducers, you will get severe blooming like the rosette pic. The flange distance between the last element of the Z system lens and the clip on filter is <16mm. The filter is not designed to handle such a large light cone. Probably the same issue without a field flattener. A field flattener on a telescope will collimate the light cone to a much tighter angle of incidence, making the filter work better.

  5. Do not trust ASIAir or similar to decide flat exposure times with DSLR/MILC. I go by the camera histogram and make sure most of the histogram is between the 25% and 50% lines (ideally 33% peak is best), and the histogram is not touching the y axis. If you have vignetting issues, and need to go past the 50% line to move the histogram off the y axis, make sure not to go past the 75% line in any channel. As many people have said above, proper flat correction is the most important issue with calibration.

  6. Again with cooled cameras with BSI sensors (no amp glow), build a library of darks and biases and take flats with ASIAir or similar. Happy hunting. and Happy New Year!

CS,

GD

Helpful
Yngvarr_75 avatar

As far as I know, the logic of the Z5 sensor is more or less the same as the R8, and as I actually knew, the RAW files it produces are not truly raw data, but already compressed by adjustments on the sensor.

As for the filter, I used a 2" filter inserted directly at the head of the optical train positioned towards the focuser.

Regarding the balancing and behavior of the SW SA GTi, I must say that I am satisfied; I can achieve alignments between 1.2" and 1.5" without too much difficulty, and the stars are always nicely round and sharp. In fact, I still have a doubt about whether a guide is necessary or not; it’s something I should look into, possibly for performing dithering, and it’s something to reconsider if I decide to switch to an astronomy camera.

I would like to say a few words to all of you who are helping me with this post, I didn't expect to have such wide support, thank you really to all of you! 🤩

Respectful Supportive
Yngvarr_75 avatar

I did a quick test with the same processing in PixInsight, but using only the lights, without darks and flats. 🫣

📷 integration_autocrop_ABE (Grandi).pngintegration_autocrop_ABE (Grandi).pngAt this point, the suspects are actually the darks, as he said AstroÅmazer

bigCatAstro avatar

Igor Fulvi · Jan 1, 2026 at 11:12 AM

I did a quick test with the same processing in PixInsight, but using only the lights, without darks and flats. 🫣

📷 integration_autocrop_ABE (Grandi).pngintegration_autocrop_ABE (Grandi).pngAt this point, the suspects are actually the punks, as he said @AstroÅmazer

The stars in the middle of the frame are not as round as they could be. Did you turn on the internal guider for EKOS?

Well Written Concise
Yngvarr_75 avatar

Actually, now that the image is more acceptable, I've noticed that the brightest stars aren't as well defined as they should be.

No, I haven't activated EKOS's internal guide.

Do you think the internal guiding of EKOS is an advantage or not? What could be the reason that the brightest stars are so blurry?

Well Written Engaging
Yngvarr_75 avatar

The discussion becomes more complicated for me here, now that I have taken my first steps in this field, and understanding how to navigate it, so I am assessing the situation in a broader way: in light of the limitations of DSLRs and also the rediscovered advantages since darks and biases are to be avoided, making things even simpler; is it worth spending 250 euros on a field flattener/reducer (going even wider) or is it better to invest that money in an astronomy camera? to also consider as a downside is the fact that DSLRs have a built-in IR/UV cut filter that already cuts the signal.

What do you think? What would you do? My goal is to have a fast and portable setup, since from my balcony I can only do tests because I have a limited portion of sky to shoot. I’d like to have a setup that gives as few problems as possible when I’m out in the field, and then maybe have fun with post-processing at home.

Correct me if I'm wrong (which is likely 🤭), but with my Evostar 72ED telescope an ASI 585MC doesn't need a field flattener because the sensor is so small that the 'good' part of the optics covers the entire sensor.