Chapter 7 Server Output Data Format 7-7
7.4.2 MPEG-2 Program Stream Packet Encapsulation
The MPEG-2 Program Stream is not defined to have any fixed packet size by the
MPEG-2 standard. The server delivers UDP packets with payload containing MPEG
data of size corresponding to seven MPEG-2 transport packets or 1316 bytes for the
program stream encapsulation. This encapsulation uses the same Ethernet packet
size as is used for the MPEG-2 Transport Stream.
7.4.3 MPEG-1 System Stream Packet Encapsulation
The MPEG-1 System Stream is not defined to have any fixed packet size by the
MPEG-1 standard. The server delivers UDP packets with payload containing MPEG
data of size corresponding to seven MPEG-2 transport packets or 1316 bytes for the
program stream encapsulation. This encapsulation uses the same Ethernet packet
size as is used for the MPEG-2 Transport Stream.
7.4.4 Thomson Electronics Encapsulation
The encapsulation supported here consists of multiple TCE MPEG packets as
payload of UDP over IP, which provides a connectionless transport mechanism. The
number of TCE MPEG packets for every UDP payload is eleven, which is the
maximum number of 130-byte TCE transport packets that fits in the largest
allowable Ethernet packet of 1500 bytes.
7.5 Fast Ethernet Addressing
The server delivers video data to a specified IP hostname and UDP port number.
Therefore, the data endpoint address is described by the concatenation of an IP
hostname and UDP port.
You specify the destination address with the MSMC API’s msmSetConnect()
function. You fill in an instance of the MsmConnect structure before calling
msmSetConnect(). This structure contains an destTiAddr field, which holds a
string. This field determines the destination address to which the server delivers
data. The address is a string of the following format:
host=<IP hostname>,udpport=<UDPport num>