Maxx Remote

• 1: Concept
• 2: Installation
• 3: Prerequisites
• 4: Quick-Start
• 5: Projects
• 6: Build a system
• 6.1: Channels and groups
• 6.2: Devices and linking
• 6.3: Inputs and routing
• 6.4: Tuning
• 7: Everyday control
• 8: Advanced
• 8.1: Multi-way channels
• 8.2: Surround input sources
• 8.3: Speaker presets
• 9: Troubleshoot
• 10: GUI reference
• 10.1: HOME
• 10.2: DEVICES
• 10.3: INPUTS
• 10.4: CHANNELS
• 10.5: GROUPS
• 10.6: CROSSMIX
• 10.7: SIG-PATH
• 10.8: VIEW
• 10.9: LOG
• 11: API
• 11.1: REST API
• 11.2: Maxx Remote View API
• 11.3: Group signal path

1 - Concept

Goal / when to use

Read this once before you build a project. Maxx Remote sits between your speakers / rooms and the amplifier hardware, so you can tune and operate without constantly asking “which amp, which output?”

Mental model

Maxx Remote is an abstraction layer over amplifier outputs. It does not matter whether 1,000 speakers sit on thirty-two 32-channel amplifiers or on many smaller units — you work with project channels and groups.

As an operator or tuner, you usually care about this speaker or this room, not which physical output is used that day. Linking can change later; the channel settings stay in the project.

System overview

Desktop / Server and UI

Maxx Remote always consists of:

1. A server that holds the project and talks to amplifiers
2. A web UI (the screens you use in the browser or Desktop window)

Access the UI at http://localhost:8000 on the machine running the server (or http://<server-ip>:8000 for Docker / remote hosts).

Objects you will use

How they relate

A channel behaves like a channel strip: you can set it directly.

If that channel also belongs to one or more groups, group values are added (summed) with the channel’s own values. The result is what the amplifier should play.

Example for volume:

When a channel is linked to a HW channel, Maxx Remote sends that output result to the device.

Because settings live in the Maxx Remote project, you can replace an amplifier or re-link speakers to different outputs without rebuilding the whole tuning from scratch.

Out of Sync

After a channel is linked, Maxx Remote periodically compares project data with the device. Someone can still change the amp from Maxx Control or other tools — Maxx Remote then reports OUT OF SYNC for the mismatched parameters.

You resolve sync by aligning values in Maxx Remote with the device, or by pushing project data to the device (SYNC). Details: Troubleshoot.

Expected result

You understand that:

• Channels and groups are how you design and operate the system
• Devices and HW channels are how sound reaches the speakers
• Output levels are the sum of channel + group contributions

Common mistakes

Related links

• Installation
• Quick-Start
• Channels and groups
• Devices and linking

2 - Installation

Goal / when to use

Get Maxx Remote running so you can open the UI and create or load a project.

• Choose Desktop for commissioning laptops and day-to-day design work.
• Choose Docker for an always-on server that browsers can reach on the network.

Prerequisites

• Supported OS for Desktop, or a host that can run Docker
• Network access to your amplifiers (see Prerequisites)
• For automatic discovery (amplifiers and Dante TX sources): the host must receive the UDP broadcast / multicast traffic listed under Ports and discovery — on Docker that means host networking

Desktop application

1. Download Maxx Remote from the Innosonix downloads page.
2. Unpack or place the portable application where you want it — no installer is required.
3. Start the application.
4. On first launch, use Start a new project or import an existing project archive.

Expected result

The Maxx Remote window opens with the project splash / HOME UI. You can also reach the same UI in a browser at http://localhost:8000 while the Desktop app is running.

Server / Docker

Ports and discovery

Maxx Remote listens for more than the web UI. Automatic discovery uses UDP broadcast and multicast, which Docker’s default bridge network does not forward reliably when you only publish ports with -p.

Maxx Remote also sends outbound unicast UDP to Dante devices (ARC channel queries, typically ports 4440 / 4444 / 4455, and CMC registration, typically 8800). Those are device-side ports — they are not something you “publish” on the container; the host firewall must allow the outbound path.

Recommended: host network (discovery works)

Use host networking whenever you want automatic amplifier scan or Dante TX discovery:

docker run --detach --name maxx-remote --network host innosonix/maxx-remote:latest

Once the container is running, open:

http://<docker-host-ip>:8000

Alternative: published ports (UI only — no discovery)

If you only need the web UI and will add amplifiers by IP / hostname (and do not rely on Maxx Remote’s Dante discovery), bridge networking with a published HTTP port is fine:

docker run --detach \
  --name maxx-remote \
  -p 8000:8000 \
  innosonix/maxx-remote:latest

Compose equivalent:

services:
  maxx-remote:
    image: innosonix/maxx-remote:latest
    ports:
      - "8000:8000"
    # Discovery (INX + Dante) will not work reliably on the default bridge.
    # Prefer network_mode: host when you need ADD FROM NETWORK or Dante TX scan.

Do not expect a long -p 9453:9453/udp -p 5353:5353/udp … list to replace --network host for discovery. Map TCP 8000 for the UI; use host networking when discovery matters.

