This document describes how the Cisco Digital Content Manager (DCM) responds when you configure the same value for a Transport Stream (TS) component and a service component.
Identical PID Example Scenario
This section provides some examples that illustrate a scenario where an identical Packet Identifier (PID) is configured for a TS component and a service component.
This image shows UNREF PIDs 555 on a transportstream:
The TS component view shows this PID, and you can give this PID a new value:
Then, you create a rule and use the same PID for an Elementary Stream (ES):
After this action, the PID appears in red in the component tracking rules:
Cisco DCM Response
You can specify the TS component rules with a specific input PID and output PID. At the same time, you can have a service component rule that matches the same input PID. The TS component rule in this case has the highest priority and receives the requested output PID.
A new feature that is available in Version 14 of the Cisco DCM allows the GUI to display this output PID colored red in the service component rules in order to indicate that there are two rules specified for the same component and that there might be a conflict as a consequence.
If the PID appears in the service it also is no longer shown as an unreferenced PID in the tree view (TS component) since the PID is referenced from the service Program Map Table (PMT).