Optional: Remote RTMP Server

Thanks to Tidy at dlive.tv for giving us guidance on the setup necessary

Intro

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:

  1. Remote RTMP Server PC
  • Runs Dlive Protocol
  • Runs nginx to listen for RTMP data and sends to Dlive Protocol client
  1. 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:

  1. Install Dlive Protocol and create a new channel. Make note of the stream key in Stream Info.
  2. 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.
  3. Allow incoming TCP traffic from port 1935 in Windows Firewall.
  4. 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:

  1. In Settings, Stream, Server, set to:
rtmp://<ip address of remote rtmp machine>/live
  1. In Settings, Stream, Stream Key, set the same stream key shown in Dlive Protocol Stream Info and in nginx.conf