Persist project data (recommended)

Option A — Export / import yourself

Use the UI Export / Import controls when you migrate to a new container.

Option B — Docker volume (preferred)

# create once
docker volume create maxx-remote-volume

docker run  --detach \
            --restart always \
            --name maxx-remote \
            --network host \
            --mount source=maxx-remote-volume,target=/root \
            innosonix/maxx-remote:latest

Expected result

Browsers on the network can open the Maxx Remote UI on port 8000, and projects survive container restarts when a volume is mounted. With --network host, ADD FROM NETWORK and Dante TX discovery can see devices on the same LAN segment.

Common mistakes

Related links

• Prerequisites
• Quick-Start
• Projects
• Docker Hub: innosonix/maxx-remote

3 - Prerequisites

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):

1. Discover devices.
2. Set IP mode / address / hostname as required by the site.
3. Update firmware if IDFM reports newer versions.

2. Ports and reachability

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 host for automatic INX and Dante discovery. Publishing only -p 8000:8000 is 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 -p mappings 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

Related links

• IDFM · Install · Discover and IP
• Installation
• Quick-Start
• Troubleshoot

4 - Quick-Start

Goal / when to use

Get first music out of a simple system: three speakers (Left, Right, Sub) on an MA32/D², with group volume/EQ and a stereo Dante source (for example Dante Virtual Soundcard).

This is a guided walkthrough. For deeper topics afterward, use Build a system and Everyday control.

Prerequisites

• Maxx Remote installed and running (Installation)
• Amplifier on the network (Prerequisites, IDFM / install)
• Speakers on amp channels 1, 4, and 9 (or adapt the link steps)
• Dante TX available (hostname + transmit channel names)

1. Create a project

1. Start Maxx Remote. On the splash screen, click Start a new project.
2. Enter a project name and confirm.

Expected result

HOME opens for the new project.

2. Create channels and a group

1. Open CHANNELS → MAP | CREATE.

   

2. Click + CHANNEL, set CHANNELS TO ADD to 3, name them (for example Left, Right, Subwoofer), then CREATE CHANNELS.

   

3. Confirm the three PROJECT CHANNELS exist. LINKED TO is empty until you connect hardware.

   

4. Click + GROUP, name it (for example ROOM 1), and create it.

   

5. Map all three channels into the group: drag and drop, or select them and click MAP.

   

Expected result

Three unlinked channels mapped to ROOM 1.

3. Add the amplifier and link outputs

1. Open DEVICES → ADD DEVICE.

2. Add a device found on the network, or add manually (model + hostname).

3. Disable CREATE CHANNELS / GENERATE PROJECT CHANNELS if offered — you already created the three you need.

   

4. Wait until Maxx Remote connects. Use CONNECT to disable network activity if needed.

   

5. Open the LINK CHs (linked channels) control.

   

6. Use IDENTIFY to play a test tone (for example pink noise at −40 dB) and confirm the physical speaker.

   

7. Link each project channel to the correct HW channel (drag and drop or LINK).

   

8. Finish Left, Right, and Sub.

   

9. Reorder later by dragging HW channels between empty slots, or swap by dropping onto an assigned slot.

Expected result

All three project channels show a hardware link; identify confirms the correct speakers.

4. Set safe group volume

1. Open GROUPS and click the VOLUME field for ROOM 1.

   

2. Enter -20 and press Enter or SET.

   

3. On CHANNELS, raise the Subwoofer channel by +6 dB for a bit of boost.

Example: group −20 dB + channel +6 dB → −14 dB output.

Expected result

Room is at a safe level; Sub sits 6 dB hotter than Left/Right at the channel layer.

5. EQ the Subwoofer

1. Open CHANNELS → EQ for Subwoofer.

2. Drag a LOW PASS filter into the EQ view.

   

3. Select the filter (blue handle / row), open the gear editor, pick for example 24 dB Butterworth, confirm OK.

   

4. Set frequency by dragging or typing, then Enter / SET.

5. Add more filters if needed.

   

6. EQ the group (room)

1. Add overall EQ on GROUPS → ROOM 1.

   

2. Jump back to the group’s channels (arrow control).

   

3. Re-open Subwoofer EQ — you should see channel EQ plus group EQ summed.

   

Expected result

Room EQ affects all members; Sub still shows its own low-pass on top.

7. Create Dante INPUTS and assign roles

From Dante Controller, note Transmit Channel@Hostname (example: 01@STEFFEN-PC).

1. Open INPUTS → + INPUT SOURCE. Fill in:

   • SOURCE LABEL — name in Maxx Remote
   • RECEIVE HOSTNAME — Dante device hostname
   • RECEIVE LABEL — transmit channel name

   

2. Open GROUPS → INPUT and assign the source to ROOM 1.

   

3. Channels inherit the source using their ROLE (Left / Right / Mono, …).

4. If Left is still MONO, it may downmix both legs — set ROLE → LEFT.

   

   

   

5. Confirm Dante Controller shows dynamic subscriptions (often prefixed with D:).

   

6. Set Right to role RIGHT. Leave Sub as MONO for a stereo downmix to the sub.

