NDI for DJ Streams — No More HDMI Cables

Every camera you add to a DJ stream has a hidden price tag: an HDMI cable, a capture card, a USB port, and ten minutes of debugging a signal that worked yesterday. Broadcast studios ran into the same wall years ago, and they solved it by sending video over the network instead of through cables. The technology is called NDI — and for a DJ rig, it quietly removes most of the hardware sitting between you and a professional-looking stream.

NDI, short for Network Device Interface, turns video and audio into ordinary network traffic. A camera, a laptop, or a phone broadcasts its signal onto your local network; any other device can pick it up. No capture card, no video cables, no driver roulette. It was launched by NewTek in 2015 with a royalty-free SDK, and it has since become the closest thing video production has to a universal standard.

This guide covers what NDI actually does, the gear you need (less than you'd think), a ten-minute setup in OBS, the bandwidth math that keeps it stable, and the DJ workflows where it shines — plus the places where it's the wrong tool.

What NDI Actually Does

The mechanics are simple. Every device with NDI support announces itself on the local network under a name you choose — CAM-Deck, OBS-Visuals, iPhone-Tom. Any other NDI device sees that name in a list and can receive the feed. Video, audio, and even an alpha channel for graphics with transparency arrive synchronised, with glass-to-glass latency specified at under 100 ms — effectively live for a music stream.

Because NDI is a protocol rather than a product, it's everywhere. PTZ cameras ship with it built in. VJ software like Resolume sends and receives it natively. vMix speaks it in every edition. And OBS Studio — the tool most DJs already stream with — gets full NDI send and receive through a free plugin called DistroAV.

One distinction before we go further: NDI is studio transport, not a delivery format. It moves video between your own devices over a local network. It doesn't put your stream on the internet — that part still belongs to your encoder and the platform you push to. More on that further down.

NDI High Bandwidth vs NDI HX

NDI comes in two quality tiers, and picking the right one is the difference between a flawless feed and a stuttering mess:

• NDI High Bandwidth — near-lossless quality, visually indistinguishable from a direct connection. Budget up to 150 Mbps per 1080p60 stream according to NDI's official guidance (a little more if you need an alpha channel). It wants gigabit Ethernet, and it's the right choice for main cameras and computer-to-computer links on cables.
• NDI HX — H.264/H.265 compressed and designed for devices where a full cable isn't practical. HX3 carries 1080p60 at around 50 Mbps; the older HX profile squeezes the same picture into roughly 10–16 Mbps. Quality is genuinely good — it's the format most wireless cameras and phone apps use.

The rule of thumb: wired and important gets High Bandwidth, wireless or bandwidth-constrained gets HX. They're the same protocol, receivers handle both side by side, and your network just sees very different amounts of traffic.

What You Need to Get Started

Almost all of it is free, and you probably own the rest already:

• A gigabit network. The switch or router your devices plug into. Wired connections are the standard for NDI — 100 Mbps ports are not enough for a single High Bandwidth stream, let alone two.
• NDI Tools (free). The official toolkit: Studio Monitor (view any source on the network — the first thing to check when something's wrong), Screen Capture (turn any computer screen into an NDI source), plus Test Patterns, Webcam, and Bridge for remote connections.
• OBS Studio + DistroAV + NDI Runtime. OBS gets its NDI powers from the free DistroAV plugin, formerly known as OBS-NDI. Current releases ask for OBS Studio 31.1.1 or newer and NDI Runtime 6.3+ — install OBS first, then the plugin, then the runtime, then restart OBS.
• At least one NDI source. A PTZ camera with NDI built in, a phone running the official NDI Camera app, or another computer running OBS or NDI Tools.

Setting It Up: OBS to OBS in Ten Minutes

This is the two-computer template, and the same steps carry over whether the second device is a laptop, a camera, or a phone. If scenes and sources are still new to you, start with our OBS Studio for DJs guide.

1. On every computer involved, install OBS Studio, then DistroAV, then the NDI Runtime — in that order. If you ever installed the old OBS-NDI plugin, remove it first; the two don't coexist. Restart OBS when you're done.
2. On the sending machine, open OBS and go to Tools → DistroAV NDI Settings. Enable Main Output and give it a clear name, like OBS-Visuals.
3. Alternative senders: run NDI Screen Capture on any computer to broadcast its screen, or open the NDI Camera app on a phone and tap the NDI logo to start sending.
4. On your streaming machine, click + in the Sources panel, choose NDI Source, and select your sender in the Source Name dropdown.
5. In the source properties, set Bandwidth to Highest on a wired network, Latency to Lowest, and tick Use audio if the sender carries sound.
6. If a source doesn't appear, open NDI Studio Monitor first. If it's missing there too, it's a discovery or network problem — not an OBS problem.

That's one link between two machines. Repeat steps 2–5 for each extra source, and a two-camera plus visuals show runs with zero capture hardware.

Bandwidth Math That Actually Matters

NDI is remarkably efficient, but it still lives on your network — and networks are where live video dies:

• Budget ~150 Mbps per High Bandwidth 1080p60 stream. A gigabit switch carries about six of those in theory; plan for fewer and leave headroom for normal internet traffic.
• HX3 needs roughly 50 Mbps; the older HX profile as little as 10–16 Mbps. A typical setup — two wired cameras plus a phone on HX — lands around 350 Mbps. Easy on gigabit, hopeless on 100 Mbps ports.
• Every receiver adds its own copy. NDI traffic is duplicated per receiving device, so if two machines monitor the same camera, that stream costs double on the network.
• Wire everything that matters. Use cables for cameras and computers; a strong 5 GHz signal can carry a phone's HX feed, but High Bandwidth over Wi-Fi drops frames for a living.
• Keep the network boring. No VPNs on production machines (they break discovery), no guest networks with client isolation, and for bigger rigs a dedicated switch keeps NDI traffic away from everything else in the house.

Five DJ Workflows Where NDI Shines

This is where it stops being network theory and starts being useful on a Friday night:

• Phone as a second camera. The official NDI Camera app turns your phone into a wireless HX source — no USB tether, no bridging software. We walked through the complete phone-camera method in Two-Camera DJ Stream Without ATEM; NDI is the wireless option there, and a USB-C-to-Ethernet adapter makes it bulletproof.
• The visuals laptop. Run Resolume or any VJ software on a second machine and send its output over the network straight into OBS. No capture card, no HDMI run under the desk.
• Screen capture without hardware. NDI Screen Capture can broadcast a single region of a display — perfect for a track-info panel pulled from your DJ software, or for showing your prep screen between sets.
• PTZ camera with remote control. Studio Monitor finds and controls NDI PTZ cameras over the network — store wide, mid and close presets, and switch framing without leaving the decks.
• A proper broadcast switcher. If you outgrow OBS scenes, vMix supports NDI natively — receive your OBS output, add replays and graphics, or send its program back. See vMix for DJs for that path.

Where NDI Fits — and Where It Doesn't

NDI solves the cable problem inside your studio. It does not reach your audience. To go live, you still compress your program in OBS and push it to a destination — YouTube, Twitch, or a self-hosted setup. That split exists in every production: transport moves video between your machines, and a server delivers it to listeners. If you want to own the delivery side, our MediaMTX guide covers self-hosting the video stream.

It's also the layer where a platform like Grooveline comes in: a free place for DJs to broadcast, where you connect your encoder, book a slot, and your audience finds you there. NDI is everything that happens before you hit that button.

And if your sources sit in different buildings — a guest DJ, a venue feed — NDI Bridge can link two NDI networks over the internet, and SRT remains the standard for remote contribution. For most DJ setups, though, plain local-network NDI is all you'll ever need.

Troubleshooting the Common Failures

• The source never appears. Nine times out of ten it's discovery, not NDI: check that both devices are on the same subnet, that firewalls aren't blocking it (on Windows, allow OBS on private networks; on macOS, give OBS local network access; on Linux, make sure Avahi is running), and that no VPN is active. Then restart OBS on the sender and verify with Studio Monitor before touching your scene.
• Video stutters or drops frames. That's bandwidth. Go wired, switch that sender from High Bandwidth to HX, check what else is hammering the switch, and remember that every extra receiver duplicates unicast traffic.
• The feed is black. Test the same source in Studio Monitor. If it's black there too, the problem is on the sending side — check that its output is actually enabled and the camera or app is capturing.
• No audio. Tick Use audio in the NDI Source properties, and check the sender's audio routing — NDI only carries sound that the sender includes.
• The plugin vanished after an update. OBS, DistroAV and the NDI Runtime must be version-matched; remove any leftover OBS-NDI files, restart, and check Help → Log Files for the plugin load line.
• Multiple rooms, VLANs or venues. Install the free NDI Discovery Server so sources can still see each other across subnets.

Get discovery and bandwidth right, and NDI is one of those upgrades that keeps paying off: every future camera, laptop or phone you add becomes one more source in a dropdown — no adapter, no dongle, no extra capture card.

Sources & Further Reading

• NDI — Bandwidth White Paper — official per-stream bandwidth tables for High Bandwidth and HX formats
• NDI — Getting Started in OBS — the official DistroAV install and setup walkthrough
• DistroAV — the free, open-source OBS plugin for NDI, with current release requirements
• NDI Tools — free downloads: Studio Monitor, Screen Capture, Bridge, and more
• vMix — NDI — how NDI works inside a production switcher, with official walkthroughs

Ready to put this into practice? Grooveline is a free platform for DJs to broadcast — create your profile, book a slot, and go live.