Prerequisites
Network, discovery, Dante, and tools you need before commissioning with Maxx Remote.
Categories:
Goal / when to use
Check this list before you expect amplifiers to appear automatically, Dante streams to route, or a Docker server to stay reachable.
1. Device network setup (IDFM)
Before Maxx Remote, put amplifiers on a working IP plan with IDFM (install):
- Discover devices.
- Set IP mode / address / hostname as required by the site.
- Update firmware if IDFM reports newer versions.
Tip
Always start network and firmware setup in IDFM. Maxx Remote assumes devices are already reachable.
2. Ports and reachability
| Traffic | Address / port | Purpose |
|---|---|---|
| TCP 8000 | host :8000 | Maxx Remote UI and REST API (http://host:8000, OpenAPI at /api-docs/) |
| UDP 9453 | broadcast 255.255.255.255 | Innosonix amplifier discovery (INX / IDFM) |
| UDP 5353 | multicast 224.0.0.251 | mDNS used for Dante device discovery |
| UDP 8702 | multicast 224.0.0.231 | Dante control-plane notifications |
| UDP 8708 | multicast 224.0.0.233 | Dante heartbeats |
Outbound (device-side ports Maxx Remote talks to, not listens on): Dante ARC queries typically 4440 / 4444 / 4455, CMC registration typically 8800.
Firewall / VLAN notes:
- The PC or Docker host must reach each amplifier’s management IP (HTTP/API used by Maxx Remote).
- Discovery broadcast/multicast usually do not cross routers. Across subnets, add amplifiers by hostname + IP instead of relying on scan.
- Docker: use
--network hostfor automatic INX and Dante discovery. Publishing only-p 8000:8000is enough for the UI if you add devices manually — see Installation.
3. Dante (audio network)
If you use Dante input sources:
- Amplifiers and sources must share a working Dante network (often separate from or VLAN’d from control).
- Maxx Remote discovers Dante TX channels on the LAN (mDNS + multicast control plane above). You can still use Dante Controller (or equivalent) to confirm Transmit Channel@Hostname names when creating INPUTS.
- Maxx Remote can create dynamic Dante subscriptions (often shown with a
D:prefix in Dante Controller). - On Docker, Dante discovery needs the same host-network path as amplifier discovery — bridge
-pmappings are not enough.
Stereo / surround routing is covered in Inputs and routing and Surround input sources.
4. Control PC / server
- Desktop: portable Maxx Remote build for your OS
- Server: Docker host with enough disk for a volume (do not rely on ephemeral container storage)
- Browser: modern Chromium / Firefox / Edge for the web UI
5. Project planning (optional)
You can create channels, groups, EQ, and routing offline with no amplifiers present. Link hardware later on site. See Projects.
Expected result
- Amplifiers respond to ping / IDFM
- Maxx Remote UI opens on port 8000
- Amplifier and Dante discovery work on the same L2 segment (or you are ready to add amplifiers manually and pick TX names from Dante Controller)
Common mistakes
Common mistakes
- Skipping IDFM and fighting wrong IPs inside Maxx Remote.
- Expecting discovery across routed VLANs without static IPs.
- Putting control and Dante on incompatible networks, then blaming INPUTS.
- Opening an old static build on port 8000 while editing something else — always confirm which Maxx Remote instance you are talking to.