Text, including the two scores - Columbia University Department of ...

Music Specification Language). JMSL itself is a family of classes that work together to create a structure for timing, scheduling, and launching musical processes. Its base class is MusicJob, which a user extends to contain any programming task while keeping its core properties (the ability to be (Hierarchical
to function within a collection of other Music Jobs, to be launched by itself or simultaneously with other MusicJobs, etc) intact. Another primary JMSL class is MusicShape, which functions as a flexible table for defining discrete musical data parameters and timing. repeated,
defined several low-level MusicJobs that generate trivial musical processes (rising figures, falling figures, drunk walk figures, sustaining figures, I
fill MusicShapes with these figures, and decide to repeat themselves a certain number of times. Outside of these classes, and constantly functioning in the background, is one or more of my class MelodyConstraints, which clamps the generated note data to several constraints: allowable pitch range, etc),
range, minimum and maximum pitch leaps, dynamic range, and adherence or non-adherence to a variable tonal center. The intended large-scale directionality of the musical result is due to the fact that these constraints are gradually changing over time. In fact, at any duration
the constraints are actually gradually interpolating from one (randomized) series of constraints to another. This way, the underlying figures moment,
be repeated many times, but because of the gradual change of the constraints, the post-constraint result will usually be slightly (and, in some cases, drastically) different for each repetition of the underlying figure. At the top level of the program is a ‘voice’, which sequentially launches a
may
4