Revox Multiuser System

The setup of the speakers is done first using the Revox App. Then, the connected devices are automatically recognized. Each device is assigned its own ID, starting at 100. If a device is removed, the ID will remain reserved in the background.

The Multiuser System 2.0 and 3.0 are supported. In version 3.0, all zones are also displayed. The assignment of the zones is done via Revox App or with the following commands:

[zonen-id]:zone-owner:[raum-id]:on
[zonen-id]:zone-owner:[raum-id]:off

Important Notes

There are several things to consider when configuring Revox. If these instructions are not followed, unexpected problems may occur.

  1. Each alias can only be defined once, even for sources.
  2. The names and aliases must not exceed a maximum length of 16 characters.
  3. The name of an alias must not contain the character :.
  4. The interface only finds devices that are actually available.
  5. If settings on the Revox side are changed, a re-import or the Search for Devices of the Installation by Antcas Control is recommended. This can also be triggered by a restart of the Revox Server.

Create Channels

In the Device Structure, Channels can be created. For these to be created, various prerequisites must be met.

Types Prerequisite
Speakers The device must be visible in the structure.

Functionality

Unlike the "normal" Revox Action Server interface, all variables are transmitted bidirectionally here. In addition, the WebSocket protocol is used to obtain all information.

Every state of a source or user is automatically distributed to all corresponding rooms. This also applies to sending values. It may happen that a signal for an amplifier is not sent if it is turned off because no source or user is assigned.

Note: The seamless support for forming zones via PLC is not implemented. These are to be formed in the Revox Multiuser App configuration. However, zones can be used instead of rooms.

Variables

The following variables are available in the room. It is recommended to use the variables of the respective room to control the system via visualization.

Variable Values Description
power TRUE/FALSE Player on/off
play TRUE/FALSE Play/Pause
next TRUE Next Track. Switching occurs on a positive edge. This command is not always available.
prev TRUE Previous Track. Switching occurs on a positive edge. This command is not always available.
repeat TRUE/FALSE Repeat All. This command is not always available.
seek 0..# Seek in the track in milliseconds. Available from Multiuser 3.
shuffle TRUE/FALSE Play Randomly. This command is not always available.
volume 0..255 Volume in percent is converted.
mute TRUE/FALSE Mute
balance -10..10 Set balance for stereo speakers.
bass -12..12 Bass from -12 dB to +12 dB
treble -12..12 Highs from -12 dB to +12 dB
user User Assignment of a user. All names (without $-prefix) are located in the interface under Users. The respective alias is used here.
source URI URI to the current source.
cmd RAW RAW command to the corresponding device.
Corresponds to $r.room:RAW
!cmd RAW Like cmd, but all telegrams are sent. This is useful for many commands.
cover_url URL URL to the album cover.
duration 0..# Duration of the track in milliseconds. Available from Multiuser 3.
infotext Multi-line info text. This can be separated with the Function Block EXPLODE. Always 3 lines are transmitted.

Source

The source source consists of the source name and the service (stream). It should later be possible to store more complex paths in order to directly address a file or radio station.

The name is structured as follows:

$s.xx://radio

If the user stream is equal to the current user, the following is returned:

radio

The following commands are possible:

Value Description
$.xx://radio Selects the source $.xx and sets it to Radio.
$.xx:// Selects the source $.xx
radio Sets the current stream to Radio. The source is switched to the user stream.
://radio Same as above.
fav/01 Reference to a favorite in the user's favorites list.

Note: It is always attempted to turn on the player or the user when changing the source.

Sending Commands

To send one or more commands, the variable cmd is used. This command can also be found in individual users, rooms, etc. For example, if a room command is sent, the prefix from the room is automatically added.

Note: Antcas Control does not have collision management when sending a value to this variable simultaneously. If the interface is waiting or restarting, only the last state is sent.

It is possible to send multiple commands in sequence. This is implemented with a new line or the character ;. This ensures that the commands always have the same order.

The following command was sent to room100.cmd:

room:on
stream:spotify

This generates the following command on the Revox Action Server:

#RXXXXXXXXXXXXX:room:on; #RXXXXXXXXXXXXX:stream:spotify

Use Revox Graphics

There is the possibility to directly use graphics from Revox. For this purpose, the value must be transferred to the visualization element image.

Graphic Value
Revox Logo "_revox_logo"

Template

The following template can be used to communicate with a room. The template has the following functions:

  • Selection of users and various sources.
  • Automatic shutdown after 5 minutes if the room is not used.
  • Automatic activation of the room when Play is clicked.
  • Volume display is shown as an attenuation value.
  • Revox Logo is used when the room is not in use.
  • International translation.
  • Compatible with Channels.

It should be noted that various settings need to be made. These are usually as follows:

  • The user list needs to be adjusted.
  • Set maximum volume in the PLC and visualization.
  • With M51, the equalizer cannot be used directly.
  • Adjust or hide the favorites list.

Download: