LAWO crystal, Руководство пользователя

Страница: 379 / 459

crystal User Manual Version: 6.6.0/2 379/459
20. Networking Options
20.1.5 Source Replication (via Ember+)
The Ember+ Src Repl element can be used to couple a source between an Ember+ provider and consumer.
Once replicated, all selected parameters will operate in parallel. The replication can be either one-way or bi-
directional. If bi-directional, then if a parameter is altered on one side, the same change is applied on the
opposing side. Note that the source types do not have to match. So, for example, a mono source could be
replicated to a stereo or 5.1 source; in this instance only parameters which match will be coupled.
The replication can affect the following source parameters (according to the options selected in the consumer):
·
Fader (sapphire, sapphire compact and ruby)
·
INP, excluding mic parameters.
·
Other DSP modules: EQ, DYN, LIM, DLY.
To use this feature, there are three parts to the configuration. First, on the consuming device, add an Ember+
Src Repl element to the " EmBER+ " branch of the 'Tree Definition'. A single element can be used to replicate
several sources from the same consumer. If you wish to replicate sources to more than one provider, then add
one
Ember+ Src Repl element for each provider. Next, define the Source parameters on the Ember+
consumer. Finally, define the Source parameters on the Ember+ provider.
Note that:
·
The use of source replication may slow down the system. See Managing the Network Traffic .
·
When using Source Replication, it is recommended that the participating Ember+ providers are
assigned a
Task Priority = Highest .
·
For bi-directional control you must enable the subscript reports on the Ember+ provider.
·
To reduce the volume of network traffic, you can configure uni-directional control by disabling the
subscript reports on the Ember+ provider.
·
Take care not to create a coupling loop - for example, by configuring two parallel Consumer/Provider
paths to the same source!