End-to-End Demo Chart
Overview
The nvidia-active-speaker-detection-h4m-sample Helm chart deploys a complete Active Speaker Detection demo pipeline on Holoscan for Media. This includes:
- Sender pipeline.
- Active Speaker Detection NIM service (
nvidia-active-speaker-detection-h4m-service). - Receiver pipeline (SMPTE ST 2110 or NMOS).
- SRT output for preview.
The NIM analyzes live video and audio streams to identify the active speaker in a multi-person scene. Detection results are transmitted as bounding box metadata via SMPTE ST 2110-40 ancillary data.
Installation
Prerequisites
Complete all prerequisite steps (Rivermax license, image pull and model pull secrets, high-speed network attachment) before running helm install. For details, refer to Getting Started.
Pull the Chart
If not already done, add the Helm repository and pull the chart:
For the full repository setup, refer to Pull Helm Charts.
Helm Installation
The chart includes a default values.yaml. For SMPTE ST 2110 static or NMOS pipelines, copy the configuration from Starter Configuration Files into values-st2110.yaml or values-nmos.yaml, adjust fields, and run the matching install command.
The default values.yaml ships with example values for cluster-specific fields such as node selector (example-gpu-node), image pull secret, network name, and scheduler. You must update these values to match your cluster before deploying. The easiest approach is to use the global overrides so that each value is specified once for all components (sender, receiver, and NIM service). For details, refer to Global Overrides.
Minimal deployment using global overrides (NMOS mode, 1080p):
Alternatively, set values per component when the sender, receiver, and NIM service run on different nodes or use different pull secrets:
For all available Helm values, refer to the Configuration Reference.
Recommended: Two-Phase Deploy
First, deploy the receiver and NIM service. When the pipeline is ready, enable the sender. This procedure prevents frames from accumulating in receiver queues before the NIM is ready.
On Red Hat OpenShift, replace kubectl with oc.
A rollout status timeout is not a failure; it means the pod did not become ready within the allotted time. The NIM pod might still be pulling its image or initializing. If a timeout occurs, check the pod state before taking action:
Look for Pulling image in the events (normal—wait longer) or CrashLoopBackOff / ErrImagePull (actionable: check secrets and node resources).
After installation, verify all pods are running:
Confirm that the sender, NIM service, and receiver pods all show READY 1/1 before continuing.
Sender Sample Media
Input Media Files
The sender expects an MPEG Transport Stream (.ts) file containing video and audio streams for active speaker detection.
Stream Composition
Each input .ts file must contain the following streams:
- Video stream: Source video with one or more visible speakers.
- Audio streams: One mono audio track per speaker (for example, two speakers require two audio tracks). Each audio stream should contain only a single speaker’s audio.
Codecs
- Video codec: H.264
- Audio codec: Opus, 48 kHz, mono
Bundled Sample Files
The sender container includes a sample .ts file:
/workspace/assets/sample_asset.ts
Use the same resolution and frame rate for the sender, NIM service (nvidia-active-speaker-detection-h4m-service), and receiver.
Each input audio stream must contain only a single speaker’s audio. During silence, audio samples must be zero. If background noise is present, enable audio thresholding via useAudioThresholdToDetectActiveAudioStream and audioThresholdDb in the pipeline configuration. For details, refer to Configuration Reference.
Receiver Type
The receiver supports two operating modes, controlled by receiver.receiverType:
Example of switching the receiver to video mode:
In ancillary mode, the ancillaryInputParams section is used. In video mode, the videoInputParams section is used instead.
Starter Configuration Files
Copy the appropriate configuration into values-st2110.yaml or values-nmos.yaml, adjust fields for your environment, and pass it to helm upgrade --install with -f.
For a full reference of all Helm keys and pipeline tuning parameters, refer to the Configuration Reference.
SMPTE ST 2110 Configuration — Static (values-st2110.yaml)
NMOS Configuration (values-nmos.yaml)
On Holoscan for Media clusters, the NMOS Connection Manager web UI is typically reached from a browser on the cluster network. For remote graphical access, refer to Chrome Remote Desktop in Getting Started.
In NMOS mode, connect receivers to the NIM service before connecting the sender via the NMOS Connection Manager UI. In SMPTE ST 2110 mode (static), ensure that the “sender → NIM service → receiver IP address and port” chain is consistent across all values.
Install
SMPTE ST 2110 (static):
NMOS is enabled by default. To deploy in fixed SMPTE ST 2110 mode (static), append the following:
NMOS:
View Receiver Output
The receiver logs the parsed ancillary payload as JSON. To view it, run the following command:
A typical log line looks like the following:
View Output via SRT
Get the internal IP of the node:
The SRT output is on port 30889 by default. To view the stream in VLC, refer to Open an SRT Stream in VLC.
Disabling Components
Individual pipeline components can be disabled during helm install or helm upgrade without removing the release:
Only the selected component stops; the rest of the pipeline continues to run.
Verify
Verify configured Helm values:
On Red Hat OpenShift, replace kubectl with oc. For log access, refer to Observability.
Uninstall
End-to-End Verification
- Create
values-st2110.yamlorvalues-nmos.yamlfrom Starter Configuration Files and run the matching Install command. - Confirm all pods show
READY 1/1withkubectl get pods. - Open the SRT preview; refer to View Output via SRT. For VLC steps, NMOS wiring, and screenshots, refer to Verification.
- Run
helm uninstall nvidia-asd-h4m-sample.
For troubleshooting, refer to Advanced Usage.