title: Crestron DM NVX — AV-over-IP Distribution description: Deep reference for Crestron DM NVX: encoder/decoder hardware, multicast architecture, switch configuration, XiO Cloud provisioning, bandwidth planning, and comparison with legacy DM. tags: [control-systems, crestron, dm-nvx, av-over-ip, video, 4k, multicast, igmp, vlan, qos, hdmi] created: 2026-05-05 status: current review_by: 2027-05-05

Crestron DM NVX — AV-over-IP Distribution

This note covers DM NVX hardware, networking, and deployment. For the Crestron platform overview, see control-systems/crestron-basics.

Crestron DM NVX (Network Video Extension) is Crestron's AV-over-IP platform for distributing 4K video, audio, USB, and control over standard 1GbE Ethernet infrastructure. NVX replaced Crestron's earlier DM (DigitalMedia) system — which used proprietary fiber or HDBaseT cabling between encoders, decoders, and matrix chassis — with a fully IP-based architecture where any encoder can reach any decoder on the same network without a dedicated matrix switcher. For new installations, NVX is the default Crestron video distribution platform.

NVX Architecture

Encoder/Decoder Model

NVX operates on an encode/decode model rather than a matrix switcher model. Each source (laptop, cable box, PC) connects to an encoder that compresses the video signal and streams it over the network as a multicast IP stream. Each display connects to a decoder that joins the multicast group for the desired stream and outputs the video signal to the display.

Routing changes are made by changing which multicast stream the decoder subscribes to — not by reconfiguring physical switch ports. A decoder in Room 201 that normally shows Stream A (the lobby camera) can be instantly switched to Stream B (the conference PC) by updating its subscription, with no physical cabling changes.

This architecture provides several advantages over legacy matrix switchers:

• Scalable routing — Adding a 25th source requires one NVX encoder; a legacy matrix would require a larger chassis
• Flexible topology — Encoders and decoders connect wherever there is a network port; rooms can be added without running new video cabling
• Redundancy — Multiple decoders can subscribe to the same encoder stream simultaneously (one-to-many)
• Remote deployment — NVX endpoints across buildings, floors, or campuses share the same routing fabric

Video Compression

NVX uses Crestron's proprietary compression codec operating at near-visually-lossless quality. Key performance specs:

The < 170 µs latency is a key differentiator: at this level, no perceptible lip-sync offset occurs, and interactive applications (touchscreen control, video conferencing) are unaffected. Compare with SDVoE at < 1 frame (< 16 ms) or compressed AV-over-IP solutions at 80–200 ms.

Hardware

Current NVX Lineup

NVX-360 is the preferred choice for conference rooms: a single unit at the table connects to both the room PC (encoding local content) and the room display (decoding remote content). One device per room end simplifies inventory and installation.

Physical Connections

Every NVX encoder and decoder includes:

• HDMI — Input (encoder) or output (decoder); HDMI 2.0 on 4K models
• 1GbE Ethernet — Primary network connection for AV stream
• USB — USB 2.0 extension (keyboard, mouse, webcam routing over IP); requires matching USB host on far end
• RS-232 — Serial control pass-through (display control commands can traverse the network alongside video)
• IR — IR pass-through for legacy infrared control
• Audio — Analog audio I/O (line level) for embedding/de-embedding audio independent of HDMI
• PoE — NVX endpoints are PoE-powered (IEEE 802.3at/PoE+); no separate power supply required. Power budget: approximately 15-25W per endpoint depending on model

The PoE requirement is significant for switch specification: a 24-port access switch feeding 20 NVX endpoints must provide 24-port PoE+ capacity (typically 370–740W PoE budget), in addition to 10GbE uplinks. Size the switch PoE budget before specifying.

HDMI/HDCP Handling

