crystal User Manual
Version: 6.6.0/2
382/459
20. Networking Options
20.1.6
Ember+ Elements
To publish other parameters, you must add one of the following Ember+ elements to the 'Tree Definition'. Please
follow the links below for more information.
·
- can be used to exchange GPIO signals with another Ember+ device. Each element
provides 32 GPIs + 32 GPOs + 8 input/output levels.
·
- the next three elements can used to trigger
source or summing bus Ember+ parameter values, and report back their status.
·
- allows another Ember+ device to control crosspoints within crystal.
·
Ember+ Orban
and
Ember+ R3LAY
- the next two elements allow parameters to be exchanged with
Orban's audio codec and Lawo's R3LAY (formerly known as Jade). The setup works in a similar
manner to the
·
Ember+ RAVENNA
- can be used to publish RAVENNA parameters.
·
- can be used to couple a Source between another Ember+ device and crystal. Once
replicated, all selected parameters will operate in parallel.
·
- allows crystal to control presets within a Lawo V_pro8.
20.1.7
Managing the Network Traffic
When a connection is first made between an Ember+ consumer and provider, the amount of network traffic
may be large, as all published parameters are transmitted.
From here on, only parameter changes are transmitted unless the connection is lost.
To increase the priority of Ember+ data, you can change the
Ember+ consumer.
If you are using
, then this will increase the volume of network traffic. The most
traffic will be caused by bi-directional control. To reduce the volume, you can configure uni-directional control
by disabling the
