T-VIPS CP525 cMux, User Manual

Page: 222 / 292

222 WEB Interface
CP525 cMux User’s Manual Rev. 5.20.12 (3944) ID: um_tsmux
Here the ’Port Index’ starts at index 0 for ASI 1, 8 for IP 1 and 24 for Switch 1. The ’Service
Index’ starts at 0 for the first service transmitted from each Input. ’Service Index’ increases by
1 for each service transmitted from that input. The ’Component Index’ starts at 0 for each new
Input or Service. ’Component Index’ increases by 1 for each component of the same type.
The default configuration has ’Port Offset’, ’Service offset’ and ’Component Index’ set to zero.
This will allow back-to-back remapping of PIDs between each port. However, in the case where
a service would be added for example from the first port at a later stage, the PIDs from the
succeeding ports would have to be remapped once more. To avoid this issue and to reserve
space between each port, ’Port Offset’ and ’Service offset’ should be set to suitable values.
An example with settings and values are given below:
Input ports: ASI 2 (Port Index 1), ASI 4 (Port Index 3). Assuming 2 services with 1 Video PID
each, on each input.
Auto-remap component PIDs: Always
Rule type: Video
Start PID: 512
Stop PID: 575
Port Offset: 4
Service Offset: 2
Component Offset: 1
The resulting PID remapping from ASI2 would be:
First video pid: 512 + (1 x 4) + (0 x 2) + (0 x 1) = 516 (Service 1)
Second video pid: 512 + (1 x 4) + (1 x 2) + (0 x 1) = 518 (Service 2)
The resulting PID remapping from ASI4 would be:
First video pid: 512 + (3 x 4) + (0 x 2) + (0 x 1) = 524 (Service 1)
Second video pid: 512 + (3 x 4) + (1 x 2) + (0 x 1) = 526 (Service 2)
The end result will be four video PIDs transmitted by the multiplexer at the following values:
Video PID 516 (ASI2 - Service 1)
Video PID 518 (ASI2 - Service 2)
Video PID 524 (ASI4 - Service 1)
Video PID 526 (ASI4 - Service 2)
In the case where the amount of remapped PIDs exceed the configured range defined by the rule
types, the multiplexer will try to keep the original PID values on the remaining un-remapped
PIDs. If this creates a PID conflict an alarm will appear on the multiplexer output.
Auto-remap component PIDs
This parameter controls enabling and disabling of automatic PID remapping. Three options
are available, “Off”, “Always” and “On Conflict”.
Parameter selection “Off” will disable automatic remapping, and the rule types will not be
processed or taken into consideration.
Parameter selection “Always” will always try to fulfil the configured remapping rules
specified, including handling of PID conflicts.
Parameter selection “On Conflicts” will only remap PIDs if PID conflicts are detected
during the multiplexing operation. In this case the first occurrence of the PID will remain at
original PID value while following occurrences will be remapped according to the specified
rules.
Keep last remap
If enabled and there is a change on the input signal(s), the last Auto-Remapped PID value