NVX supports HDCP 2.2 throughout the chain. For HDCP-protected content (streaming media, Blu-ray) to route successfully, every component in the signal path must support the appropriate HDCP version. Common HDCP failure mode: a 4K HDCP 2.2 source routed through an encoder that handles HDCP 2.2, but a decoder connected to an older display that only supports HDCP 1.4. The decoder will downscale or refuse to output. Verify HDCP support at both the encoder and the decoder/display combination during design.

EDID management: NVX encoders handle EDID (Extended Display Identification Data) by presenting a fixed EDID to the source. Without EDID management, a laptop connected to an NVX encoder might negotiate a 4K resolution that the destination display does not support. Configure the encoder's EDID to reflect the lowest-common-denominator display in the system, or use Crestron's per-encoder EDID configuration to match the intended destination.

Network Configuration

NVX requires specific network infrastructure to function reliably. This is the area most commonly underspecified, leading to intermittent dropouts and failed deployments.

VLAN Design

NVX endpoints must be on a dedicated AV VLAN, isolated from general IT traffic. Recommended design:

All NVX endpoints on VLAN 100 communicate without inter-VLAN routing, which simplifies multicast handling. The control processor on VLAN 101 communicates with NVX endpoints via inter-VLAN routing (Layer 3) — the processor uses the NVX REST API for routing commands, not multicast.

IGMP Snooping

NVX video streams are multicast. Without IGMP snooping, a single NVX encoder stream (up to 950 Mbps) floods every port on the VLAN, saturating links to all decoders and immediately degrading or eliminating video on all streams.

IGMP snooping configuration:

• Enable IGMP snooping at the VLAN level on every switch in the NVX VLAN
• Enable an IGMP querier on at least one switch per VLAN (or the router interface for that VLAN)
• Verify with switch show commands that IGMP groups are registered — each active decoder should show a registered IGMP group for its subscribed stream

IGMP fast-leave: Enable IGMP fast-leave (immediate leave) on NVX switch ports. Without fast-leave, when a decoder stops subscribing to a stream, the switch waits for the IGMP query interval (typically 125 seconds) before stopping multicast delivery. During source switching, this causes up to 2-minute delays before the old stream stops. With fast-leave enabled, unsubscription is processed immediately.

QoS — DSCP Marking

NVX encoders mark outgoing video packets with DSCP 34 (AF41). Configure all switches in the NVX path to map DSCP 34 to a high-priority queue — second only to voice traffic (DSCP 46/EF).

# Cisco IOS example
mls qos dscp-mutation NVX_policy
interface GigabitEthernet1/0/1
 mls qos trust dscp

Without QoS, bursty office traffic (file copies, video calls, backup jobs) can compete with NVX multicast streams at the switch queue level, causing frame drops and visible artifacts. QoS is non-optional in shared-infrastructure deployments.

Bandwidth Planning

Critical insight: Each NVX stream is nearly 1GbE by itself. A 24-port access switch with 20 NVX encoders pushing simultaneous streams requires 20 Gbps of uplink bandwidth — minimum two 10GbE uplinks, with LACP bonding for failover. Budget switch-to-core uplinks before finalizing the NVX count.

Multicast reduces downstream bandwidth: 10 decoders subscribing to the same encoder stream use no more switch bandwidth than 1 decoder. The bandwidth is consumed once at the encoder's switch port, then multicast to all subscribers on that VLAN. This favors designs where many rooms display the same content (digital signage, lobby displays, overflow rooms).

Static IP Assignment

All NVX endpoints should be assigned static IPs. DHCP-addressed endpoints work initially but become unreliable when leases renew, as the Crestron control system stores endpoint IP addresses for routing commands. Changing IPs break the control program's ability to address specific decoders. Use DHCP reservations (MAC-to-IP binding on the DHCP server) as an acceptable alternative to manual static addressing — this provides the benefits of centralized IP management while ensuring stability.

NVX Control and Routing via Crestron

Control Processor Integration

