Configuring ports

Allow SoundBase Desktop through your firewall so device discovery, Remote View, and integrations work.

SoundBase Desktop opens local network sockets for wireless device discovery and control, and runs small local servers for Remote View (TCP 9999), the Bitfocus Companion bridge (TCP 5480), and REAPER OSC (UDP 9000). The complete port and protocol list lives in the network reference — this page is the firewall how-to.

Note

If a firewall alert pops up when SoundBase Desktop starts, allow access for the network types you use — on a show network that’s typically Private (and Domain where applicable).

macOS

1. On first launch, macOS asks whether SoundBase Desktop may find devices on the local network — click Allow. (To change it later: System Settings → Privacy & Security → Local Network.)
2. If the macOS firewall is enabled, open System Settings → Network → Firewall → Options and confirm SoundBase Desktop.app is allowed to receive incoming connections — or leave Automatically allow downloaded signed software to receive incoming connections enabled, which covers it.

Windows

1. On first launch, Windows Defender Firewall asks about SoundBase Desktop — check the network types you use (Private, and Domain if applicable) and click Allow access.
2. To fix it after the fact: Windows Security → Firewall & network protection → Allow an app through firewall, then tick SoundBase Desktop for the right network types. There may be more than one entry after updates — allow each.
3. For third-party firewall or endpoint software, use the vendor’s instructions to allow the application, including its inbound listeners (see the port list).

Note

Running Shure Wireless Workbench on the same machine? Its snetDaemon needs its own firewall allowance — that’s part of WWB, not SoundBase.

If devices still don’t appear after the firewall is open, confirm the right network interface is selected on the device setup page and that your computer is on the same subnet as the devices — see the network requirements.