PID Mapping Options in ZEN Master
0 min
The Zixi Platform offers two primary PID map options:
- Designated PID Map Input: Visible on the broadcaster as a PID Map input.
- Source-Level PID Map: Embedded in the source and hidden within the broadcaster input.
ZEN Master orchestration provides multiple methods to handle PID mapping, each utilizing these options differently:
- PID Map Source: Creates a visible PID Map input parallel to the original Broadcaster input. Functions like a standard ZEN Master source and can be added to Sources/Channels for use.
- Broadcaster Push: Generates a PID Map on the receive side, embedded within the Broadcaster input and not visible. Bandwidth at the receive side reflects the full payload for billing and processing. [Not appropriate for customers trying to save intercluster bandwidth with PID Map.]
- Intercluster Pull: PID Map is created on the receive side. The PID Mapy is built into Broadcaster input and not visible. Bandwidth at receive side will still show full for billing/processing purposes even though PID Map is happening. [Not appropriate for customers trying to save intercluster bandwidth with PID Map.]
- Failover Source: Produces a visible Broadcaster PID Map input parallel to the failover source on the Broadcaster. This input is automatically used by ZEN Master for all Targets connected to that source through a Passthrough Channel.
- ZEN Master Targets: Will create a visible broadcaster PID Map input parallel to the requested Source when a Target is actively requested or delivered. The same PID Map will be automatically used by any future target created with that PID Mapping Profile applied delivering that Source.
- ZEN Master Sources with PID Map Support: PID Map is built into broadcaster input and not visible. Input bandwidth will reflect total payload of source entering broadcaster and not PID Mapped bitrate.