Expected result

Music plays Left / Right / Sub with correct legs; Dante shows the subscriptions Maxx Remote created.

Checklist — you are done when

• Project created and named
• Three channels + one group, channels mapped to the group
• Amplifier connected; three HW links confirmed with IDENTIFY
• Group volume set to a safe level; Sub offset applied if desired
• Sub low-pass (and optional room EQ) in place
• Stereo INPUT created and assigned to the group
• Channel roles Left / Right / Mono correct
• Audio heard on all three speakers

Common mistakes

Related links

• Projects
• Build a system
• Surround input sources
• Troubleshoot

5 - Projects

Goal / when to use

Manage the project file that holds your channels, groups, devices, inputs, views, and tuning. Use this when starting a job, moving between machines, or keeping a Docker server’s configuration safe.

Prerequisites

• Maxx Remote Desktop or Server running (Installation)

Create a new project

Desktop or browser splash

1. Start Maxx Remote with no project loaded.
2. Choose Start a new project.
3. Enter a clear site name (for example Museum-Floor2).

Desktop menu (Electron)

Use the application menu when available:

• New Project
• Load Project / Last Projects
• Save Project / Save Project As
• Close Project

Expected result

HOME shows the new project name; DEVICE / CHANNEL counts start empty.

Open / import an existing project

1. On the splash screen, choose Import project archive to host, or
2. Use the top-bar Import control to upload a project archive or partial JSON.

Expected result

HOME and list pages populate with the imported project.

Export / backup

1. Use the top-bar Export control.
2. Store the download with your site documentation.

Export before:

• Updating Maxx Remote
• Recreating a Docker container
• Handing the project to another engineer

Offline planning

You can design without amplifiers:

1. Create channels and groups.
2. Set volumes, EQ, delay, mute, speaker presets.
3. Define INPUTS and roles (even if Dante is not online yet).
4. On site, add devices and link.

Project settings stay in Maxx Remote until you link and sync to hardware.

Docker persistence

Recommended pattern:

1. Mount a volume (see Installation).
2. Periodically Export from the UI as an off-host backup.
3. When migrating hosts, import the archive into the new server.

HOME project card

On HOME you can:

• View / set the project NAME
• See overall STATUS for devices and linked channels
• Enable AUTO SYNC so Maxx Remote can push project data when differences are found
• Open REST-API Doc for integrators

Details: GUI · HOME.

Expected result

You can create, reopen, and back up a project, and you know how Docker storage differs from Desktop files.

Common mistakes

Related links

• Installation
• Quick-Start
• Troubleshoot

6 - Build a system

Goal / when to use

Use this chapter after Quick-Start when you commission a real site: model speakers and rooms, connect amplifiers, bring in program sources, then tune.

For multi-way cabinets, surround, and speaker presets, see Advanced.

6.1 - Channels and groups

Goal / when to use

Build the logical system: one channel per speaker (or multi-way cabinet), and groups for rooms, zones, or show control.

Prerequisites

• Open project (Projects)
• Optional: sketch which speakers belong to which rooms

Create channels

1. Open CHANNELS → MAP | CREATE.
2. Click + CHANNEL.
3. Set how many channels to add and name them (for example Lobby Left, Lobby Right).
4. Click CREATE CHANNELS.

For multi-way cabinets (one channel object with Low/Mid/High ways), enable MULTI-WAY MODE — see Multi-way channels.

Expected result

Channels appear in the CHANNELS list with empty LINKED TO until devices are linked.

Create groups

1. In MAP | CREATE, click + GROUP.
2. Name the group after the room or zone (for example Foyer, Hall A).
3. Create the group.

Expected result

The group appears in GROUPS and in the mapping lists.

Map channels into groups

1. Stay in CHANNEL | GROUP MAPPING (MAP | CREATE).
2. Select one or more channels.
3. Drag them onto a group, or click MAP.
4. Use UNMAP when a speaker should leave a room.
5. Filters MAPPED ONLY / UNMAPPED ONLY help large projects.

Expected result

Groups show their member channels; CHANNELS can show group membership.

Choose what a group can control

On a group’s edit dialog, GROUP ABILITIES decide which controls the group exposes (Mute, Volume, EQ, Input, Speaker Preset, and more). Turn off abilities you do not want operators to touch at group level.

Expected result

GROUPS overview and edit tabs match the abilities you enabled.

Channel roles (for inputs)

Set each channel’s ROLE (Left, Right, Mono, Center, LFE, surrounds, …) so group INPUT assignment routes the correct Dante legs. Details: Inputs and routing, Surround.

Common mistakes

Related links

• Concept
• Devices and linking
• Everyday control
• GUI · CHANNELS · GUI · GROUPS

6.2 - Devices and linking

Goal / when to use

Connect real amplifiers and map each project channel (speaker) to the correct HW channel (amp output).

Prerequisites

• Channels already created (Channels and groups)
• Amplifiers reachable (Prerequisites)
• Prefer fixed IPs for installed systems

Add a device

