NewTek TriCaster 2 Elite (3 RU) User Manual
Page 202
P a g e | 184
in contrast to other types of online video distribution which requires the viewer to completely download the
video file before he can begin play. Given a sufficiently high-speed connection between host and viewer, they
may well be able to enjoy a seamless viewing experience without stuttering or other issues.
L
IVE
S
TREAMING
Live streaming is a growing international market, and one you may well wish to serve. This form of streaming
is a somewhat more demanding implementation. Rather than record a file and deal with it later, live video
is transmitted over the network (effectively in real-time
, give or take a little ‘time in the pipe’ as it were.)
Delivering a good quality stream requires that you consider both your network connection capabilities and
that of your viewers. As well, to ensure reliable delivery, you will ideally have some idea of the size of your
audience.
Naturally, streaming video is highly compressed to reduce bandwidth demands and make it available to a
wider group. The decision as to which encoding format to use for your live stream is up to you or
–
in some
cases
–
your client. Here are some things to consider:
▪
Some corporate and institutional network administrators opt to support one or another format
exclusively. (Check with your IT department to find out if this affects your decision).
▪
RTMP and RTSP combined have a very wide installed user base, and work well across multiple
platforms (PCs, Macs, Linux, etc.).
▪
SRT is an open source protocol that is managed by the SRT Alliance. It can be used to send media
over unpredictable networks, like the Internet. More information about SRT can be
found here -
RTSP
S
TREAM
D
ECODING
The processing demands from high-quality video applications and devices have increased in the last few
years. As video content continues ever-expanding, technology evolves to handle the demand. Beginning with
TriCaster version 7-4 dated January 2021 and later, TriCaster will take advantage of GPU hardware
acceleration for all stream decoding.
Unfortunately, some streams are simply incompatible with the GPU decoder. We recommend that the
originating stream vendors look to solve the compatibility and take advantage of modern GPU decoding. We
also understand that users of TriCaster may not have that option and must wait for vendor development
cycles.
As a workaround, if a stream is found to be incompatible, you can append the URL with a command that
instructs TriCaster to not use hardware acceleration.
(optional components are enclosed in square brackets)
rtsp:
//\[username\[:password\]@\]ip\_address\[:rtsp\_port\]/server\_URL\[?param1=val1\[¶m2=
val2\]...\[
&hw_accel=false
\]\]
For example, the original URL of:
rtsp:// stream_IP_address.com:554/myStreamserver
Would change to:
rtsp://stream_IP_address.com:554/myStreamserver
?hw_accel=false