Maxx Control on Innosonix Docs

Maxx Control REST: Set channel names

Mon, 01 Jan 0001 00:00:00 +0000

Use the Maxx Control REST API to get and set channel names so zones and automation UIs stay readable. Names can contain alphanumeric characters, spaces, and special characters.

Get Channel Name

Retrieve the current name of a channel:

curl -X 'GET' http://${IP}/rest-api/settings/channel/1/name

{
 "value": "Living Room Left"
}

Set Channel Name

Set or update the name of a channel. Channel names can be up to 256 characters and support:

Maxx Control REST: Control device mute and volume

Mon, 01 Jan 0001 00:00:00 +0000

Use the Maxx Control REST API to set device-level master mute, master volume, and startup mute on one amplifier. These controls affect all channels globally — useful for emergency mute, master volume, and safe startup behavior.

Device Mute

The device mute acts as a master mute that affects all channels, regardless of individual channel mute settings.

Get Device Mute State

curl -X 'GET' http://${IP}/rest-api/settings/device/dsp/mute

{
 "value": false
}

Set Device Mute

curl -X 'PUT' http://${IP}/rest-api/settings/device/dsp/mute \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '{
 "value": true
}'

curl -X 'PUT' http://${IP}/rest-api/settings/device/dsp/mute \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '{
 "value": false
}'

Device Volume

The device volume acts as a master volume control that affects all channels. Individual channel volumes are relative to this setting.

Device Information

Mon, 01 Jan 0001 00:00:00 +0000

Getting Device Information

The device information endpoint provides details about your amplifier model, available channels, installed options, and hardware features.

Get Device Information

Retrieve all device information with a simple GET request:

curl -X 'GET' http://${IP}/rest-api/info/device

{
 "model_name": "MA32D",
 "channel": 32,
 "options": ["IF1", "IF2", "D1", "D2"],
 "psu_fan": true,
 "housing_fan": true
}

Understanding the Response

model_name: The amplifier model (e.g., MA32D, MA32LP, MA24D2)
channel: Number of available channels (16-32)
options: Array of installed options:
- IF1, IF2, IF3: Interface options
- D1, D2, D3: Dante options
- M1: Additional options
psu_fan: Whether PSU fan is installed
housing_fan: Whether housing fan is installed

This information is useful for:

Maxx Control REST: Enable or disable EQ

Mon, 01 Jan 0001 00:00:00 +0000

Use the Maxx Control REST API to enable or disable channel EQ (eqenable) — bypass the whole equalizer for testing or mode changes while keeping filter settings intact.

Enable EQ for Multiple Channels

Enable the equalizer for multiple channels in a single request:

curl -X 'PUT' http://${IP}/rest-api/settings/channel/ \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '[
 {
 "channel_id": 1,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 2,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 3,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 }
]'

[
 {
 "channel_id": 1,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 2,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 },
 {
 "channel_id": 3,
 "dsp": {
 "eqenable": {
 "value": true
 }
 }
 }
]

Disable EQ for Multiple Channels

Disable the equalizer for multiple channels:

micro MAXX series

Mon, 01 Jan 0001 00:00:00 +0000

micro MAXX (MICRO MAXX series) is Innosonix’s compact DSP amplifier family: GaN power stages, onboard loudspeaker management, and flexible Audio over IP (Dante / AES67). Models share the same small chassis and the same control stack as other MAXX amplifiers.

Same software as other MAXX amps

micro MAXX devices expose the same Maxx Control webpage and device REST API, and have full Maxx Remote support. Commission network and firmware with IDFM first — same path as larger MAXX chassis.

Mute Control

Mon, 01 Jan 0001 00:00:00 +0000

Channel Mute Control

Mute control allows you to silence individual channels or the entire device.

Get Channel Mute State

Check if a channel is currently muted:

curl -X 'GET' http://${IP}/rest-api/settings/channel/1/dsp/mute

{
 "value": false
}

Mute a Single Channel

Mute a specific channel:

curl -X 'PUT' http://${IP}/rest-api/settings/channel/1/dsp/mute \
-H 'Content-Type: application/json' \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '{
 "value": true
}'

{
 "value": true
}

Unmute a Single Channel

Unmute a specific channel:

REST API

Mon, 01 Jan 0001 00:00:00 +0000

Every amplifier exposes a hierarchical JSON REST API used by Maxx Control itself and by third-party systems. Prefer this API for single-device integration. For project-level multi-amp control, use the Maxx Remote HTTP API instead.

Base URL and transport

Item	Value
Scheme / port	`http://` on port 80
Base path	`/rest-api`
Example	`http://${IP}/rest-api/settings/channel/1/dsp/mute`

Methods you will use most: GET (read), PUT (write / partial update), OPTIONS (allowed ranges and constraints), plus POST / DELETE on a few resources (for example EQ bands).

Volume Control

Mon, 01 Jan 0001 00:00:00 +0000

Channel Volume Control

Volume control is one of the most common operations. You can control individual channels or multiple channels at once.