1. Open DEVICES → ADD DEVICE.
2. Choose:
   • ADD FROM NETWORK — select discovered units (SCAN NETWORK as needed)
   • ADD MANUALLY — model + hostname (and IP when known)
3. Decide whether to CONNECT AFTER ADDING.
4. Only enable CREATE CHANNELS if you want Maxx Remote to auto-create a project channel per amp output. For planned systems, leave this off.
5. Confirm ADD / ADD SELECTED.

Expected result

The device row appears with STATUS updating as Maxx Remote connects. CONNECT can pause network activity.

Link project channels to HW channels

1. On the device row, open LINK CHs.

2. Select a project channel and a free HW channel.

3. Use IDENTIFY on the HW side to play a test tone and confirm the speaker.

   

4. LINK (or drag and drop).

   

5. Repeat for all speakers.

6. Reorder / swap by dragging HW channels between slots.

Expected result

CHANNELS LINKED TO shows the amp/output; identify matches the physical position.

Multi-way and speaker devices

Multi-way channels need several HW channels (or a speaker-style device) linked together. See Multi-way channels.

Replace a device

Typical sequence:

1. Export the project (Projects).
2. On the old device row, note hostname / links (or leave links and remove carefully).
3. Add the replacement amplifier (same model when possible).
4. Re-link project channels to the new HW channels (IDENTIFY again).
5. Use SYNC if STATUS shows differences (Troubleshoot).

Optional delete dialog may offer to remove linked project channels — usually keep project channels and only remove the device.

Device row actions worth knowing

Common mistakes

Related links

• Quick-Start · linking
• Troubleshoot
• GUI · DEVICES

6.3 - Inputs and routing

Goal / when to use

Bring program audio into Maxx Remote so groups and channels receive the correct Dante (or related) streams.

Prerequisites

• Groups with Input ability enabled
• Channel ROLE planned (Left / Right / Mono / surround roles)
• Dante Controller available to read TX names
• See also Surround input sources for 5.1 / 7.1

Create an INPUT SOURCE

1. Open INPUTS → + INPUT SOURCE.
2. Fill in:
   • SOURCE LABEL — friendly name in Maxx Remote
   • RECEIVE HOSTNAME — Dante device hostname
   • RECEIVE LABEL — transmit channel name
3. For stereo / surround sources, add each leg as required by the source type.
4. Save with CREATE SOURCE.

Example TX naming in Dante Controller: 01@STEFFEN-PC.

Optional tools on INPUTS: DANTE DISCOVERY, volume offset / mute on the source, CSV import/export for large lists.

Expected result

The source appears in INPUTS and can be selected on groups.

Assign a source to a group

1. Open GROUPS → select the group.
2. Open INPUT and choose the source.
3. Confirm the group output / channel setup (Stereo, 2.1, 5.1, …) matches the speakers in that room.

Expected result

Member channels receive streams according to their ROLE and the active crossmix strategy.

Set channel roles

1. Open CHANNELS (or the channel edit dialog).
2. Set ROLE to LEFT, RIGHT, MONO, or a surround role.
3. NONE means this channel will not take INPUT SOURCE streams.

Expected result

Left hears left, Right hears right; Dante Controller shows dynamic subscriptions (often D:).

Review the signal path

Use SIG-PATH to see source → group → channel → device at a glance, and to run TEST / identify from that view. See GUI · SIG-PATH.

Common mistakes

Related links

• Quick-Start · inputs
• Surround input sources
• GUI · INPUTS · GUI · CROSSMIX

6.4 - Tuning

Goal / when to use

Dial in levels and DSP after speakers are linked. Prefer group moves for room-wide changes and channel moves for speaker-specific trim.

Prerequisites

• Channels mapped to groups
• Devices linked if you want to hear results on hardware
• Understand summation (Concept)

Volume

Room (group)

1. Open GROUPS.
2. Click VOLUME for the room.
3. Enter a value (for example -20) → Enter / SET.

Speaker trim (channel)

1. Open CHANNELS.
2. Click VOLUME on the speaker.
3. Enter an offset relative to the current summed output workflow you are using → SET.

Mute and power

• Use group MUTE for room silence.
• Use channel MUTE for a single speaker.
• POWER controls (where available) can be driven from channel, group, or operator VIEW widgets.

EQ

1. Open EQ from the channel or group row (EQ icon / edit dialog EQ tab).
2. Drag filter types (PEQ, shelves, HP/LP, …) into the plot.
3. Select a filter, set type (gear), frequency, gain, Q.
4. On a channel, review the summed curve when groups also contribute EQ.

Delay and phase

1. Open the channel or group edit dialog → DELAY / PHASE.
2. Set delay for alignment; use phase invert when polarity must flip.
3. Prefer group delay only when the whole room should shift together.

Limiters, FIR, speaker tools

Advanced DSP (limiters, FIR, speaker detection, speaker presets) lives in the channel / group edit tabs (LIMIT, SPEAKER, …). For packaged speaker tunings see Speaker presets.

Bulk edits

On CHANNELS / GROUPS list pages, column headers such as VOLUME, MUTE, DELAY, PHASE open editors that can apply to the current selection — useful for many identical fills.

Undo / redo

