More technical streamers can optionally build out a remote windows machine that runs an nginx server to receive RTMP traffic and route the stream through Dlive Protocol. The advantage of a remote RTMP server is the networking resources for streaming is separated out from the gaming machine. It's particularly useful if the RTMP server machine has a higher available upload bandwidth.
The two parts include:
- Remote RTMP Server PC
- Runs Dlive Protocol
- Runs nginx to listen for RTMP data and sends to Dlive Protocol client
- Gaming PC
- Runs game and OBS Studio
- Sends RTMP stream to Remote RTMP Server
Remote RTMP Server Setup
On the windows machine that will be the remote RTMP server, perform the following:
- Install Dlive Protocol and create a new channel. Make note of the stream key in Stream Info.
- Install ngninx version 1.7.12.1 from http://nginx-win.ecsds.eu/download/ The binary includes the plugin nginx-rtmp-module already built in.
- Allow incoming TCP traffic from port 1935 in Windows Firewall.
- Add the settings below into the nginx.conf. Note the ip address for the gaming machine and the stream key from step 1 is needed.
rtmp {
server {
listen 1935;
chunk_size 4096;
application live {
live on;
record off;
allow publish <ip address of gaming machine>;
deny publish all;
push rtmp://localhost/app/<the stream key>;
}
}
}
Gaming PC Setup
Configure OBS Studio with the following settings on the gaming machine:
- In Settings, Stream, Server, set to:
rtmp://<ip address of remote rtmp machine>/live
- In Settings, Stream, Stream Key, set the same stream key shown in Dlive Protocol Stream Info and in nginx.conf