PVI VECASTER PRO Series, Manual

Page: 40 / 45

VECASTER SERIES MANUAL Pro Video instruments
39
STREAMING PROTOCOLS
1. .TS format — MPEG Transport Stream
● Digital container format for transmission and storage of audio, video, & PSIP Data.
● Encapsulates packetized elementary streams and equips them with error correct and synchronization features to
maintain transmission integrity when the communication channel carrying the stream is degraded.
● Ideal for maintaining transmission integrity over unknown or unreliable mediums.
● Can carry multiple programs.
2. RTMP — Real Time Messaging Protocol
● Protocol developed for streaming audio, video, and data over the internet.
● RTMP is a TCP-based protocol which maintains persistent connections and allows low-latency communication.
● Splits streams into fragments and their size is negotiated dynamically between the client and server.
● In practice individual fragments are not typically interleaved. Instead, the interleaving and multiplexing is done at
the packet level, with RTMP packets across several different active channels being interleaved in such a way as to
ensure that each channel meets its bandwidth, latency, and other quality-of-service requirements. Packets
interleaved in this fashion are treated as indivisible and are not interleaved on the fragment level.
3. HTTP — Hypertext Transfer Protocol
● An application protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of
data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources
that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.
● HTTP functions as a request – response protocol in the client – server computing model. A web browser, for example,
may be the client and an application running on a computer hosting a website may be the server. The client
submits an HTTP request message to the server. The server, which provides resources such as HTML files and other
content, or performs other functions on behalf of the client, returns a response message to the client. The
response contains completion status information about the request and may also contain requested content in its
message body.