Maxx Remote supports undo/redo for project edits — use it while tuning instead of guessing previous values.

Expected result

Rooms sit at safe levels; individual speakers are trimmed; EQ/delay match the design intent; CHANNELS output values match what you hear.

Common mistakes

Related links

• Everyday control
• Speaker presets
• Multi-way channels

7 - Everyday control

Goal / when to use

Run the finished system: change room levels, mute zones, watch meters/status, and hand simple control to operators via VIEW.

Prerequisites

• Project commissioned (Build a system)
• Devices connected and in sync

Group vs channel — which control?

Remember: group and channel values add. CHANNELS shows the output result.

Typical operator moves

Set room volume

1. Open GROUPS.
2. Set VOLUME (or use a VIEW volume widget).
3. Confirm meters move on member channels.

Mute a room

1. GROUPS → MUTE on, or VIEW mute control.
2. Confirm CHANNELS / SIG-PATH reflect mute.

Check health

1. HOME — project / device / linked-channel status cards.
2. DEVICES — STATUS, CONNECT, SYNC.
3. CHANNELS — LEVEL and STATUS columns.
4. LOG — export or filter if something failed.
5. Floating OUT OF SYNC — resolve before a show (Troubleshoot).

Operator VIEW pages

1. Open VIEW (view manager).
2. Create a page with + VIEW.
3. Add objects: group volume/mute, channels, level meters, images, links to other views.
4. SAVE VIEW.
5. Copy the operator Link (fullscreen page without editor chrome).
6. Open that URL on a tablet or control PC.

Details: GUI · VIEW and View API.

Expected result

Operators adjust the intended rooms without accessing CHANNELS / DEVICES commissioning screens.

Snapshots (groups)

Where available, group SNAPSHOTS store and recall sets of group-related settings for scene changes. Use them for rehearsed level/EQ scenes — not as a substitute for project export.

Expected result

Day-to-day control happens mostly from GROUPS and VIEW; CHANNELS is for trim and diagnosis; OUT OF SYNC stays clear.

Common mistakes

Related links

• Tuning
• GUI · VIEW
• Troubleshoot

8 - Advanced

Goal / when to use

Use these Maxx Remote topics after the basic stereo / mono workflow is solid.

8.1 - Multi-way channels

Goal / when to use

Use a multi-way channel when one physical speaker cabinet needs several amplifier outputs (for example low / mid / high). You still control the cabinet as one channel, while each way holds driver-specific DSP.

Prerequisites

• Familiarity with Channels and groups and linking
• Enough free amp outputs for every way

Create multi-way channels

1. Open CHANNELS → MAP | CREATE → + CHANNEL.
2. Enable MULTI-WAY MODE.
3. Set NR OF WAYS to 2, 3, or 4.
4. Name the parent channels and click CREATE CHANNELS.

Expected result

Each new channel is a parent cabinet with fixed child ways (not separately deletable).

Convert an existing channel

1. Open the channel edit dialog → MAIN.
2. Enable multi-way (or change way count) and confirm the popup.
3. You can pre-set the way count before enabling.

Naming

Ways are named from the parent plus a role:

Link multi-way channels

Linking is like normal channels, with a few extras:

1. Open DEVICES → LINK CHs.

2. Multi-way parents show their way count.

   

3. Use the PROJECT CHANNELWAYS tab to link individual ways (different amps or non-default order).

   

4. On the PROJECT CHANNELS tab, select the matching number of device channels before LINK unlocks (3-way → 3 HW channels).

   

Drag and drop rules

• Dragging a multi-way parent highlights the matching number of HW channels.

  

• Dragging HW channels onto a parent requires the same count.

  

• Extra HW channels continue to the next project channel in line.

  

• Whole-cabinet links assign HW channels low → high in list order.

  

Speaker-style devices

Some amplifiers present as a single “speaker” device with a fixed internal way layout. For those:

• Link a matching multi-way parent as a whole — not individual ways.
• The linker filters to parents with the correct way count (shown next to the device name).

How settings combine

Parent settings and way settings combine much like group + channel. For limited DSP resources (EQ, FIR, limiters, speaker detection), a way’s own settings take precedence when the hardware cannot hold everything. Parent values may already include group contributions.

UI differences

CHANNELS overview

• Ways are not multi-selected for bulk edits — edit the parent for “whole cabinet” changes.
• Ways have no separate power control; INPUT on ways is read-only (inherited).
• Parent level meter shows the combined level of its ways; STATUS combines way status.

Edit dialogs

• Way editor: no Power / Input tabs; name read-only; no channel role / multi-way section.
• Parent SPEAKER tab: no one-shot speaker detection (set per way).
• Parent STATUS lists way status (similar to groups listing members).

Common mistakes

Related links

• Devices and linking
• Speaker presets
• Tuning

8.2 - Surround input sources

Goal / when to use

Route surround program (5.1 / 7.1 and related) into rooms when the speaker layout and the source layout are not always identical. For basic stereo INPUTS, start with Inputs and routing or Quick-Start.

Prerequisites

• Groups with Input ability enabled
• Channels created and given surround ROLEs
• Dante TX labels known for every surround leg

