/ Examples / Control / CCRelayer

Wherein you'll learn how to relay control events.

Right-click to copy this example to your workspace.

CCRelayer

CCRelayer is a simple but handy node to help distribute control events to downstream nodes. It acts as both an event switch as well as a event broadcaster. It its role as switcher, there are a few caveats with respect to the timing of the switch. If a port-switch occurs between NoteOn and NoteOff events:

• it's possible that a note will become stuck.
• it's possible that CC (MPE) events will get detached from their associated note.

The remedy to this problem is to time the switching of control streams when a stream is "quiet".

Controller is the port where you connect one or more control-event sources.

RelayTarget selects which output port(s) should receive the events.

• None mutes all control events.
• All distributes all control events to all downstream receivers.
• Ctrl0-Ctrl3 nominates one of the output ports as active. Only nodes that are downstream from the selected port will receive control events.

Routing allows you to create a routing table to more precisely characterize the transfer of inputs to outputs. Please see Looper example for more.

Remap allows you to connect Remapping nodes to modify the input values prior to relaying them.

The Example

In this example we have two Relayer nodes. RelayNotes conveys the notes generated by Euclid to either Stk FrencHrn or to Stk Flute. RelayPan conveys the control signals produced by Pan, a CCGenerator node to either Chan0 or Chan1.

At the heart of matters is the Target node that is sending the control event, RelayTarget, to periodically switch ports for both RelayNotes and RelayPan. Since Debug is enabled for that node you can see the CC value in the Log as they are emitted.

The TimeKeepers_ role is merely to put an end to the session (after 12 bars). You'll note that in this example we indeed do experience the stuck note phenomenon.