> 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.

# Limitations

This page lists known limitations for BNR NIM.

## Audio Format

- BNR supports mono PCM L24 audio.
- Use `v2-48k` for 48 kHz audio and `v2-16k` for 16 kHz audio.
- Input and output sample rates must match the selected model variant.

## Stream Count

- A single BNR NIM pod processes one audio input stream and produces one audio output stream.
- For multiple channels or independent speakers, deploy multiple BNR NIM instances or downmix upstream as appropriate.

## Networking

- SMPTE ST 2110 traffic requires a correctly configured high-speed Multus network attachment.
- `NetworkAttachmentDefinition` resources are namespace-scoped and must be present in the namespace where the chart is deployed.
- Rivermax licensing and compatible NIC configuration are required for ST 2110 operation.

## OpenShift

- The pod security configuration requires Linux capabilities used by Rivermax and the media stack.
- Grant an appropriate Security Context Constraint before deployment.

## Scheduler

- The chart defaults assume a topology-aware scheduler. If the cluster does not provide `topo-aware-scheduler`, override the scheduler value before deployment.