In-4 < Unicast/Multicast Transport Streams In
This is the preferred method for providing stream input to the DME when Transport Stream is required. Transport Stream is required in cases where transport of metadata such as KLV is required, since no other protocol is capable of transporting this metadata. In this scenario the DME input is a live stream push from a Transport Stream transmitter. Common examples of sources capable of producing a live Transport Stream push include a VB6000/7000/9000 VBrick MPEG‑2/H.264 encoder or another DME.
| Note: If you wish to redistribute the stream using Unannounced RTP (Out-7), Served RTP from the RTP Server (Out-4), or Push RTP via RTSP from the RTP Server (out-11) an internal RTP Push (Out-10) must be configured. |
To configure a unicast/multicast (TS) input:Objective: Use this option if you need to tune into an MPEG2TS carrying an H.264 load and need to distribute it further. The transport stream is either a multicast on your network or a unicast directed to this DME from a source.
●If multicast, you will need to know the IP address and port the multicast is being sent on.
●If unicast to you, you will need to know which port number it is being sent to.
1. Fill in the multicast address and port if multicast, or enter and port if unicast. For source specific multicasts, enter the multicast address followed by a colon and then the source address. Example:
2. Enter the port number. The port number needs to be unique for all unicast sources specified in the list.
3. Enter a name for this incoming transport stream. You can also use the default name, or create another meaningful name for this stream. The name is used to distribute the stream to other destinations and stream types.
4. Enable the location and click . The status will indicate “Receiving” if the stream is found and being received. It will display “Waiting For Stream” if the stream is not detected. For multicast sources, the multicast address and port combination must be unique. For unicast sources, the port number must be unique (i.e. the same port cannot be used for multiple unicast receive.)
TS Pull supports true pass-through without any parsing of the stream so the stream and all of its contents including KLV (if any) can be passed through to other TS destinations. See use case
Out-5 > Push TS for more information.
The incoming name specified in the user interface can now also be used to stream the incoming transport stream as RTMP, RTP (via RTSP), or HLS. Once configured, you can see details about this stream in the Monitor >
Multi Protocol Connections page. .
See Also:
