Information AboutMusic-n |
| CATEGORIES ABOUT MUSIC-N | |
| domain-specific programming languages | |
| audio programming languages | |
|
MUSIC had a number of descendants, e.g.:
Less obviously, MUSIC can be seen as the parent program for:
All MUSIC-N derivative programs have a (more-or-less) common design, made up of a Library of Function s built around simple signal-processing and synthesis routines (written as Opcode s or Unit Generator s). These simple opcodes are then constructed by the user into an instrument (usually through a text-based instruction file, but increasingly through a graphical Interface ) that defines a Sound which is then "played" by a second file (called the Score ) which specifies notes, durations, pitches, amplitudes, and other Parameter s relevant to the Music al Informatics of the piece. Some variants of the language merge the instrument and score, though most still distinguish between control-level functions (which operate on the Music ) and functions that run at the Sampling Rate of the Audio being generated (which operate on the sound). A number of highly original (and to this day largely unchallenged) assumptions are implemented in MUSIC and its descendants about the best way to create sound on a computer. Many of Mathew's implementations (such as using pre-calculated Array s for Waveform and Envelope storage, the use of a Scheduler that runs in musical Time rather than at audio rate) are the norm for most hardware and software synthesis and audio DSP systems today. |
|
|