Transport Stream In
To access the Transport Stream In fields:
1. Navigate to > .
Use this page to configure streams pushed via unicast or multicast to the Multi-Protocol server using transport stream. The number of streams supported depends on the model of the DME.
MPG2TS Streams
The DME can accept a live unicast or multicast MPEG2TS (with an MP2 or MP4 H264 payload) and deliver it from the DME as unicast or multicast. (A live MPEG2TS is typically pushed from a a VB6000/7000/9000 VBrick MPEG‑2/H.264 encoder or another DME.)
For H264 content wrapped in an MPEG2TS, the stream can also be transmuxed and delivered as Flash, HLS, RTP, or HDS.
For MYPEG-2 content, there is no transmuxing. In order to identify an incoming Transport Stream with MPEG‑2 content (so that it can be “passed through” without further parsing), the incoming stream name must be preceded with “:”.
For example, when configuring a (with MPEG‑2 content) the must be:
Similarly, you must use the same (preceded with ) when configuring the stream for . Using this stream as input for HLS or other conversions will not work. Passthrough Transport Streams preserve KLV data when being delivered through the DME.
Field | Description |
Stream Name | Name used within the DME to connect input and output streams. Use the default stream name (, etc.) or override as desired. See above, MPG2TS Streams (with MP2 content) must be prepended with |
Multicast Source / Localhost | Source of multicast stream/local host. If the stream is a unicast to the DME, enter the DME's IP address. For source specific multicast addresses, enter it as "multicastipaddress:sourceipaddress.". Example: 232.1.1.1:172.22.2.166 |
Port | Port on which the stream is unicast or multicast. If there are multiple unicast input streams, be sure that each input stream has a unique port number. |
Enable | Use to enable an input stream. |
Status | Read only: Disabled | Connected | Receiving. |