Get Channel Volume

Retrieve the current volume setting for a specific channel:

curl -X 'GET' http://${IP}/rest-api/settings/channel/1/dsp/volume

{
 "value": -10.5
}

Set Single Channel Volume

Set the volume for a single channel. Volume range is -72.0 dB to +24.0 dB:

AES67 / SDP subscribe

Mon, 01 Jan 0001 00:00:00 +0000

Subscribe an amplifier channel DSP patch to an external AES67 / SDP audio source. This is the same path Maxx Control’s channel-input UI uses when you paste SDP or pick a discovered AES67 flow.

When to use

Use this when a third-party sender (PipeWire, another AES67 device, etc.) publishes an SDP session and you want a MAXX channel to receive that multicast/unicast RTP stream as its input source AES67 STREAM (source_id 25).

Maxx Control REST: Switch input patches

Mon, 01 Jan 0001 00:00:00 +0000

AES67 / SDP

To subscribe a channel to an AES67 / SDP stream (source_id 25), see AES67 / SDP subscribe.

Use the Maxx Control REST API to switch channel input patches (for example Dante slots) with a bulk PUT or per-channel calls. When switching between inputs, there are multiple approaches:

Changing the Input Patch itself

Example Configuration for CH1, CH2, CH4, CH7, switch between Dante Input 1-4 and Dante Input 21-24

Maxx Control (MaxxControl)

Mon, 01 Jan 0001 00:00:00 +0000

Maxx Control (also written MaxxControl) is the control surface built into every Innosonix amplifier: a browser web UI plus an open REST API on the device. Use it for one amplifier when you want local control with no desktop install, or when a media-control / home-automation system should talk to a single amp. That includes micro MAXX — same webpage and API as other MAXX models. For many amplifiers, rooms/groups, and offline projects, use Maxx Remote instead.

Software

Mon, 01 Jan 0001 00:00:00 +0000

Always start with IDFM (install) to set IP and firmware on all devices.

On this site, Maxx Control docs focus on the device REST API and third-party plugins; the full on-device UI manual is published separately (see downloads).

These tools apply to the MAXX family including micro MAXX (same Maxx Control webpage/API and full Maxx Remote support).

Features	MAXX Remote	MAXX Control
Single-Channel Control
Multichannel Control		(per Device only)
Device Settings
Grouping
Undo / Redo
Offline Project Planing

Basic device setup in the network → IDFM (install)
Single device without much need to constantly change settings of multiple channels → Maxx Control
Head start without any additional installation? → Maxx Control
More than one device? Recommendation → Maxx Remote

Amp enable

Mon, 01 Jan 0001 00:00:00 +0000

Power-enable a channel amplifier stage (distinct from mute):

PUT /settings/channel/{channel_id}/ampenable

curl -X PUT "http://${IP}/rest-api/settings/channel/1/ampenable" \
 -H "token: f4005bf8507999192162d989d5a60823" \
 -H "Content-Type: application/json" \
 -d '{"value": true}'

Use "value": false to disable. Multi-channel updates can go through PUT /settings/channel with ampenable on each object.

Save / persist

Mon, 01 Jan 0001 00:00:00 +0000

Runtime changes are held until they are saved. Trigger a manual save with:

PUT /settings/save (token required; no JSON body)

curl -X PUT "http://${IP}/rest-api/settings/save" \
 -H "token: f4005bf8507999192162d989d5a60823"

Check save / autosave state with GET /status/save.

Note

The device may also autosave. Integrators that change many parameters in a burst should still call /settings/save when a persistent result is required (power cycle / reboot).

Third Party Plugins

Mon, 01 Jan 0001 00:00:00 +0000

These plugins use the device REST API to control one amplifier each. For multi-amp project control, use Maxx Remote instead.

Loxone Maxx Control plugin

Mon, 01 Jan 0001 00:00:00 +0000

Loxone integrators can control one Innosonix amplifier via Maxx Control using the Loxone Library plugins and example templates. Install the add-ons into Loxone Config, point each instance at the amp IP (or hostname.local), and drive mute, volume, and status over the device REST API.

What is the Loxone Maxx Control plugin?

The Loxone Maxx Control integration is a set of .LxAddon plugins from the Loxone Library that talk to a single amplifier’s Maxx Control REST API. Instantiate a plugin once per physical device.

Q-SYS Maxx Control plugin

Mon, 01 Jan 0001 00:00:00 +0000

Q-SYS integrators can control one Innosonix amplifier via Maxx Control using the Innosonix Maxx Control plug-in for Q-SYS Designer. Add the plug-in to your design, enter the amp IP, and expose mute, volume, meters, and status to Q-SYS UCIs and logic.

What is the Q-SYS Maxx Control plugin?

Innosonix provides a plug-in that integrates Maxx Series amplifiers (Maxx Control) with the QSC Q-SYS ecosystem. Devices can then be controlled from Q-SYS Designer, Q-SYS compatible user-control interfaces, and GPIO logic on Q-SYS cores and peripherals.