> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/nim/maxine/lipsync-h4m/1.0.0/configuration/llms.txt. # Configuration Reference Helm values, environment variables, and operator custom resource fields for LipSync on Holoscan for Media are organized across the following pages: | Page | Content | |------|---------| | [Common Helm Configuration](/nim/maxine/lipsync-h4m/configuration/common) | Generic values shared by all NIM service chart deployments: cluster/workload, NGC API key secret, PVCs, and NMOS. NUMA-aware `schedulerName`: [Getting Started](/nim/maxine/lipsync-h4m/getting-started#scheduler-requirements-for-numa-aware-clusters). | | [Pipeline Configuration](/nim/maxine/lipsync-h4m/configuration/pipeline) | LipSync NIM-specific values: model and ancillary options, video raster, audio format, SMPTE ST 2110 session wiring, and logging. | | [End-to-End Demo Chart Configuration](/nim/maxine/lipsync-h4m/configuration/demo-chart) | Sender and receiver Helm values for the `nvidia-lipsync-h4m-sample` chart. | | [Operator Configuration](/nim/maxine/lipsync-h4m/configuration/operator) | `nvidia-lipsync-h4m-operator` Helm chart values and `NvidiaLipsyncMediaFunction` custom resource fields. | When using the [End-to-End Demo Chart](/nim/maxine/lipsync-h4m/installation/lipsync-h4m-sample), NIM service keys live under `nvidia-lipsync-h4m-service.` in the values YAML, not at the top-level `sender` / `receiver` scope. ## Docs - [Common Helm Configuration](https://docs.nvidia.com/nim/maxine/lipsync-h4m/1.0.0/configuration/common.md) - [Pipeline Configuration](https://docs.nvidia.com/nim/maxine/lipsync-h4m/1.0.0/configuration/pipeline.md) - [End-to-End Demo Chart Configuration](https://docs.nvidia.com/nim/maxine/lipsync-h4m/1.0.0/configuration/demo-chart.md) - [Operator Configuration](https://docs.nvidia.com/nim/maxine/lipsync-h4m/1.0.0/configuration/operator.md)