This is the multi-page printable view of this section. Click here to print.
| Features | MAXX Remote | MAXX Control |
|---|---|---|
| Single-Channel Control | ||
| Multichannel Control | (per Device only) | |
| Device Settings | ||
| Grouping | ||
| Undo / Redo | ||
| Offline Project Planing |
What we call MAXX-CONTROL is basically a static webpage hosted on each device for easy access out of every web browser. The webpage controls the amplifier by utilizing its fully open REST-API
All function, the devices offers are available via the integrated REST-API.
The API is based on HTTP PUT / GET / OPTIONS / DELETE calls with JSON payload.
Every PUT / DELETE call has to be verified via a “Authentication Token” in the HTTP header. The default token is: “f4005bf8507999192162d989d5a60823”
This documentation is more dedicated as general overview and description how to handle the API. Each device includes the latest API-Documentation with all available calls.
It can be found on the lower right corner of the OVERVIEW page:
It’s an hierarchical REST API with partial resource updates, structured per channel and it’s corresponding resources like DSP / EQ / VOLUME / etc.
That means you can basically update the whole device with up to 32 channels, with a single HTTP PUT call like a HTTP PUT on http://{IP}/rest-api/settings with a json payload containing the requested structure.
On the other hand, update single resources down in the tree is also possible, e.g. http://{IP}/rest-api/settings/channel/1/ampenable
Controlling the volume of several zones, consists of n-channels per device.
Let’s say a Zone consists of channel 1, 2, 3, 11, 12, 13. All volumes can be updated simultaneously by performing: HTTP PUT http://${ip}rest-api/settings/channel with the following payload, value: -10.2 representing the volume of -10.2 dB :
[
{
"channel_id": 1,
"dsp": {
"volume": {
"value": -10.2
}
}
},
{
"channel_id": 2,
"dsp": {
"volume": {
"value": -10.2
}
}
},
{
"channel_id": 3,
"dsp": {
"volume": {
"value": -10.2
}
}
},
{
"channel_id": 11,
"dsp": {
"volume": {
"value": -10.2
}
}
},
{
"channel_id": 12,
"dsp": {
"volume": {
"value": -10.2
}
}
},
{
"channel_id": 13,
"dsp": {
"volume": {
"value": -10.2
}
}
}
]curl -X 'PUT' http://${IP}/rest-api/settings/channel/ \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '[{"channel_id":1,"dsp":{"volume":{"value":-10.2}}},{"channel_id":2,"dsp":{"volume":{"value":-10.2}}},{"channel_id":3,"dsp":{"volume":{"value":-10.2}}},{"channel_id":11,"dsp":{"volume":{"value":-10.2}}},{"channel_id":12,"dsp":{"volume":{"value":-10.2}}},{"channel_id":13,"dsp":{"volume":{"value":-10.2}}}]' Sometimes it can be handy to turn off / on the whole channel equalizer. For this example, use channel 1, 2, 3, 11, 12, 13. This can be done by:
HTTP PUT http://${ip}rest-api/settings/channel
[
{
"channel_id": 1,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 2,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 3,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 11,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 12,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 13,
"dsp": {
"eqenable": {
"value": false
}
}
}
]curl -X 'PUT' http://${IP}/rest-api/settings/channel/ \
-H 'token: f4005bf8507999192162d989d5a60823' \
-d '[
{
"channel_id": 1,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 2,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 3,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 11,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 12,
"dsp": {
"eqenable": {
"value": false
}
}
},
{
"channel_id": 13,
"dsp": {
"eqenable": {
"value": false
}
}
}
]'[
{
"channel_id": 1,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 2,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 3,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 11,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 12,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 13,
"dsp": {
"eqenable": {
"value": true
}
}
}
]curl -X 'PUT' http://${IP}/rest-api/settings/channel/ \
-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": 11,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 12,
"dsp": {
"eqenable": {
"value": true
}
}
},
{
"channel_id": 13,
"dsp": {
"eqenable": {
"value": true
}
}
}
]'All those plugins utilizing the REST-API to aceess a SINGLE device.
Due to the fact that Loxone can only combine either Virtual Inputs or Virtual Outputs in a Template file, two different Templates have to be installed:
It’s totally valid to use only one, depending on your needs.
Download the corresponding .LxAddon Files and install it into your Loxone Config by double clicking or via the Import wizard like:
Both Plugins can be instantiated multiple times, as often as you want to control physical devices.
hostname.local. Leading http:// must pre appended like http://amp1.local or http://10.77.178.20
/rest-api/status is required as well, like http://10.77.150.60/rest-api/status
Download the MAXX-CONTROL.Loxone example file from the Loxone Library
The Template basically provides the following predefined controls:
and some examples of how to create custom commands for improved performance.
Simple digital outputs which can be grouped together in any desired combination.
Similar to Power / Mute Volume will send out any changes for each output as a single http request.
The interesting part here is how to map the common Loxone Analog Values in a range of 0-10 to a dB value for the amplifiers. That can be easily done with the Correction field of each output. The default configuration will map the values of 0-10 to -72dB - +10dB
This will give you almost the full dynamic range of the volume value:
A basic understanding of the REST-API interface is recommended to create those combined commands.
As a starting point, have a look at the three included examples:
Those commands send the same value to multiple channels within a single HTTP request, significantly improving performance when many channels are involved in a call.
Let’s have a look at the HTTP body which is sent out when the DIGITAL OUTPUT is set to ON by clicking on the edit button of that line:
You basically see a JSON payload file containing an ARRAY of single JSON objects for the corresponding channels, indicated by the channel_id tag:
[
{
"channel_id": 1,
"dsp": {
"mute": {
"value": true
}
}
},
{
"channel_id": 5,
"dsp": {
"mute": {
"value": true
}
}
},
{
"channel_id": 7,
"dsp": {
"mute": {
"value": true
}
}
},
{
"channel_id": 30,
"dsp": {
"mute": {
"value": true
}
}
}
]
To modify that, simply duplicate the entries:
{
"channel_id": 1,
"dsp": {
"mute": {
"value": true
}
}
},
for each channel, you want to control and change the channel_id to the desired channel number.
"," after each object, except the last one! Please use any JSON validator to verify the final JSON object before putting it back into Loxone Config
"value": true with "value": false and insert that object into the HTTP body for OFF
Download the MAXX-STATUS.Loxone example file from the Loxone Library
The MAXX-STATUS Template periodically polls the /rest-api/status URL of the amplifier and filters the response for each channel status/device status.
The raw CHxx STATUS value represents the default syslog severity levels like:
| STATUS | Level |
|---|---|
| 0 | EMERGENCY |
| 1 | ALERT |
| 2 | CRITICAL |
| 3 | ERROR |
| 4 | WARNING |
| 5 | NOTICE |
| 6 | INFORMATIONAL |
| 7 | DEBUG |
| 8 | OK |
In combination with the provided STATUS component with the following settings:
An easy virtualization can be achieved.
Combining the Val output of each STATUS component with an OR Gate, a simple GLOBAL STATUS can be generated when any channels or device assert any state higher than NOTICE ( see STATUS settings, State value).
Innosonix GmbH has developed a plug-in to integrate our web based control page for Maxx Series called Maxx Control with QSC Q-SYS Ecosystems.
Innosonix Devices can be added to the Q-SYS Ecosystem with Q-SYS Designer Software. You must be using Q SYS Designer 9.8 or above in order to use this plug-in
Innosonix Devices can then be controlled by Q-SYS Designer, Q-SYS compatible user-controlled interfaces and GPIO logic ports integrated into Q-SYS cores and peripherals.
Innosonix devices must have firmware version V3.19.4 or above installed to be compatible with the Maxx Control Plug-in. If you are unsure what firmware you device is currently using, please download IDFM to help confirm and if need be install up to date firmware.
For further control and processing capabilties of your Maxx Device please download Maxx Remote
Download the Innosonix Maxx Control Plug-in from the Third Party Downloads section of the Downloads section of our website.
Copy the insert name of plug-in here from into the My Documents/QSC/Q-Sys Designer/Plugins Folder
Open Q-SYS Desinger, the Plug-in can be found in the Schematic Elements/Plugins section on the right-hand side of the page:
Drag and drop the Plug-in into your design and select it by clicking once on the Plug-in icon.
Control pins can be enabled by ticking the check-boxes in the “Control Pins” section as required:
Go “Online” with your Q-Sys project. If devices are not connected you can use the “Emulate” function under the “File” tab in the menu above.
Double clicking the Plug-in icon brings up the device interface, select the “Global Tab”, and enter the amplifiers IP address. If you are having trouble find the IP address of your device it will appear on the front screen of your device Alternatively, use idfm to find the IP addressof your device:
The “Global Tab” notifies the user of important information on the Innosonix device including:
Select the “Channels Tab”:
For any more information please visit feel free to Contact us!
Work in progress documentation.
… is, and abstraction layer between devices and just channels. It doesn’t matter if 1000 channel are spread out over 32x 32 Channel amplifiers, or 125x 8 Channel Amplifiers or any other combination.
As a user, you normally don’t want to know on which amplifier channel your speakers are mapped during operation and tuning of the system. The only thing that’s interests is that you want to control this specific channel or a group of channels in a room for example.
MAXX Remote can be used in two different application forms:
In both scenarios, the MAXX Remote system always consists of an SERVER and FRONTEND / USERINTERFACE / GUI part which is general a html webpage controlling the actual server.
The SERVER / Desktop application containing an integrated webserver where the USERINTERFACE is always accessible. Like on your local PC: http://localhost:8000
In MAXX Remote we distinguish between some basic object types:
CHANNELS or PROJECT CHANNELS
Represents a single amplifier channel which holds data for every possible DSP option.
GROUP
Groups can control every parameters the channels offers but will affect multiple channel at once.
DEVICES
Devices represents amplifier in your Project. Each Devices, depending on it’s type, offers a specific channel count like 8, 16, 24, 32.
HW CHANNELS
are those hardware channel, present on devices in your project, like CH1 @ AMP1
CHANNELS could be seen like regular channel strips on an amplifier device itself. That means, you can control this specific channel like you want.
If a CHANNEL is part of one or multiple GROUPS, those groups could also add some values to that channel. Depending on the parameter type, the overall summation of the channel value and all assigned groups will be the final output value of that channel.
| Source | Volume |
|---|---|
| Channel | -2dB |
| Group 1 | -1dB |
| Group 2 | +5dB |
| ________ | _______ |
| OUTPUT | +2dB |
If a CHANNEL is linked to a HW Channel (a channel on an Amplifier device), MAXX Remote will send the CHANNEL values to the device.
Since all channel settings are stored in the database of MAXX REMOTE, it’s easy to exchange a device or even reorder the channel assignment over devices.
Once a CHANNEL is linked to a device, MAXX REMOTE monitors those channel values on the device itself because it’s still possible to directly change channel values via MAXX CONTROL.
If any mismatch in data consistency is detected via the periodical check-in MAXX REMOTE, an OUT OF SYNC warning is asserted, which shows the affected parameters.
It’s the user’s responsibility to resolve those issues by either changing values in the MAXX REMOTE to align with the device or just overwriting the data in the device with those data stored in MAXX REMOTE.
Good part, it’s quite easy!
Just download the application from our webpage
Those applications are portable, which means no installation is required, just start them.
docker run --detach --name maxx-remote --network host innosonix/maxx-remote:latest
The option --network host is not necessarily required, except if you want to use device discovery which is performed on UDP broadcast message on port 9453
If not used, must add Devices manually via their IP address.
Once the Docker Container is running, the integrated web server can be accessed via the IP address of the Docker on port 8000.
When starting the Docker Container without any attached volume, your whole project configuration is stored in the container volume itself.
AND WILL BE LOST once you delete the container or a new one is started
You can manage the project files by downloading/uploading the current runtime configuration when switching to a new container.
The preferable way is to use a dedicated docker volume to store the runtime configuration of the server.
# create a new volume ( only has to be done once )
docker volume create maxx-remote-volume
# start the container and mount the volume
docker run --detach \
--restart always \
--name maxx-remote \
--network host \
--mount source=maxx-remote-volume,target=/root \
innosonix/maxx-remote:latest
Set up a simple demo scenario containing three speakers (Left / Right / Sub) connected to CH 1, 4, and 9 on an MA32/D², doing some equalization and routing music from a Dante Virtual Sound card.
The first time you are going to Start the Maxx Remote, this splash screen appears. Click on Start a new project and type in any name.
Let’s create our three required channels and one group containing all channels.
Finish that by clicking on CREATE CHANNELS
We can use different approaches to supply some music to those channels. But for now, assume a stereo source coming from a Dante Device / Dante Virtual Soundcard.
By using INPUTS in the Maxx Remote, we can specify MONO or STEREO Sources in the Dante network. The required information can be found in the Dante Controller, containing the HOSTNAME and the Transmit Channel name. A Dante Stream will be represented by that combination Transmit Channel@HOSTNAME.
In the example below, 01@STEFFEN-PC
For a basic explanation on how to handle Input Sources, please refer to the corresponding section in the Quick-Start chapter. Here we will have a more in-depth look on all the features regarding Surround audio.
Since there is no uniform naming convention for the additional surround channels (The nomenclature will vary, depending on which resources you refer to), let’s quickly establish which designation in Maxx Remote refers to which speaker in a 5.1 and 7.1 surround setup:
{ width=300px }
{ width=50% }
Creating Surround Input Sources works just as described in the Quick-Start chapter. Naturally, there are a few more channels requiring a RECEIVE LABEL for surround setups.
Since Surround Setups are not just limited to “Left” and “Right” channels, there are now a few more roles available that you can assign to a CHANNEL.
Selecting NONE will result in this CHANNEL not being provided any INPUT SOURCE related Dante Streams at all.
With MONO, a CHANNEL will usually be assigned to all the streams included in an INPUT SOURCE, but more on that later.
“Output-” or “Channel-Setup” is a new setting that has been added to the GROUP overview page. This setting should reflect the kind of speaker setup your GROUP is supposed to control. To guarantee a correct output, all channel-roles included in a surround setup need to be assigned to at least one CHANNEL assigned to this GROUP. Leaving out a necessary role or assigning a role that is not part of your selected output setup won’t throw any errors but will result either in a Dante stream not being assigned to any CHANNEL or in a CHANNEL not receiving any Dante stream.
In real world scenarios, not always will the channel setup of a GROUP and the INPUT SOURCE you assign to it be an exact match. Either your speaker setup might have fewer channels available than your input source would require, or an INPUT-SOURCE requires fewer channels than your speaker setup provides. In the first scenario, you’d have to create a DOWNMIX of all the Dante streams to the available channel roles in case you want all the information included in the source material to be played back on the available speakers. In the latter scenario, you’d have to create an UPMIX in case you want to guarantee that all speakers will always be provided with a Dante stream.
For ease of communication, we combined those two scenarios under the term CROSSMIX.
Maxx Remote will provide a set of predefined default crossmix strategies for all possible combinations of input- and output-setups that you can review and edit on the CROSSMIX page. Of course you can also define and add your own custom crossmix strategies.
Besides the usual text search, at the top of the page you will also find a couple of filters, to quickly limit the displayed crossmixes to the desired input- and/or output-setups.
Crossmix Strategies can be assigned at three levels to combinations of Input- and Output-Setups:
Global Default (lowest priority)
Since for every combination of Input- and Output-Setup there must always be a global default to fall back to. It is not possible to un-default or delete a crossmix strategy currently assigned the role of default. Rather, you’d first have to assign another strategy as default for this combination of Input- and Output-Setup before being able to do either.
For all Input-Setups on a specific GROUP (medium priority)
In case no specific strategy is assigned, the select box will display whichever strategy is globally assigned to this In-/Out combination.
For individual combinations of INPUT-SOURCE and GROUP (highest priority)
In case no specific strategy is assigned, the select box will display whichever strategy is applicable from either of the lower priority levels.
Programatically, a crossmix strategy is always used to determine which Dante streams should be routed to which output channels, not just in cases the input- and output setup do not match. Maxx Remote will check in reverse order (3. - 2. - 1.) to see, which strategy is applicable to the In-/Out combination at hand and distribute the Dante streams accordingly.
On all three levels, you can use the gear icon to open the EDIT view for the selected or applicable crossmix strategy.
The select boxes will only display the crossmix strategies befitting the Output Setup of the selected GROUP and whichever Input Setup is applicable.
