Control Sources
Control Sources
25-1
Chapter 25
Control Sources
Control Sources
Control sources are assigned as values for control source parameters, like Src1 and Src2, Depth
Control for Src2, and LFO rate control. Assigning a control source to one of these parameters is
like connecting control source outputs to various inputs on early modular synthesizers. You
can think of each control source parameter as the input to a synthesizer module, and the values
for those parameters as the outputs of modules generating control signals.
For the control sources to have an effect, two things have to happen. First, the control source
must be assigned as the value for (patched to) a control source parameter like Src1. In other
words, for a control source parameter to have an effect, it must be programmed to respond to a
particular control message. Second, the control source must generate a signal. The level of the
control sourceÕs signal determines how much effect it has on the control source parameter to
which itÕs assigned.
In terms of generating signals, there are two types of control sources. The Þrst, which might be
called hardware control sources, require some physical movement to transmit them. The
control source called MWheel (MIDI 01) is probably the most prominent example of this type of
control source. When you move your MIDI controllerÕs Mod Wheel, it sends a Modulation
message (MIDI 01), unless youÕve programmed it to send something else. By default, when the
K2vx receives a MIDI 01 message, it responds by sending a control signal to whatever control
source is assigned as the value for the ModWhl parameter on the MIDI mode RECV page. Of
course, you can program the Mod Whl parameter to send any available control source signal in
response to MIDI 01 messages.
Some of these hardware control sources have physical controls Òhard-wiredÓ to transmit them.
That is, there are certain physical controls that
always
generate these control signals. Every time
you strike one of your MIDI controllerÕs keys (or pluck a string, or whatever), for example, a
Note on message is generated, along with an Attack velocity message. So any time you strike a
key, any control source parameter that has AttVel assigned as its value will be affected by the
Attack velocity message. Similarly, every time you move the physical Pitch Wheel, a PWheel
message is generated. Whether this affects anything depends on whether you have assigned
any control source parameters to respond to the PWheel message (in other words, whether any
control source parameter has PWheel assigned as its value).
On the MIDI XMIT page (and in the Setup Editor) youÕll Þnd six parameters that correspond to
the standard physical controls found on many keyboard controllers: Mod Wheel, Foot
Switches 1 and 2, the Control Pedal (CPedal), the Controller Slider (Slider), and mono pressure
(Press). As long as the LocalKbdCh parameter on the RECV page in MIDI mode matches the
transmit channel of your MIDI controller, these parameters will always respond to speciÞc
MIDI control messages: ModWhl always responds to Modulation messages (MIDI 01); FtSw1
always responds to Sustain (MIDI 64); FtSw2 always responds to Sostenuto (MIDI 66); CPedal
always responds to Foot (MIDI 04); Slider always responds to Data (MIDI 06); Press always
responds to mono pressure.
The values you assign for these six parameters determine which control messages will be
transmitted to the K2vx and to its MIDI Out port when you move the corresponding controls
on your MIDI controller. If you look at the MIDI XMIT page, youÕll see that the parameter
called ModWhl has a default value of MWheel. You can interpret this as follows: ÒMoving the
Mod Wheel on my MIDI controller sends the MWheel (Modulation, MIDI 01) message to the
To Next Page
Loading...