Is this page helpful?

Verification#

After the sample chart is deployed, the end-to-end demo can be verified by confirming that the pipeline is healthy and that audio output from the receiver can be heard in VLC (or another SRT client). A preview stream is exposed by the receiver over SRT; the cluster’s node address and the service or NodePort mapped to the receiver’s SRT port should be taken from your Helm values.

Open an SRT Stream in VLC#

The following steps are performed:

  1. Start VLC media player.

  2. Select Media → Open Network Stream (or Open Network).

  3. In the URL field, enter an SRT URL in the following form:

    srt://<node-of-pod>:<port>

    • <node-of-pod> is the Kubernetes or OpenShift node address on which the SRT listener is exposed.

    • <port> is the mapped port for the receiver’s SRT preview.

Obtain a node IP address for the SRT URL as follows:

oc get node -o wide

On plain Kubernetes, use kubectl get node -o wide instead of oc.

The INTERNAL-IP (or another address that is routable from the machine on which VLC is run) is used together with the external or NodePort value configured for the receiver’s SRT preview.

Example

srt://<internal-ip>:<external-srt-port>

Follow the same address pattern as in View Output via SRT for your release and environment.

After playback is established, the preview should be similar to the following image. The enhanced audio waveform is visible in the VLC audio visualizer.

VLC preview with Studio Voice enhanced audio

NMOS Workflow#

When the Helm charts are deployed with NMOS enabled, the sender, Studio Voice NIM service, and receiver are registered with the NMOS registry. In the NMOS Connection Manager UI, these components are listed under Available.

Each node is dragged from Available into the workspace; outputs are then connected to inputs so that media is routed sender → NIM → receiver in the order required by the deployment. The reference wiring is shown in the following diagram.

Connect receivers to the NIM before the sender is connected, so that audio is not accumulated in receiver queues. For more information, refer to NMOS Mode and Recommended: Two-Phase Deploy.

NMOS Connection Manager workspace with sender, NIM, and receiver connections

See Also#