This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

GUI reference

Maxx Remote GUI reference — purpose and key actions for each screen (HOME, DEVICES, INPUTS, CHANNELS, GROUPS, CROSSMIX, SIG-PATH, VIEW, LOG).

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.

ScreenPurpose
HOMEProject overview, status, API docs link
DEVICESAmplifiers, connect, sync, link outputs
INPUTSDante / input sources
CHANNELSSpeakers / project channels
GROUPSRooms and zones
CROSSMIXSurround / layout mix strategies
SIG-PATHEnd-to-end signal routing view
VIEWOperator pages
LOGApplication log / export

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

1 - HOME

Maxx Remote HOME screen — project overview, status cards, activity, and REST API docs link.

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.

2 - DEVICES

Add amplifiers, connect, identify, sync, and link hardware channels.

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

3 - INPUTS

Create and manage input sources for groups (typically Dante TX labels).

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.

4 - CHANNELS

Project channels — speakers, DSP, roles, and group membership.

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.

5 - GROUPS

Rooms and zones — grouped control of volume, mute, EQ, inputs, and more.

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

6 - CROSSMIX

Strategies that map input layouts to speaker layouts (upmix / downmix).

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.

7 - SIG-PATH

Visual signal path from sources through groups and channels to devices.

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.

8 - VIEW

Build operator pages with meters and simple controls; share fullscreen links.

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.

9 - LOG

Application log — search, filter, load history, and export for support.

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.