Surround channel names in Maxx Remote

Naming varies across the industry. Maxx Remote uses:

5.1

1. Center (C)
2. Left (L)
3. Right (R)
4. Left Surround (Ls)
5. Right Surround (Rs)
6. Low Frequency Effect (LFE)

7.1

1. Center (C)
2. Left (L)
3. Right (R)
4. Left Surround (Ls)
5. Right Surround (Rs)
6. Back Surround Left (Bsl)
7. Back Surround Right (Bsr)
8. Low Frequency Effect (LFE)

Create surround INPUT SOURCES

Same workflow as stereo INPUTS, with more RECEIVE LABEL entries — one per surround leg. See Quick-Start · inputs.

Channel roles

Assign each speaker channel a role. NONE receives no INPUT SOURCE streams. MONO usually receives a combination of legs (see crossmix).

Group output / channel setup

On GROUPS, set output / channel setup to match the room (Stereo, 2.1, 5.0, 5.1, 7.0, 7.1, …). Every role in that setup should exist on at least one mapped channel.

Missing or extra roles do not always hard-error — you may simply get silent speakers or unused streams.

Crossmix (upmix / downmix)

What it is

When the INPUT SOURCE layout and the group speaker layout differ, Maxx Remote needs a matrix that maps input legs to output roles. Downmix and upmix are both handled as CROSSMIX strategies.

Crossmix page

1. Open CROSSMIX.
2. Review built-in strategies for each in/out pair; edit or add your own (+ CROSSMIX).
3. Filter by input / output setup when the list is long.

Assignment priority (highest wins)

1. INPUT SOURCE + GROUP specific strategy
2. GROUP strategy for an input setup
3. Global default for that in/out pair

Maxx Remote always picks a strategy (even for exact matches) by checking from highest priority to lowest. Gear icons open the editor for the selected / effective strategy.

Add / edit a crossmix

1. Rows = output roles, columns = input legs.

2. Enable crosspoints (double-click, or select + Enable).

3. Set Gain Offset on active points (common 0 / ±3 / −6 values are color-coded).

4. Name the strategy to unlock Add; use Save or Save As New when editing.

   

5. Mark Default only when this should become the global fallback for that in/out pair.

6. You cannot change in/out setup on the current global default (would remove the fallback). Non-defaults can change freely.

Changing setup on a strategy that was assigned to a group/input clears that assignment; Maxx Remote falls back to the next strategy in the chain.

Expected result

Surround legs land on the intended speakers; intentional up/downmix uses the strategy you selected; Dante shows the resulting subscriptions.

Common mistakes

Related links

• Inputs and routing
• GUI · CROSSMIX
• GUI · INPUTS

8.3 - Speaker presets

Goal / when to use

Package a finished speaker tuning so you can reuse it on other channels or jobs. From Maxx Remote 1.13.0, presets are created and edited in Maxx Remote (not only on the amplifier).

For multi-way cabinets, read Multi-way channels first.

Prerequisites

• Channel (or multi-way parent) tuned the way you want
• Matching way count on any target channel that will load the preset

What a preset stores

Typical fields included:

• Volume
• Phase invert
• Delay
• EQ
• FIR
• Limiters

Create a preset

1. Finish tuning on a regular or multi-way channel.
2. Open the channel edit dialog → SPEAKER tab (use the parent for multi-way).
3. Click CREATE PRESET.
4. Enter metadata. Optionally set a password so only authorized users can edit later.
5. Confirm creation / export as needed (.spkr files).

Expected result

You have a reusable speaker preset file / project preset you can apply elsewhere.

Edit a preset

1. Apply the preset to a channel (or open a channel that already has it).
2. SPEAKER tab → EDIT (enter password if prompted).
3. The UI focuses on the preset editor channel(s).
4. Change DSP, then SAVE or SAVE AS NEW / abort as offered.

Each edit increments an internal revision so two files with the same name/id can be compared for which is newer when exporting.

Apply a preset

1. Open the target channel or group → SPEAKER.
2. Use Select file (or the preset picker) and choose a .spkr file.
3. Confirm the way configuration matches (2-way preset → 2-way channel only).

Groups

• Mapped channels inherit a group’s speaker preset unless the channel already has its own.
• If several groups provide presets, the channel uses the preset from the group that was mapped first — avoid stacking conflicting group presets.
• Way-count mismatches on some members are skipped for those members.

Expected result

Target channels show the preset on the SPEAKER tab; amp output follows after link/sync.

Legacy .speaker presets

Presets created on MAXX devices (.speaker) still load, but:

• They are not editable in Maxx Remote
• New .spkr presets take precedence; applying a new preset removes the legacy one
• A channel prefers a new preset (even from a group) over a legacy preset on the channel itself

Common mistakes

Related links

• Multi-way channels
• Tuning
• GUI · CHANNELS

9 - Troubleshoot

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

1. Click OUT OF SYNC (or device SYNC).
2. Review which parameters differ.
3. Choose direction carefully — normal recovery is APP → DEVICE (project wins).
4. Use SYNC DEVICE / SYNC EVERYTHING as offered.
5. Optional: enable HOME AUTO SYNC so future mismatches are pushed from the project automatically.

