-
-
Notifications
You must be signed in to change notification settings - Fork 100
Advanced tips
You can use the old interface by passing the --legacy option to the client, this will turn the player into a simple window with the video and no buttons.
SysDVR client discovers consoles in your local network using UDP broadcast packets, your console is continuously sending these packets so the client can find it. You can disable this feature by creating a file called /config/sysdvr/no_adv on your console's sd card (create the folders that do not exist already). The file can be empty, it just needs to exist.
If you are using windows make sure the file has no extension.
When you disable network discovery SysDVR will not be able to find your console and you will have to manually enter the IP address of your console in the client.
When using Simple network mode you can add your console directly as a source to OBS.
To do this, add a new media source from the main OBS window and untick local file, then type rtsp://<ip address>:6666/ where <ip address> is the IP address of your console.
Note that this will add some delay to the stream since RTSP is usually buffered.
The built-in video player in SysDVR-Client 5.0 by default will use ffmpeg's default decoder for h264, in my tests this is always a software decoder, you can provide your own decoder name with the --decoder <decoder name> option from the command line.
This is especially useful on mini PCs where decoding the video stream in software is too slow.
To view the decoders installed on your pc you can do dotnet SysDVR-Client.dll --show-decoders, in the output the decoder called h264 is the default one, the part before : is the name you have to use with the --decoder option.
Note that the decoders shown are all the ones enabled in the ffmpeg build you're using, for example on an AMD pc you may see the Intel video decoder, that's not going to work.
As codecs are part of the ffmpeg libs you may want to provide your own libs, on windows replace the av*.dll files in runtimes/win-x64/native with your custom build. On linux and mac it depends on how you installed ffmpeg.
There's also the --hw-acc option that will choose the first decoder that it can find but it may not work because as explained earlier ffmpeg may show some decoders not compatible with your hardware.
The best streaming setups i can think of, from best to worse, are:
- 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.
- Switch and PC connected via lan to the same router.
- Switch connected to a near 5GHz router and PC connected via lan.