Introduction
•
Multiplexer output transport streams can be created from any services or
components carried on any input transport stream. A single component can also
be used in multiple output transport streams. Each multiplexer engine receives
PSI/SI/PSIP table data via nCompass Control and manages the carousel
insertion of that data into the associated transport stream output.
•
A maximum of 8192 PIDs for each multiplexer is supported.
•
The dynamic PID tracking of incoming services is supported.
•
PID filtering is supported to allow the removal of unwanted PIDs.
•
PID remapping is supported to allow a component received on one PID to be
output on a different PID.
•
Missing incoming PIDs can be detected and used to initiate appropriate alarms
to nCompass Control. Detected PIDs can also be excluded from the monitoring.
•
The MX8400 can operate in both active and redundant modes. Synchronization
of MX8400 configurations is automatically maintained for redundant mode of
operation.
•
The MX8400 provides Program Level Redundancy by sourcing any transport
streams missing from the primary network from the secondary network without
affecting any other active service. Refer to
Annex E, Redundancy Modes
for
further details.
•
The MX8400 supports dual redundant 10/100 Ethernet interfaces for system
control and for CA data.
•
The MX8400 supports a single fixed power supply(100-240 V AC)
•
The MX8400 supports an Alarm relay connection.
1.3.2.1
Program Specific Information Generator (PSIG)
PSIG (described by ETSI TS 103 197, DVB: High-end Implementation of DVB
Simulcrypt) is supported by this release of the MX8400.
The PSI Generator (PSIG) is defined as the head-end process(es) responsible for
generating MPEG-2 PSI (Program Specific Information) tables.
Note:
Please refer to
Annex I PSIG Support
for further information.
1.3.2.2
Program Clock Reference (PCR)
•
Multiplexing non-time stamped components (e.g. DVB Subtitles or MHEG Data)
between incoming services is supported.
•
The MX8400 supports mixing time stamped components that reference valid
PCR PIDs from different remultiplexed feeds/incoming services. This is normally
only supported with feeds that use a single PCR reference in the incoming
transport stream or single PCR based Encoder's inputs.
2/1553-FGC 101 1014 Uen B
1-7
Summary of Contents for MX8400
Page 1: ...MX8400 Multiplexer Software Version 5 2 0 and later REFERENCE GUIDE 2 1553 FGC 101 1014 Uen B...
Page 26: ...Installing and Powering Up 2 1553 FGC 101 1014 Uen B 2 4 BLANK...
Page 94: ...Operating the Multiplexer using nCompass Control 2 1553 FGC 101 1014 Uen B 4 18 BLANK...
Page 96: ...Preventive Maintenance and Fault finding 2 1553 FGC 101 1014 Uen B 5 2 BLANK...
Page 146: ...Technical Specification 2 1553 FGC 101 1014 Uen B B 20 BLANK...
Page 148: ...Static Parameters 2 1553 FGC 101 1014 Uen B C 2 BLANK...
Page 186: ...Redundancy Modes 2 1553 FGC 101 1014 Uen B E 2 BLANK...
Page 192: ...IP Protocols 2 1553 FGC 101 1014 Uen B F 2 BLANK...
Page 196: ...IP Protocols 2 1553 FGC 101 1014 Uen B F 6 Figure F 3 Editing Stack Download Ports...
Page 198: ...ProMPEG FEC Support for IP Streaming 2 1553 FGC 101 1014 Uen B G 2 BLANK...
Page 204: ...Setting up the SFN Functionality 2 1553 FGC 101 1014 Uen B H 2 BLANK...
Page 212: ...Setting up the SFN Functionality 2 1553 FGC 101 1014 Uen B H 10 BLANK...
Page 214: ...PSIG Support 2 1553 FGC 101 1014 Uen B I 2 BLANK...
Page 220: ...BISS Support 2 1553 FGC 101 1014 Uen B J 2 BLANK...
