> This page is for NVIDIA LipSync on Holoscan for Media, version 1.0.0 (Latest) (default).
> For other versions, use one of these documentation indexes:
> - 1.0.0 (Latest) (default): https://docs.nvidia.com/nim/maxine/lipsync-h4m/1.0.0/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nim/maxine/llms.txt.

# Verification

After the sample chart is deployed, the end-to-end demo can be verified by confirming that the pipeline is healthy and that video output from the receiver can be viewed 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:

   ```text
   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 (or the sender preview, if that path is being verified).

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

```bash
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**

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

Follow the same address pattern as in [View Output via SRT](/nim/maxine/lipsync-h4m/installation/lipsync-h4m-sample#view-output-via-srt) for your release and environment.

After playback is established, the preview should be similar to the following image.

![VLC preview of LipSync receiver SRT output](/nim/maxine/_fern-files/maxine-nim.docs.buildwithfern.com/188cf4b3a2d48f26cab9a1453d06a4b1aaf877bab77abbf8a2cf55801cb0e1cd/pages/lipsync-h4m/images/lipsync_vlc.svg)

---

## NMOS Workflow

When the Helm charts are deployed with NMOS enabled, the sender, LipSync 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 the receiver *first* by establishing sender audio and LipSync NIM output to receiver. After the receiver connection is in place, connect the sender audio and video streams to the LipSync NIM. For more information, refer to [Limitations and Known Behaviors](/nim/maxine/lipsync-h4m/limitations-and-known-behaviors) and [End-to-End Demo Chart Installation](/nim/maxine/lipsync-h4m/installation/lipsync-h4m-sample).

![NMOS Connection Manager workspace with sender, LipSync NIM, and receiver connections](/nim/maxine/_fern-files/maxine-nim.docs.buildwithfern.com/8d02ea644bf8d785d35db75e4089b3675dfbec7f01ab49ea3c8cac258be4fa0c/pages/lipsync-h4m/images/Lipsync_nmos.svg)

---

## See Also

- [End-to-End Demo Chart Installation](/nim/maxine/lipsync-h4m/installation/lipsync-h4m-sample): SRT port mapping and receiver settings.
- [Observability](/nim/maxine/lipsync-h4m/observability): Health checks and logs.