Troubleshoot
Categories:
Goal / when to use
Something does not connect, discover, sync, or route audio. Work through the matching section below.
Out of Sync
Symptoms
- Floating OUT OF SYNC alert in the UI
- Device SYNC indicator not clean
- Levels or EQ on the amp do not match Maxx Remote
Why it happens
Maxx Remote owns linked channels (Remote → device). Edits in Maxx Control, front-panel/other tools, or failed partial writes create differences. Maxx Remote detects them on periodic check-in.
Steps
- Click OUT OF SYNC (or device SYNC).
- Review which parameters differ.
- Choose direction carefully — normal recovery is APP → DEVICE (project wins).
- Use SYNC DEVICE / SYNC EVERYTHING as offered.
- Optional: enable HOME AUTO SYNC so future mismatches are pushed from the project automatically.
Expected result
Sync UI clears; amp matches the project.
Do not “fix” sync by randomly editing both Maxx Control and Maxx Remote. Pick Maxx Remote as source of truth for linked systems.
Device not discovered
Symptoms
ADD FROM NETWORK is empty; UI may warn that discovery on UDP 9453 is unavailable.
Steps
- Confirm the amp appears in IDFM (discover) on the same PC/network.
- Check PC and amp are on a discovery-friendly segment (broadcast does not cross routers).
- Docker: use
--network host— publishing UDP 9453 with-pis not enough for broadcast discovery. See Installation. - Select the correct NETWORK INTERFACES / RECEIVE DISCOVERY options if shown.
- Fall back to ADD MANUALLY with hostname + IP.
Expected result
Device listed, or manually added and CONNECT goes online.
Dante TX sources missing in Maxx Remote
Symptoms
INPUTS / Dante discovery shows no (or stale) transmit channels, while Dante Controller on another PC may still see them.
Steps
- Confirm Maxx Remote can join the Dante control network (same L2 segment as the devices).
- Docker: use
--network host. Dante discovery needs mDNS (224.0.0.251:5353) plus multicast224.0.0.231:8702and224.0.0.233:8708— bridge-pmappings do not deliver that reliably. - Check host firewall allows those UDP multicast joins / inbound packets.
- As a workaround, read Transmit Channel@Hostname from Dante Controller and enter the INPUT SOURCE manually.
Expected result
TX channels appear for assignment, or you can enter them from Dante Controller.
Device connected but offline / errors
- DEVICES → STATUS column and CONNECT switch.
- Ping / browser-check the amp IP; re-run IDFM if IP changed.
- LOG → filter errors, Export Log if you need support.
- Try IDENTIFY / REBOOT DEVICE when safe.
- Re-link channels if the amp was replaced.
Dante / INPUTS silent
- Confirm TX hostname and label in Dante Controller match the INPUT SOURCE.
- Check channel ROLE (Left/Right vs Mono).
- Confirm the group has Input ability and a source assigned.
- For surround mismatches, review crossmix and group output setup.
- Verify Dante and control networks are as designed (many sites separate them).
- Look for
D:subscriptions in Dante Controller after assignment.
Wrong speaker / wrong EQ after linking
- Open LINK CHs.
- IDENTIFY each HW channel.
- Unlink and re-link to the correct project channel.
- Re-apply or verify speaker preset if used.
Replace an amplifier
- Export the project.
- Add the new device; keep project channels.
- Link speakers again with IDENTIFY.
- SYNC project → device.
- Remove the old device when safe (do not delete project channels unless intended).
Common mistakes
- Blaming Maxx Remote for discovery when IDFM also cannot see the amp.
- Recreating Docker without a volume after a “fix.”
- Syncing device → app accidentally and wiping intentional project tuning.
- Leaving AUTO SYNC off and Maxx Control open on the same amps.