The Crestron control processor routes NVX video by sending API commands to encoder and decoder endpoints. NVX endpoints expose a REST API over HTTP; the Crestron SIMPL program (or SIMPL# Pro code) sends routing commands:

# Set NVX decoder to subscribe to a specific encoder stream
PUT http://[decoder-ip]/Device/Streams/ActiveStream
Body: { "StreamLocation": "239.255.255.1" }  # Encoder's multicast group

In practice, SIMPL Windows programs use the Crestron NVX SIMPL module, which abstracts the REST API into familiar join signals. SIMPL# Pro programs use HttpClient to call the REST API directly.

XiO Cloud routing: In XiO Cloud-managed deployments, routing can be configured through the cloud interface without writing API code — useful for initial commissioning and remote troubleshooting.

Routing from SIMPL

The NVX SIMPL module exposes:

• Route[n] digital inputs — switch decoder n to source n
• Stream_Location$ serial input — set multicast address directly
• Online_FB digital output — decoder connected status
• Resolution_FB$ serial output — current output resolution
• HDCP_Status_FB digital output — content protection active

Wire Route[1] through Route[n] to touchpanel joins in the source-select matrix. Label them Source_PC, Source_Laptop, Source_Cable and connect to the corresponding encoder multicast addresses.

NVX vs Legacy DM

When legacy DM is still appropriate: Service work on existing installations. Systems where structured cabling (Cat6a runs to all AV locations) is already in place and the network infrastructure cannot support the NVX bandwidth requirements. Small rooms with guaranteed point-to-point routing needs where NVX's multicast complexity is unwarranted.

DM Lite: Crestron's DM Lite products (HD-MD series) use HDBaseT over Cat6 for point-to-point distribution. These are not NVX — they use hardware matrix switchers or standalone extenders, not IP multicast. DM Lite is positioned for small rooms (1-4 sources) where an IP-based system is overkill but a simple HDMI extender lacks the control and monitoring features of a managed Crestron system.

Common Pitfalls

• IGMP snooping disabled at VLAN level. The switch's global IGMP snooping setting may be enabled, but if it is not enabled on the specific VLAN carrying NVX traffic, multicast floods the VLAN. Verify IGMP snooping is configured at the VLAN level using show ip igmp snooping vlan [id] (Cisco) or equivalent. This is the #1 cause of NVX deployments where video works in testing but fails under load.

• Insufficient switch uplink bandwidth. A 24-port 1GbE access switch with 1GbE uplinks connecting 10 NVX encoders cannot pass more than 1 Gbps upstream — 9 out of 10 encoder streams are dropped or severely throttled. Size uplinks at commissioning: count active encoders, multiply by 950 Mbps, add 20% headroom, provision 10GbE uplinks accordingly.

• HDCP version mismatch at decoder/display interface. A 4K source successfully encodes and streams, but the decoder outputs black screen or a lower resolution. Check the decoder's HDCP negotiation status via the REST API or XiO Cloud. If the display only supports HDCP 1.4 and the source is HDCP 2.2, downconversion or content refusal occurs. Specify display HDCP 2.2 support for any installation distributing protected 4K content.

• NVX endpoints on DHCP with lease renewal. A decoder works for 24 hours, then loses connectivity as its DHCP lease renews with a new IP. The control processor's routing commands go to the old IP. Assign static IPs or DHCP reservations to all NVX endpoints before commissioning.

• USB extension oversubscribed. Each NVX encoder/decoder pair can extend one USB peripheral path. In a conferencing room with a webcam, a speakerphone, and a room control USB hub, only one USB device can traverse the NVX link at a time without additional USB extension hardware. Design USB extension separately from video routing; plan for USB-over-IP or dedicated USB extenders for multi-device scenarios.

• QoS not configured on uplinks. QoS is configured on access ports but not on the 10GbE uplinks between access and distribution switches. NVX packets lose their priority treatment on the uplinks and compete with bulk transfers. Configure DSCP trust and queuing on all switch interfaces in the NVX path — not just access port connections to endpoints.