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

Return to the regular view of this page.

Ember+

Ember+ is an open control protocol used by many broadcast devices, e.g. mixing consoles by Lawo and others. A device that offers its parameters is called a provider, a device that connects to it and reads or changes those parameters is called a consumer.

mAirList can act as both:

  • Ember+ Consumer – connects to an Ember+ provider (e.g. a mixing console) and executes commands when parameters change.
  • Ember+ Consumer (Lawo) – the same, with additional fader start support for Lawo consoles.
  • Ember+ Provider – offers the internal logic states of mAirList as Ember+ parameters, so they can be read and changed by other devices.

1 - Ember+ Consumer

The Ember+ Consumer remote connects to an Ember+ provider (e.g. a mixing console) via TCP/IP, and executes remote control commands when the value of a parameter changes.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Ember+ Consumer (Ember+ category).

Connection

  • Host name or IP and Port: The address of the Ember+ provider. The default port is 9000.
  • Keepalive Interval: If set, mAirList sends keepalive requests in this interval, so that a broken connection is detected and re-established.

The Monitor helps you to find the parameters you are interested in. Check Enable Monitor, then operate the device: Each parameter change is displayed in the list. Double-click a parameter to add it to the command list.

Parameter Tree

The Parameter Tree tab displays the complete parameter tree of the provider, along with the current values. Double-click a parameter to add it to the command list.

Commands

The Commands tab contains the list of parameter changes that mAirList reacts to. Each entry consists of:

  • Parameter: The path of the parameter in the Ember+ tree.
  • Value Condition and Value: A condition for the new value of the parameter: =, !=, <, <=, >=, > compare it to the specified Value, * matches any value.
  • Command: The command to execute when the parameter changes and the condition is met. The variable $VALUE is replaced by the new value of the parameter.

2 - Ember+ Consumer (Lawo)

This interface is a variant of the Ember+ Consumer for Lawo mixing consoles. In addition to the generic parameter commands, it supports fader start and PFL for the players, based on the console’s source names.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Ember+ Consumer (Lawo) (Ember+ category).

The connection settings, monitor, parameter tree, and commands are the same as for the Ember+ Consumer. Additionally, select the console’s Product ID, i.e. the root node of its Ember+ tree.

Players

On the Players tab, select the playlist and player, and enter the Source name of the console source that the player is connected to (leave empty to disable). mAirList monitors the Fader Result Start, Channel On and PFL1 active parameters of that source, and starts and stops the player accordingly.

Options:

  • Automatic PFL switch: The PFL of the source switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

3 - Ember+ Provider

The Ember+ Provider remote turns mAirList into an Ember+ provider: Ember+ consumers (e.g. a mixing console, a broadcast controller, or a monitoring system) can connect to mAirList and read the internal logic states of mAirList, such as the ON AIR state or the states of the players, and receive updates when they change.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Ember+ Provider (Ember+ category).

  • Bind IP: The local IP address(es) to listen on, separated by commas. Leave empty to listen on all network interfaces.
  • Port: The TCP port to listen on. The default is 9000.
  • Read-only access: If checked, consumers can only read the parameters. Otherwise, they can also change them, e.g. to trigger functions in mAirList.

Connections and disconnections of consumers are recorded in the System Log.