schedulek
Adds a new score event.
Syntax
schedulek knsnum, kwhen, kdur [, kp4] [, kp5] [...]
schedulek "insname", kwhen, kdur [, kp4] [, kp5] [...]
schedule kPar[]
Performance
knsnum -- instrument number. Equivalent to p1 in a score i statement. knsnum must be a number greater than the number of the calling instrument.
“insname” -- A string (in double-quotes) representing a named instrument.
kwhen -- start time of the new event. Equivalent to p2 in a score i statement. kwhen must be nonnegative. If kwhen is zero, insum must be greater than or equal to the p1 of the current instrument.
kdur -- duration of event. Equivalent to p3 in a score i statement.
kPar[] -- event parameters as a k-rate array.
kp4, kp5, ... -- Equivalent to p4, p5, etc., in a score i statement. The opcode also accepts strings as arguments for p4-pN.
schedulek adds a new score event. The arguments, including options, are the same as in a score. The kwhen time (p2) is measured from the time of this event.
If the duration is zero or negative the new event is of MIDI type, and inherits the release sub-event from the scheduling instruction.
Examples
Here is an example of the schedulek opcode. It uses the file schedulek.csd.
A musical example featuring the schedulek opcode: Schedulek_Heintz.csd by Joachim Heintz.
See also
Credits
Author: John ffitch
University of Bath/Codemist Ltd.
Bath, UK
January 2020