DHD has released a free, cross-platform utility designed to solve one of the most persistent headaches in broadcast audio engineering: figuring out the IP address of a newly connected device. DHD Discovery, available now for Windows 10 and later, quietly watches the local network and surfaces every compatible DHD audio device the moment it comes online. A single click then opens that device’s browser-based management interface, eliminating the usual hunt through DHCP tables, switch ports, and scribbled notes.

How DHD Discovery Streamlines Device Access

The utility sits in the system tray and uses Multicast DNS (mDNS) to detect DHD hardware on the local network segment. It works without requiring a central DNS server—devices simply announce themselves, and Discovery listens. The result is a near-instant picture of what’s connected: DHD cores, RM1 broadcast-from-anywhere interfaces, AES67/Ravenna audio-over-IP endpoints, and Dante-connected DHD interfaces all appear automatically.

Each discovered device shows critical operational details right in the tray menu or a resizable local dashboard. IP address, firmware version, serial number, and connection status are displayed alongside colour-coded health indicators. A search bar and favourites list help manage larger inventories, and manual entries let you add devices on other subnets—a necessity in studios where management networks often sit on separate VLANs from audio traffic.

The standout feature is direct WebApps access. Click any device, and its full web-based configuration environment opens in the default browser. No copying IP addresses, no typing errors, no confusion between identical interfaces in a rack. As DHD managing director Marc Herrmann put it in the company’s announcement: “Anyone who has commissioned a DHD system knows the question: A new device joins the network, so what’s its IP? Our established DHD Toolbox application has always had the answer but a lightweight utility in your tray is simply more comfortable for that quick look.”

Why Instant IP Resolution Matters in Broadcast

For the engineers who build and maintain radio studios, OB vans, and production control rooms, the seconds spent hunting for a device’s address add friction to almost every task. A new interface might get a DHCP lease, retain a static address from a previous deployment, or lurk on an unexpected VLAN. Without a discovery tool, identifying it means pinging, scanning, consulting spreadsheets, or physically tracing cables.

DHD Discovery removes that uncertainty. During commissioning, an installer can confirm that each piece of hardware is reachable as soon as it’s patched into the switch. When a unit is replaced, the utility immediately reveals whether the new device has joined the correct network and which IP it claimed. For routine maintenance, a quick glance at the tray icon can tell a support engineer that a core or remote interface is present and healthy—or flag it as missing before deeper troubleshooting begins.

The tool is especially valuable in outside broadcast work. Temporary setups often involve unfamiliar switches, limited documentation, and tight deadlines. Bringing up a Discovery dashboard on a laptop gives an at-a-glance inventory of DHD gear on the local link, letting engineers move faster from hardware setup to audio configuration.

The Bigger Picture: From Analog to IP-Centric Workflows

Professional audio has undergone a decisive shift toward networked, packet-based transport over the past decade. Standards like AES67, Ravenna, and Dante now connect mixing consoles, I/O boxes, and routing matrices across standard Ethernet infrastructure. While this brings flexibility and scalability, it also introduces a new layer of complexity—devices are no longer identified by a physical control cable running to a patchbay. They’re just IP endpoints, indistinguishable from any other network node without the right tools.

DHD has long offered device discovery inside its Toolbox application, a comprehensive platform for configuring console logic, managing firmware, and designing larger systems. But launching Toolbox to check an IP address is overkill for a routine task. Discovery fills that gap as a lightweight, always-on companion that does one job quickly.

mDNS, the protocol behind the app, is a natural fit. It’s standard, low‑overhead, and designed for local networks where devices need to find each other without pre‑configured DNS entries. The trade‑off is that mDNS traffic typically stays on its own subnet; Discovery can’t automatically scan across routed VLANs unless the network is specifically set up to forward multicast. That’s why the manual subnet entry feature exists, and why DHD is clear that Discovery supplements, not replaces, formal network monitoring.

What Broadcast Engineers Need to Know Before Deploying

System requirements and availability
DHD Discovery runs on Windows 10 (or newer), macOS 12 (or newer), and modern Linux distributions with FUSE support. The installer is free and available directly from DHD’s website. On Windows, the app appears as a system tray icon and can be set to launch automatically at login.

Security and network design
Because Discovery exposes device IPs, firmware versions, and direct management links, it should only run on workstations that are already authorized to access the audio or management network. Most broadcast facilities isolate these networks with firewalls and access controls; tool should be treated as part of that administrative surface. Ensure that device WebApps themselves enforce strong passwords and, where supported, HTTPS.

Organizations with complex multi‑VLAN topologies should test Discovery on a non‑production segment first. mDNS behaviour depends on switch configuration—multicast forwarding, IGMP snooping, and mDNS gateway settings can all affect what the app sees. If a critical device fails to appear, it’s often a network boundary issue rather than a hardware fault.

Update policy
Discovery can check for and install updates automatically. That’s convenient for standalone PCs, but in a mission‑critical studio, any software change merits review. Consider disabling auto‑update on machines that support live productions and instead roll out tested versions through a change‑management process.

Integration with existing tools
Discovery is not a replacement for DHD Toolbox, which remains the environment for in‑depth configuration. Neither is it a substitute for a proper network monitoring system that watches stream health, clocking, and switch telemetry. Think of it as a digital “rack labels” layer: it tells you what’s there and how to reach it, so you can get to the real work faster.

The Road Ahead

DHD will showcase Discovery at IBC2026 in Amsterdam (September 11–14), where engineers can see it running against live hardware. The cross‑platform design is a strategic move that acknowledges the mixed‑OS reality of modern broadcast teams—Windows workstations are common in control rooms, macOS on freelancers’ laptops, and Linux in specialist audio servers.

Looking further, the utility’s foundation on mDNS could open doors to broader discovery across other AoIP ecosystems, though DHD has made no such announcements. For now, the tool is laser‑focused on DHD’s own product line, and its success will be measured by how reliably it surfaces devices across the diverse hardware generations and network designs found in real‑world studios.

In a workflow where seconds count, a free tray app that turns “What’s the IP?” into a one‑click answer is a modest but genuine improvement. DHD Discovery doesn’t rewrite the rules of broadcast audio; it simply removes a daily annoyance, and that may be exactly what busy engineers need.