Expected result

Sync UI clears; amp matches the project.

Device not discovered

Symptoms

ADD FROM NETWORK is empty; UI may warn that discovery on UDP 9453 is unavailable.

Steps

1. Confirm the amp appears in IDFM (discover) on the same PC/network.
2. Check PC and amp are on a discovery-friendly segment (broadcast does not cross routers).
3. Docker: use --network host — publishing UDP 9453 with -p is not enough for broadcast discovery. See Installation.
4. Select the correct NETWORK INTERFACES / RECEIVE DISCOVERY options if shown.
5. 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

1. Confirm Maxx Remote can join the Dante control network (same L2 segment as the devices).
2. Docker: use --network host. Dante discovery needs mDNS (224.0.0.251:5353) plus multicast 224.0.0.231:8702 and 224.0.0.233:8708 — bridge -p mappings do not deliver that reliably.
3. Check host firewall allows those UDP multicast joins / inbound packets.
4. 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

1. DEVICES → STATUS column and CONNECT switch.
2. Ping / browser-check the amp IP; re-run IDFM if IP changed.
3. LOG → filter errors, Export Log if you need support.
4. Try IDENTIFY / REBOOT DEVICE when safe.
5. Re-link channels if the amp was replaced.

Dante / INPUTS silent

1. Confirm TX hostname and label in Dante Controller match the INPUT SOURCE.
2. Check channel ROLE (Left/Right vs Mono).
3. Confirm the group has Input ability and a source assigned.
4. For surround mismatches, review crossmix and group output setup.
5. Verify Dante and control networks are as designed (many sites separate them).
6. Look for D: subscriptions in Dante Controller after assignment.

Wrong speaker / wrong EQ after linking

1. Open LINK CHs.
2. IDENTIFY each HW channel.
3. Unlink and re-link to the correct project channel.
4. Re-apply or verify speaker preset if used.

Replace an amplifier

1. Export the project.
2. Add the new device; keep project channels.
3. Link speakers again with IDENTIFY.
4. SYNC project → device.
5. Remove the old device when safe (do not delete project channels unless intended).

Common mistakes

Related links

• Concept · Out of Sync
• Prerequisites
• Devices and linking
• GUI · LOG

10 - GUI reference

Goal / when to use

Use this section as a Maxx Remote screen map: what each page is for, key actions, and links to task guides.

Task-oriented docs start at Quick-Start and Build a system.

10.1 - HOME

Purpose

Landing overview for the open project: health at a glance and entry points to docs / API.

Key actions

