Simple Network mode is SysDVR’s default, and its simplest idea: the console publishes a standard RTSP video stream on your local network, and any compatible player can open it — no SysDVR-Client app involved. That makes it the only mode that works on devices with no client at all, like iPhones, iPads and smart TVs. The trade-off is latency and polish: as the author puts it, it may have higher latency or not look as good as the client modes, so treat it as the convenience option, not the performance one.
The address every player needs
Whatever player you use, the stream address is always the same pattern — the console’s local IP on port 6666:
rtsp://<SwitchIP>:6666/You’ll find the console’s IP in the Switch’s Settings → Internet page (it shows the current connection details) or in your router’s list of connected devices. Simple Network is the default mode, but if you changed modes before, set it back in SysDVR Settings on the console (full build) — USB-Only builds don’t offer network modes at all.
mpv — the recommended player
The official guide recommends mpv, because it can be told to prioritise latency over buffering. Point it at the stream with the author’s low-latency flags:
mpv --profile=low-latency --no-cache --cache-secs=0 --demuxer-readahead-secs=0 --cache-pause=no rtsp://<SwitchIP>:6666/You can also choose the transport protocol: --rtsp-transport=udp for the lowest latency on a clean network, or TCP if your Wi-Fi is congested and UDP gives you artefacts and dropouts. The flags above disable the caches that otherwise add seconds of delay, which is exactly what you want when you’re actually playing through the stream rather than just watching.
VLC
VLC works too: use Media → Open Network Stream, paste the rtsp://…:6666/ address, and play. Expect noticeably more delay than mpv with the flags above — VLC buffers network streams conservatively and is best here for watching or testing, not for playing action games through the stream.
OBS Studio
OBS can take the RTSP address directly as a Media Source: add the source, untick “Local File”, and paste the stream URL as the input. Know the cost before you build a setup on it — OBS adds buffering delay to media sources, so the preview you play from will lag behind the console. For broadcasting that’s usually acceptable (your commentary setup matters more), but for playing through OBS, a client mode feeding OBS is the better architecture; see streaming to Twitch & YouTube with OBS.
When to choose Simple Network mode
- Devices with no SysDVR client: iPhone and iPad (there is no iOS client — RTSP players are the workaround, covered in SysDVR on iPhone & iPad), smart TVs, and spare laptops.
- Quick checks: verifying the sysmodule works before installing anything else.
- Casual viewing: a second screen for someone watching you play, where a little delay doesn’t matter.
When latency matters — rhythm games, fighters, anything twitchy — switch the console to TCP Bridge mode with the client, or go all the way to USB mode. Simple Network’s job is reach, not speed.
A practical tip regardless of player: because the address is just an IP, save it as a bookmark, playlist entry or OBS scene now, while it works. If it ever stops connecting weeks later, the most likely change is the console’s IP being reassigned by your router — ten seconds to check, and the checklist below covers it.
Player choices compared
| Player | Latency | Setup effort | Best for |
|---|---|---|---|
| mpv with the low-latency flags | Lowest of the three | One command line | Actually playing through the stream |
| VLC | Noticeable buffering delay | A few clicks | Quick tests and casual watching |
| OBS as a media source | Adds its own buffering delay | One source to add | Broadcasting or recording the stream |
What quality to expect
The stream itself is the same one SysDVR always produces: 720p at 30fps, H.264 video with uncompressed 16-bit 48 kHz stereo audio. Simple Network doesn’t lower the resolution — the difference from the client modes is delay and smoothness under load, because a general-purpose player buffers more and optimises for playback rather than interaction. For watching, recording a casual session, or putting gameplay on a TV in another room, most people never notice. For playing a platformer through the stream on a big TV across the house, you’ll feel the extra delay in jumps and parries — that’s your cue to use a client mode on that device instead.
If the player won’t connect
- Check the mode. The console must be in Simple Network mode (Settings app) — a console set to TCP Bridge or USB doesn’t serve RTSP.
- Check the IP. DHCP can reassign the console’s address after a reboot or router restart; re-read it from the console’s Internet settings and update the URL.
- Check the network. Player and console must be on the same local network, and the router must not isolate clients (guest networks and hotspots often do).
- Check the timing. The sysmodule starts about 20 seconds after boot; a connection attempt before that fails for the simplest of reasons.
- Expect a short wait for picture. The stream begins at the next keyframe (roughly every two seconds) — moving the in-game camera helps it lock on.
Next steps
- Install SysDVR on the console — if you haven’t done the console side yet.
- SysDVR Client setup (Windows) — the client unlocks the lower-latency modes.
- Full map of modes and guides: the SysDVR setup guide hub.