The Kyma Language for Sound Design, Version 4.5

Automation
To prevent a controller from ever showing up in the virtual control surface, tell it to display as
#nothing:
!Harm is: (`MIDIController71 displayAs: #nothing).
The global map is always there, invisibly associating Event Values with your external MIDI devices.
When you first get Kyma, the Default map is selected as your global map. To select a different global
map, use Choose global map… in the File menu. ‡
Whatever your current global map may be, you can always temporarily add to it or override portions of it
in a local map. The MIDIMapper Sound has a Map parameter where you can enter the associations that
differ from the global map. These associations apply only to those Sounds to the left of the MIDIMapper
in the signal flow diagram. Anything not overridden in the local map will be specified in the global map.
You can also use a local map to specify controllers that will show up in the virtual control surface only,
without being connected to any external controller. This is especially useful when you have some specific
names that you would like to give the controllers for one specific Sound, but when those controller names
are not generally useful enough to warrant adding them to the global map.
To specify a named controller that will show up in the virtual control surface only (and not be controllable
with physical faders), use the same name for both the Event Value and the Event Source, e.g.
!Freq is: `Freq.
Local maps are also handy for displaying the true value of a fader. In other words, instead of taking the
(0,1) controller and multiplying it by the desired range in the parameter field, you can change the range
of the controller to whatever minimum and maximum value you like. Typically, this is not something
you would want to do in the global map, because the desired range is probably going to be different for
each Sound. So, although you can specify a different range in the global map, it is most often done in a
MIDIMapper.
To specify a range of values for a MIDI controller, use a statement like the following:
!Frequency is: (`MIDIController18 min: 100 max: 1000).
This gives you a fader called !Frequency whose minimum value is 100 and whose maximum value is
1000 controlled by MIDI continuous controller number 18 on the default MIDI channel.
The extra tags specifying channel, range, etc. are not limited to use in local maps. They can also be used in
any new global maps that you design or modify.
In some situations, you might want to automate parameter changes, rather than controlling them by hand
with a MIDI fader or the virtual control surface. There are several ways to accomplish this:
♦ Use a software sequencer to draw the continuous controller functions, and then control the Capybara
from the sequencer.
♦ Use the sequencer to draw the time-varying behavior of each controller, export the sequence as a
standard MIDI file, and read the MIDI file in Kyma.
♦ Use the time functions built in to Kyma.
♦ Use a Sound to control the way the parameter changes over time (in the same way that you might use
an LFO to control a parameter in a modular analog synthesizer).
♦ Use the Script parameter of a MIDIVoice to algorithmically specify how the controller value
changes over time.
♦ Use the AnalogSequencer Sound to generate sequences of note events and controller values.
‡ When you opened the Default map, you may have noticed that there were a couple of other maps in the Global
Maps folder as well. You can make a copy of the Default map, and customize it for whatever MIDI devices you
have in your studio. For example, the PC1600 map is one that we have set up for the Peavey PC 1600 MIDI controller,
and the Lightning map was designed to map the horizontal and vertical movements of the left and right
wands of a Buchla Lightning controller.
48