The cause: the sky does not stop turning between frames
Star trail stacking joins the arcs your camera recorded. Every second the shutter is closed, the sky keeps rotating and nothing records it, so that piece of the arc simply does not exist in your data. Stack the frames and those missing pieces show up as dark breaks: dashes instead of lines.
This is why the problem gets worse the longer your dead time is, and why it is invisible on a single frame. It is a capture issue that only reveals itself after stacking, which is what makes it so frustrating to discover at the end of a cold night.
The dead time comes from a short list of culprits, in rough order of how much damage they do:
- Long exposure noise reduction. The camera shoots a second, equally long dark frame after every exposure. A 30 second frame becomes 60 seconds of camera time, half of it recording nothing. This produces gaps as long as the dashes.
- Interval timers set too generously. An intervalometer set to 35 seconds for a 30 second exposure builds in five seconds of guaranteed sky rotation you will never get back.
- Slow card writes. Large RAW files on a slow card, or RAW plus JPEG, can stall the next exposure.
- In-camera corrections such as lens correction or high ISO noise reduction applied to RAW, which add processing time between frames.
How much gap is visible
The sky turns 15 arcseconds per second of time. Whether that shows depends on your focal length, but the proportion is easier to think about: the gap is the dead time divided by the total cycle time.
| Exposure | Interval | Dead time | Result |
|---|---|---|---|
| 20 s | 21 s | 1 s | About 5 percent break, subtle but visible at full size |
| 20 s | 25 s | 5 s | 20 percent break, clearly dashed |
| 30 s | 60 s | 30 s | Noise reduction left on: dashes and gaps are equal |
| 25 s | 26 s | 1 s | About 4 percent, the practical target |
Below roughly five percent, gap filling closes the trails convincingly. Above twenty percent, you are asking software to invent most of the arc, and it will look like it.
Fixing it at capture
- Turn off long exposure noise reduction. This single setting is the most common cause. Shoot dark frames separately at the end of the session instead and let your stacker use them.
- Use continuous drive with a locked remote release rather than the camera's interval timer. The camera fires the next frame the instant it can, which is the shortest dead time your body is capable of.
- If you must use an intervalometer, set the interval to the exposure plus one second. Not plus five. Test it before you commit to four hours.
- Shoot RAW only, on a fast card. Drop the simultaneous JPEG.
- Turn off in-camera lens corrections and high ISO noise reduction where your body allows it.
- Check after ten frames. Look at the file timestamps: the difference between consecutive frames should be your exposure plus about a second.
Repairing a sequence you already shot
The fix is gap filling, and there are two ways software does it, which produce noticeably different results on wide lenses.
Interpolated gap filling blends between the frames on either side of the gap. It works, and it is what most free tools do. Because it does not know where the sky actually is, it bridges the gap along a straight line between the two positions.
Geometric gap filling works out where your camera was pointed by identifying the star field, then synthesizes the missing positions along the true arc each star traveled. On a 14mm or 20mm lens, where trails curve strongly across the frame and the celestial pole may sit inside the picture, that difference is the difference between a smooth arc and a chain of straight chords.
Satrelle does the second kind, and applies it automatically when it detects dead time between your frames. There is nothing to switch on. If you want the detail on how the sky solve drives it, the guide covers it.
Gap filling reconstructs, it does not resurrect. If half your cycle time was dead, no software will give you a genuinely continuous trail. Fix the capture and the repair becomes invisible.
Questions
Why are my star trails dashed instead of continuous?
Because the sky kept turning during the gap between your exposures. Every second the shutter is closed is a piece of the arc that was never recorded, and a lighten blend cannot invent it. A one second gap between 20 second frames leaves roughly a 5 percent break in every trail, which is clearly visible at full size.
How do I stop gaps in star trails when shooting?
Shorten the dead time between exposures. Shoot in continuous drive with a locked remote rather than using the camera's interval timer, turn off long exposure noise reduction, which doubles your dead time, use a fast card and shoot RAW without an extra JPEG, and set the interval to the exposure time plus one second at most.
Can I fix dashed star trails after the shoot?
Yes. Gap filling reconstructs the missing pieces of each arc. Simple gap filling interpolates between the frames you shot. Satrelle solves the star field first, so it knows the true path each star traveled and synthesizes the in-between positions along that arc, which matters most on wide lenses where trails curve strongly.
Does long exposure noise reduction cause gaps in star trails?
Yes, and it is the most common cause of severe gaps. Long exposure noise reduction takes a second dark frame of the same length as your exposure, so a 30 second frame becomes 60 seconds of camera time with 30 seconds of it recording nothing. That produces trails that are dashes with gaps as long as the dashes. Turn it off and use dark frames in stacking instead.
Related
- My star trails are straight lines instead of arcs
- Removing aircraft and satellite trails
- Star trail exposure and arc calculator
- The complete guide to star trail photography on a Mac
macOS 12 Monterey or later · Apple Silicon