SysDVR’s stream is a modest 720p30 feed, so when it lags, stutters or the audio drifts away from the picture, the bottleneck is almost never raw bandwidth. The most likely causes are the client’s audio/video sync keeping frames waiting, and the quality of the local connection between console and PC. Both are fixable in minutes.
One myth to drop immediately: your internet speed is irrelevant. SysDVR network streaming is entirely local — what matters is the signal and path between the Switch and the receiving device, nothing upstream of your router.
Fix 1: Toggle “Disable Audio/Video sync” in the client
SysDVR-Client has a setting to disable A/V sync. With sync enabled, the client holds audio and video together, which adds latency and can turn small connection hiccups into visible stutter. Disabling sync reduces latency and smooths out glitchy video — the trade-off named in the official notes is that audio may drift out of sync. So treat it as a lever, not a permanent answer:
- Video lags or glitches: disable A/V sync and see if the picture smooths out.
- Audio is ahead of or behind the picture: try the opposite state — re-enable sync if you disabled it, and improve the connection (Fix 2) so sync no longer costs you stutter.
Fix 2: Climb the connection hierarchy
Local connection quality decides everything. From best to worst:
- Wired LAN for the console (dock with a LAN adapter, PC wired too) — the most stable option.
- Console and PC on the same router, close to it.
- Near 5GHz Wi-Fi — acceptable when you are close to the router; distant or congested Wi-Fi is where stutter lives.
Move the console and PC closer to the router, get both onto the same network, and avoid public or heavily shared Wi-Fi. “Wired” for a Switch means the dock’s built-in LAN port (on the OLED dock) or a USB LAN adapter in the dock — it removes Wi-Fi from the console’s half of the path entirely, which is the half that usually suffers. If you use TCP Bridge mode, that is already the lowest-latency network mode. And if you are on 2.4GHz Wi-Fi because it “reaches further”, try 5GHz anyway: for a stream this small, a clean short-range 5GHz link beats a strong but crowded 2.4GHz one almost every time.
Fix 3: RTSP delay that grows over time is a cache problem
In Simple Network (RTSP) mode, players like mpv use a cache buffer to ride out dropped packets — and that buffer slowly turns into delay, so the stream feels fine at first and seconds late after a while. Use mpv’s low-latency flags (--profile=low-latency --no-cache --cache-secs=0 --demuxer-readahead-secs=0 --cache-pause=no) as covered in the RTSP mode guide. OBS as a media source adds its own buffering delay on top — expect a little, always.
Quick reference: symptom to fix
| Symptom | Most likely cause | Fix |
|---|---|---|
| Constant stutter / glitches | A/V sync holding frames, weak local link | Disable A/V sync; improve connection (LAN / same router) |
| Delay grows the longer you watch | Player cache in RTSP mode | mpv low-latency flags; restart the player to reset delay |
| Audio out of sync with video | A/V sync disabled, or marginal connection | Re-enable A/V sync; improve connection quality |
| Lag even on a good network | Decoder struggling on the PC | Try another decoder / hardware acceleration (advanced tips) |
Fix 4: Use USB mode as the zero-network test
Want to know in one minute whether your network is the problem? Switch SysDVR to USB mode and stream over a cable with the USB setup. USB is the lowest-latency mode and removes the network entirely. If USB is smooth, your sysmodule and client are healthy and every remaining problem is your local network path. If USB also stutters, look at the PC side — decoder choice and hardware acceleration, covered in the advanced tips post.
RTSP transport: UDP for latency, TCP for stability
If you watch in Simple Network mode with mpv, the transport protocol is a real lever: mpv can pull the RTSP stream over UDP or TCP (--rtsp-transport=udp). UDP skips retransmission, so delay stays minimal — but every dropped packet on a lossy Wi-Fi link shows up as a glitch or a freeze. TCP delivers everything, which looks cleaner on a weak signal, at the cost of extra delay when packets need resending. On a solid connection, UDP is the low-latency choice; on a marginal one, TCP plus the no-cache flags is often the smoother watch. Try both — the better one depends entirely on your room, not on the console.
Glitches point at the link, stutter points at sync
Learn to read the failure, because the two big symptoms have different owners. Random visual glitches and artifacts mean data is arriving damaged or late — that is the connection, and only the hierarchy in Fix 2 (or the USB test in Fix 4) cures it. A picture that is smooth but consistently behind, or that judders in a steady rhythm, is the client managing sync and buffering — that is Fix 1 and Fix 3 territory. Chasing the sync toggle for a glitching picture, or rewiring your network for a rhythmically juddering one, wastes an afternoon; match the fix to the symptom.
Still stuck?
If lag survives a wired connection and the sync toggle, note your mode, connection type, and both SysDVR versions, then ask in the project Discord or open a GitHub issue. Related guides on the troubleshooting hub: client can’t find the console and no audio at all (different problem from desync — silence has its own checklist).