Introductory Suggestions For Your First Testing
No doubt you will be
substituting your own binaries that call librist. It is unlikely that
you will use exactly the same command line parameters as the sample
binaries, but this document make use of them to illustrate several
scenarios. Because this is an introductory document, it will focus on
the main profile. There will be a followup document.
First Test: Sender
stream source (192.168.1.11) emits a unicast udp stream to the rist
sender at port 19994. You can start the stream before establishing
the rist connection between rist sender and receiver, or after. If
debugging, and trying to establish that rist sender and receiver are
establishing a connection properly, hold the stream off until after
the connection has been established. By doing so, you can read the
messages to standard output easier.
sender (192.168.1.12) “listens” (the @ sign means it will
listen) at port 1994 for that stream.
sender (192.168.1.12) also “listens” at port 8193 (the @ sign,
again) for the 1st rist receiver to initiate the connection. Later
we will show an example where the receiver “listens” for the
rist receiver contacts the sender on port 8193 and initiates the
connection. Some parameters are set only on the sender; the receiver
obtains any such parameters upon the establishment of the
initiated, the rist sender (192.168.1.12) sends it to the 1st
rist receiver on port 8193 using the main profile (-p 1).
receiving the stream, the 1st rist receiver emits the
de-risted stream to another host (192.168.1.14), which will be able
to view it using a client such as vlc. In the example below, a vlc
client running at the host with the address 192.168.1.14 would
therefore be able to view the stream by opening a network stream at
cases, AES128 should be sufficient. AES256 is available, but some
may find that the additional security is not a good “value” as
measured by “bang for the buck. Adding the parameter “-t 2”
will use the AES256. But please feel free to err on the side of
-e parameter, as was done in the previous example, sends the stream
Note that (on the
rist side, not the ingress media side of the command line) we have
merely moved the “@” sign and changed the IP address from the
sender host to the receiver host’s IP address. In all cases when
you use the “@” sign, you will be using it with an IP address on
the host at which you are running the binary. The receiver will
listen, and the sender will initiate in the example below.
Multicast being a
common and highly useful protocol in professional streaming, it is
important to incorporate at an early point in testing. We recommend
not testing multicast in your very first test, because unicast
is usually easier to debug. At this point, however, you’ve sent a
few streams via librist.
We add one more
host, 192.168.1.23 as a second receiver. The second receiver
parameter is “-b.” The binaries in the project support up to four
(-s, -b, -c, -d, in that order). The sender specifies another pair of
ports for the second channel. The second receiver emits its outbound
stream to yet another host (192.168.1.15). Note that the sender
requires an additional port for each receiver.