Skip to content

Advanced tips

exelix edited this page May 26, 2020 · 7 revisions

RTSP over TCP and UDP

This is especially important for direct RTSP mode.
The SysDVR server supports two modes: TCP and UDP, this usually doesn't matter but I've found different programs will connect using different modes, eg. mpv will always use TCP while obs will try UDP first and then TCP. Depending on your network environment you can find one to perform worse than the other so you'll have to test which one works best for you.

In mpv you can force udp mode by running mpv rtsp://<SwitchIpAddress>:6666/ --rtsp-transport=udp.

Multiple client instances

You can stream multiple consoles to the same pc by launching SysDVR-Client multiple times, for RTSP you have to change the port by adding the --port <port number> option to the command line. This is not supported in the GUI.

Streaming setups

The best streaming setups i can think of, from best to worse, are:

  1. Switch and PC directly connected to each other via lan. For this to work you'd need to host a dhcp server, your own 90dns instance and a server to spoof conntest.
  2. Switch and PC connected via lan to the same router.
  3. Switch connected to a near 5GHz router and PC connected via lan.

Libusb on windows

Since SysDVR 4.0 the client has a custom WinUsb backend to improve USB performances on windows, due to protocol differences it won't work with libusb, if you're on windows and installed the libusb-win32 driver you can force it by selecting Force LibUsb backend in the GUI or by adding --no-winusb to the command line.

Clone this wiki locally