PID Mapping Options in ZEN Master

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 channel 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 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