End-to-End Demo Chart
Overview
The nvidia-studio-voice-h4m-sample Helm chart deploys a complete Studio Voice demo pipeline on Holoscan for Media. This includes:
- Sender pipeline.
- Studio Voice NIM service (
nvidia-studio-voice-h4m-service). - Receiver pipeline (SMPTE ST 2110 or NMOS).
- SRT output for preview.
The Studio Voice NIM processes incoming audio streams and performs real-time AI-based speech enhancement (noise suppression, dereverberation, restoration of clarity). Enhanced audio is transmitted via ST 2110-30.
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. Before deploying, you must update these fields to match your cluster. 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):
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 audio 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 an audio stream for Studio Voice enhancement.
Codecs
- Audio codec: Opus, 48 kHz, mono.
Bundled Sample Files
The sender container includes a sample .ts file:
/workspace/assets/studio_voice_48k_2_looped_10min.ts
Using a Custom Input Asset
To test with your own audio, upload a .ts file to a PersistentVolumeClaim (PVC) and enable the built-in PVC mount on the sender:
The PVC is mounted at /workspace/assets inside the sender pod, overlaying the default bundled assets.
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)
In NMOS mode, the transport parameters (multicast IP address, port, subnet) are negotiated dynamically by the NMOS Connection Manager over IS-04 and IS-05, so the preceding NIM service block needs only sessionName for each input/output. The values are discovered at runtime.
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 Studio Voice NIM before connecting the sender via the NMOS Connection Manager UI. In SMPTE ST 2110 mode (static), ensure that the “sender → NIM → 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 Output via SRT
Get the internal IP addressof the node:
The SRT output is on port 32090 by default. Open the stream in VLC or ffplay:
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
The *-model-cache and *-nim-logs PVCs carry helm.sh/resource-policy: keep and are not removed by helm uninstall. This preserves the cached model across reinstalls; clean them up manually when no longer needed:
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 studio-voice-h4m-sample.
For troubleshooting, refer to Advanced Usage.