> This page is for NVIDIA Background Noise Removal on Holoscan for Media, version 2.0.0 (Latest) (default).
> For other versions, use one of these documentation indexes:
> - 2.0.0 (Latest) (default): https://docs.nvidia.com/nim/maxine/bnr-h4m/2.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.

# Overview

NVIDIA Background Noise Removal (BNR) NIM removes unwanted background noise from speech and improves intelligibility in noisy live-production environments. The NIM ingests a single PCM audio stream over SMPTE ST 2110-30, applies real-time denoising, and publishes enhanced audio over SMPTE ST 2110-30 for downstream broadcast equipment.

This NIM is designed for live broadcast and production workflows that ingest and egress uncompressed audio over SMPTE ST 2110 using [NVIDIA Rivermax](https://developer.nvidia.com/networking/rivermax-getting-started). It is deployed with Helm charts on a [Holoscan for Media](https://developer.nvidia.com/holoscan-for-media) cluster and can optionally be managed through a Kubernetes operator.

## Architecture

The BNR NIM is built on NVIDIA's software platform:

- [**Holoscan for Media:**](https://developer.nvidia.com/holoscan-for-media) Media platform for SMPTE ST 2110-oriented live pipelines and Kubernetes-native orchestration.
- [**NVIDIA Rivermax:**](https://developer.nvidia.com/networking/rivermax-getting-started) GPU-accelerated SMPTE ST 2110 and RTP ingest and egress.
- **CUDA:** GPU-accelerated processing.
- **TensorRT:** Optimized neural network inference.
- **Triton Inference Server:** Local model execution and metrics.

## Processing Flow

The NIM performs the following actions in sequence:

1. Receives uncompressed mono audio via SMPTE ST 2110-30 over the high-speed network interface.
2. Selects the BNR denoiser variant from `model.type` (`v2-48k` or `v2-16k`).
3. Runs inference through Triton Inference Server inside the pod.
4. Applies the configured `intensityRatio` (from `0.0` to `1.0`).
5. Emits enhanced audio via SMPTE ST 2110-30.

### Logical Pipeline

```text
Sender → BNR NIM → Receiver
```

| Piece | Role |
|-------|------|
| Sender | Example workload: TS file to ST 2110-30 audio (demo chart). |
| BNR NIM | Background noise removal and, when NMOS is enabled, registration with an external NMOS registry; enhanced ST 2110-30 audio output. |
| Receiver | Consumes enhanced audio, optionally re-streams via SRT. |

**Operator variant:** Reconciles only the BNR NIM deployment and SDP ConfigMap from an `NvidiaBnrMediaFunction` custom resource.

## Inputs and Outputs

| Direction | Stream Type | Transport | Format | Supported Configurations |
|-----------|-------------|-----------|--------|--------------------------|
| Input | Audio | [SMPTE ST 2110-30](https://docs.nvidia.com/holoscan-for-media/latest/user-guide/getting-help/rivermax-st-2110.html) | PCM L24, mono | 48 kHz with `v2-48k`; 16 kHz with `v2-16k`. |
| Output | Audio | [SMPTE ST 2110-30](https://docs.nvidia.com/holoscan-for-media/latest/user-guide/getting-help/rivermax-st-2110.html) | PCM L24, mono | Same sample rate and channel count as input. |

<Note>
BNR expects a single mono speech stream per input session. For multi-channel mixes, downmix to mono on the sender or instantiate one NIM per speaker channel.
</Note>

## Deployment

BNR NIM supports three deployment patterns:

| Deployment Option | Description |
|-------------------|-------------|
| **NIM service chart** | Deploys the BNR NIM as a standalone Kubernetes deployment for integration into a custom media pipeline. |
| **Kubernetes operator** | Manages BNR NIM workloads through a `NvidiaBnrMediaFunction` custom resource. Suitable for declarative, production-grade management. |
| **End-to-end demo chart** | Deploys a complete demo pipeline: sender, BNR NIM service, and receiver. Recommended for initial evaluation. |

For installation instructions, refer to [Installation](/nim/maxine/bnr-h4m/installation).

## Supported Operating Modes

### ST 2110 Static Mode

Media streams use fixed multicast IP addresses, ports, and session names. Configure the sender output, BNR input/output, and receiver input so the IP and port chain is consistent.

### NMOS Mode

Devices and streams are registered and connected using AMWA NMOS IS-04 and IS-05. This mode simplifies setup by moving transport negotiation into the NMOS Connection Manager UI.

## See Also

- [Holoscan for Media](https://docs.nvidia.com/holoscan-for-media/latest/index.html) documentation.
- [System Requirements](https://docs.nvidia.com/holoscan-for-media/latest/user-guide/requirements/index.html) for Holoscan for Media.
- [Rivermax](https://docs.nvidia.com/holoscan-for-media/latest/user-guide/getting-help/rivermax-st-2110.html) and ST 2110 for Holoscan for Media.
- [Known Limitations](/nim/maxine/bnr-h4m/limitations).