Broadcast Contribution: A Practical Commissioning Checklist

Define the handover at each end

A contribution link is ready when the receiving team can use the pictures and sound in its intended workflow. A network connection or a decoder status marked “locked” is only part of that result. Start by agreeing exactly what leaves the source and what must arrive at the destination.

Name the source device, encoder, network handover, receiver and downstream equipment. Identify who owns each part of the chain and who can change its settings. This avoids troubleshooting a network fault when the actual mismatch is at a video or audio interface.

Build the compatibility matrix

Record exact values rather than writing only “HD”, “4K” or “IP”. When the downstream workflow requires captions, ancillary data, reference signals or particular timing behaviour, list them explicitly and verify support for the selected model and firmware.

Separate media direction from connection setup

In SRT caller/listener operation, the caller initiates the connection to the listener. That role does not by itself determine which endpoint sends the video. The SRT protocol documentation describes the connection handshake.

Draw the media direction and the connection roles separately. Confirm that the agreed port is reachable, that any address translation is understood, and that the listener is available before beginning the test. Record the actual stream identifier and encryption configuration where used.

On RTP links, sequence numbers and timestamps help the receiver interpret the stream. RTP alone does not guarantee delivery, reserve bandwidth or provide a packet-recovery service. Assess the network and any additional protection required by the selected equipment. See the RTP specification, RFC 3550.

Commission in stages

1. Confirm the source. Check the actual output format with appropriate monitoring equipment. Verify embedded audio channel assignments.
2. Build a local loop. Connect the intended encoder and receiver on a controlled network. Save the working settings before adding the external path.
3. Add the contribution network. Observe stream rate, network errors and recovery behaviour while watching and listening at the destination.
4. Check the downstream handover. Confirm the output on the production equipment itself, including the required video timing and audio mapping.

If the result fails, return to the last working stage and change one variable. Keep a known-good source and receiver configuration available so that troubleshooting does not depend on several unverified settings at once.

Make picture, sound and recovery part of acceptance

Use a test sequence that includes motion, fine detail, dark areas and transitions. Listen to every required audio channel. Check lip synchronisation against a suitable visual and audible event, using the same measurement method for all configurations.

Agree the required test duration and representative network load with the operator. Log interruptions, format changes and alarms. In a controlled test, restart a source or interrupt the link and record whether service resumes automatically and what the operator sees during recovery.

If redundancy is required, test the planned switchover with the actual system. Document whether a disturbance occurs; the presence of a backup path does not establish a seamless changeover.

Hand over a configuration that can be reproduced

The handover pack should include the compatibility matrix, a connection drawing, device and firmware versions, saved configurations, network ownership, acceptance results and the recovery procedure. Store credentials separately with the authorised operator.

Keep the scope clear: a receiver, an encoder, an audio receiver and an ASI/IP gateway serve different stages of a chain. Select the needed function first, then confirm the exact model’s supported inputs, outputs and stream formats. A familiar protocol name does not replace that compatibility check.

Practical questions