1. Read PROJECT card — name, status, AUTO SYNC.
2. Rename the project (NAME / SET) when needed.
3. Check DEVICES counts and status.
4. Check CHANNELS counts and linked-channel status.
5. Review LAST ACTIVITIES (who changed what).
6. Note APP-Version.
7. Open REST-API Doc (same as http://host:8000/api-docs/).

When to use

• Start of a session: is everything online?
• Enable AUTO SYNC after commissioning.
• Hand integrators the OpenAPI link.

Related

• Projects
• Troubleshoot · sync
• API

10.2 - DEVICES

Purpose

Manage every amplifier in the project and map physical outputs to project channels.

Key actions

1. ADD DEVICE — from network scan or manually (model, hostname, IP).
2. Choose network interface / SCAN NETWORK when discovery is used.
3. Toggle CONNECT per device.
4. IDENTIFY the amplifier.
5. Open LINK CHs to assign project channels ↔ HW channels.
6. Run SYNC when project and device differ.
7. Open device SETTINGS, COPY SETTINGS, or REBOOT DEVICE.
8. REARRANGE list order; REMOVE devices (watch delete-linked-channels option).

Related tutorials

• Devices and linking
• Quick-Start
• Troubleshoot

10.3 - INPUTS

Purpose

Define named INPUT SOURCES that groups can use for program audio.

Key actions

1. + INPUT SOURCE — label, receive hostname, receive label(s).
2. Edit source properties; set volume offset / mute when needed.
3. Use DANTE DISCOVERY helpers if available.
4. REARRANGE order; delete SELECTED / ALL.
5. Import/export via CSV for large systems.
6. Create/edit stream patches when the UI offers CREATE/EDIT STREAM.

Related tutorials

• Inputs and routing
• Surround input sources
• Quick-Start · inputs

10.4 - CHANNELS

Purpose

Work on individual speakers (project channels): levels, DSP, roles, linking status, and meters.

Key actions

1. MAP | CREATE — add channels; open channel↔group mapping.
2. Enable MULTI-WAY MODE when creating cabinets with multiple ways.
3. Set ROLE for input routing (Left / Right / Mono / surround…).
4. Edit DSP via row controls or dialog tabs: Volume, Mute, Phase, Delay, EQ, Limiter, Speaker, Input, Power, Status, …
5. Read LEVEL / STATUS; remember values are final output (channel + groups).
6. REARRANGE, CSV export/import, Copy Settings between channels.
7. Jump to device linking from linked-channel indicators.
8. Create / apply SPEAKER PRESET on the Speaker tab.

Related tutorials

• Channels and groups
• Tuning
• Multi-way channels
• Speaker presets

10.5 - GROUPS

Purpose

Control many speakers as a room or zone. Group parameters sum with each member channel.

Key actions

1. Create groups via MAP | CREATE → + GROUP.
2. Map / unmap member channels.
3. Configure GROUP ABILITIES (which controls the group exposes).
4. Set VOLUME, MUTE, EQ, delay/phase as enabled.
5. Assign INPUT sources and output/channel setup (stereo / surround).
6. Select group-level CROSSMIX overrides when needed.
7. Manage SNAPSHOTS for scene recalls.
8. Apply group SPEAKER PRESET carefully (members inherit unless overridden).

Related tutorials

• Channels and groups
• Everyday control
• Surround input sources

10.6 - CROSSMIX

Purpose

Define and assign matrices that route INPUT SOURCE legs to group output roles when layouts differ (or even when they match).

Key actions

1. Browse strategies; filter by input / output setup.
2. + CROSSMIX to create a custom matrix.
3. Edit crosspoints and gain offsets in the matrix editor.
4. Mark a strategy as global default for an in/out pair (always keep one).
5. Assign overrides on groups or group+input combinations (higher priority).
6. REARRANGE / delete unused non-default strategies.

Related tutorials

• Surround input sources
• Inputs and routing

10.7 - SIG-PATH

Purpose

See how audio is supposed to flow: source → group → channel → device. Useful for verifying routing after INPUT changes.

Key actions

1. Open SIG-PATH.
2. Filter by SOURCE, GROUP, LINKED, UNLINKED.
3. Inspect columns/tabs for group, channel, input, and device relationships.
4. Use TEST / identify controls to confirm the physical path.
5. Jump back to CHANNELS / GROUPS / DEVICES to fix anything wrong.

Standalone per-group URLs exist for integrators — see Group signal path API.

Related tutorials

• Inputs and routing
• Everyday control

10.8 - VIEW

Purpose

Create simplified operator canvases (rooms, mute, volume, meters, images) without exposing the full commissioning UI.

Key actions

1. + VIEW to create a page.
2. Add objects: channel, group, level meter, mute, power, volume, device, group input, image, view link.
3. Arrange with align / distribute / layer tools; optional snap-to-grid.
4. MANAGE IMAGES for background / diagram assets.
5. SAVE VIEW.
6. Copy the operator Link for fullscreen use (/view/...).
7. DELETE VIEW when obsolete; BACK TO LIST to manage many pages.

Related tutorials

• Everyday control
• View API

10.9 - LOG

Purpose

Inspect what Maxx Remote and connected clients recently did when diagnosing failures.

Key actions

1. Open LOG.
2. Search / filter; Apply / Reset.
3. Load older entries when the issue is further back.
4. Export Log for support tickets.
5. Correlate with the navbar warning icon and OUT OF SYNC alerts.

Related tutorials

• Troubleshoot

11 - API

Maxx Remote exposes a few user-facing integration surfaces. This section stays thin on purpose: the live OpenAPI document on a running system is the contract for REST calls.

OpenAPI UI on a running host: http://localhost:8000/api-docs/ (also linked from HOME → REST-API Doc).

11.1 - REST API

Goal / when to use

Drive day-to-day control (levels, mutes, selections) from a media controller or similar. Prefer this over scraping the GUI.

Where is the full reference?

Each Maxx Remote instance ships OpenAPI docs:

• UI: HOME → REST-API Doc
• URL: http://localhost:8000/api-docs/ (replace host/port as needed)

That document is authoritative for paths, payloads, and versions.

Scope

Compared with Maxx Control’s device REST API, this API targets the Maxx Remote project/server — operator-oriented control of the system Maxx Remote manages, not low-level single-device setup.

Related

• API overview
• View API

11.2 - Maxx Remote View API

The Maxx Remote View API exposes a saved VIEW as a standalone operator page — without the Maxx Remote editor chrome. Operator URLs use the /view/ path (also called the View API).

What is the Maxx Remote View API?

Use it when you want tablets or dedicated operator PCs to show only the mute / volume / meter widgets you placed in VIEW, not the full project editor.

How do I open a VIEW operator page at /view/?

1. In VIEW, create and SAVE a page.
2. Copy the operator Link from the editor toolbox.
3. Open URLs of the form:

http://<server>:8000/view/<view-name>

(Exact name encoding matches what the UI copies.)

Expected result

Fullscreen operator canvas with the mute / volume / meter widgets you placed.

Related

• GUI · VIEW
• Everyday control

11.3 - Group signal path

Goal / when to use

Embed or bookmark a SIG-PATH page for one room/group — useful on a monitoring wall.

URL pattern

Groups are addressed by their internal id (UUID), for example:

http://<server>:8000/group-signal-path/<group-uuid>

Example:

http://localhost:8000/group-signal-path/36875a19-8203-4647-9760-303ffd3c8f8f

Obtain the group id from your project/export or integrator tooling — it is not the display name.

Related

• GUI · SIG-PATH
• GUI · GROUPS