Configure the input

There are multiple types of transport stream configurations. Each type presents a different set of parameters.

Configure a transport stream input for Satellite demodulator

Before you start, ensure:

  • the following option must be available within the server: MKP/HWO/PCI/SAT/DEMOD.
  • a Receiver service is configured.
  1. From the Home page, select the RECEIVER item from the required feed then click .

  2. From the Primary tab, select Satellite for the Input type. Satellite input options display.

  3. Set the LNB parameters, LNB frequency, LNB voltage and 22kHz.

    2 license key tokens (Max 4 inputs requires 8 tokens) are required to enable the higher order modulation schemes (16APSK and above) for each satellite input.

  4. Set the Tuner parameters, Frequency, Symbol rate, Search range, C/N Margin Alarm, MIS enable, MIS Stream ID, and Gold code.

  5. Ensure that the Source Status is green (receiving) for existing sources, and that no errors occur.

Configure the transport stream input for satellite

There are 4 independent satellite inputs. You can route a single satellite input to independent services, or to route a single input to multiple services.

The satellite input option is compatible with:

  • DVB-S (EN300-421)
  • DVB-S2 (EN302-307-1)
  • DVB-S2 extensions
  • DVB-S2X (EN302-307-2)

DVB-S2 offers up to a 30% increase in data rate carriage for an equivalent link margin compared to what the older DVB-S standard can offer. This functionality is often partnered with MPEG-4 or HEVC compression to give bandwidth efficient distribution of high definition or ultra-high definition services.

DVB-S2X is an extension to the DVB-S2 standard and can provide up to 20% performance improvement compared to DVB-S2 and increase the efficiency of satellite links. This will enable an increase in video quality or an increase in the number of video services or a reduction in leased satellite bandwidth, bringing lower operational expenditure.

Configure transport stream input for ASI

A Receiver service can support decoding or passthrough of transport streams into RX1 over ASI.

Before you start, ensure:

  • at least one service is configured.
  • the following option is available within the server: MKP/HWO/PCI/ASI/IN.
  1. From the Home page, select the RECEIVER item from the required feed then click to edit.

  2. From the Primary tab, select ASI for Input type.

    Packet size depends on the input format. For ASI options are either 188 or 204.

  3. Configure the TS packet size and the ASI Port.

  4. Ensure that the Input Status is green (receiving) and that they're no errors (this only applies if the source currently exists).

Configure transport stream input for IP input

A Receiver service can support decoding or passthrough of transport streams into RX1 via Ethernet.

Configure transport stream input for IP in unicast

Before you start, ensure at least one Receiver service is configured.

  1. From the Home page, select the RECEIVER item from the required feed then click to edit.

  2. From the Primary tab, tick Unicast. Stream address is greyed out and a port parameter displays.

  3. Enter the UDP Port number for the incoming transport stream.

  4. Select the Ethernet port for the Network interface that the incoming transport stream is available on.

  5. Ensure that the Input status is green (receiving) and that they're no errors (this only applies if the source currently exists).

Configure transport stream input for IP in multicast

Before you start, ensure at least one Receiver service is configured.

Transport streams can be streamed into RX1 over either Ethernet (IP) or ASI depending on the hardware installation.

  1. From the Home page, select the RECEIVER item from the required feed then click to edit.

  2. From the Primary tab, check that the Unicast checkbox is unticked then enter a multicast Stream address.

    The Multicast parameter is grayed out if Unicast is selected.

  3. Enter the UDP port number for the incoming transport stream.

  4. Select the Ethernet port for the Interface that the incoming transport stream is available on.

  5. Ensure that the Input status is green (receiving) and that they're no errors (this only applies if the source currently exists).

Transport stream passthrough

The RX1 supports up to a maximum of 4 independent ‘TS passthrough’ Receiver services.

The incoming transport stream can be received via either the IP, ASI or Satellite interface and can be routed unaltered to the IP output interface.

It is possible to decrypt up to 15 services from the incoming TS using BISS v1, BISS v2 (including BISS-CA), Director or Common Interface (if fitted) before the stream is routed to the output.

  1. From the Services page, click Add service then select Receiver. A new window displays:

  2. Configure the following parameters:

    • Enter a suitable Name for the service.
    • Select the Type to be TS Passthrough.
    • Select the Server to be Receiver to create and configure the service.
  3. Click to edit the service.

  4. See Configure the input for how to set up in the input interface to receive the incoming transport stream.

  5. See Configure the decryption for how to decrypt any of the incoming service in the transport stream.

    A maximum of 15 Transport stream services can be decrypted.

  6. Select the Output tab from the Parameters window. A new window displays:

  7. Configure the following parameters:

    • Select the Network interface for the outgoing transport stream.
    • Enter a Stream address (Multicast IP address) and UDP port number for the outgoing transport stream.
    • Enter the Time to live for the outgoing data packets.