Final Glossary

Just as in the introduction we gave a brief glossary of the fundamental concepts upon which this Thesis was to be built, we will now summarize the most important ideas also in the form of a glossary. We will give short definitions and refer to the related section in this document.

• CLAM: Acronym for ``C++ Library for Audio and Music''. Audio and music development framework that represents the practical realization of the DSPOOM metamodel. See chapter 3.
• DSPOOM: Acronym for ``Digital Signal Processing Object-Oriented Metamodel''. Abstract metamodel that includes a complete object-oriented approach and a graphical model of computation that can be instantiated to model any digital signal processing system especially in the audio and music domain. See chapter 4.
• Processing Object: Basic building block of a DSPOOM model. It is the object-oriented encapsulation of a process. See section 4.1.1
• Processing Data Object: Object that encapsulates all data in a DSPOOM model offering general services such as a homogeneous interface or passivation/activation facilities. Inputs and outputs to a Processing object are all Processing Data objects (or Controls if the input is asynchronous). See 4.1.2
• Network: Dynamic grouping of Processing objects in DSPOOM. A Network basically contains a list of Processing objects and a list of connections between Ports and Controls. Internal flow control issues are automatically handled. See section 4.1.3.
• Processing Composite: Static grouping of DSPOOM Processing objects. In a Processing Composite class the developer defines the internal behavior and flow control issues. See section 4.1.3.
• OOCTM: Acronym for Object-Oriented Content Transmission Metamodel. Following this abstract model, information transmission can be seen as a sequence of the following processes: analysis, understanding, encoding, transmission, decoding, interpreting and synthesis. See chapter 5.
• Content: Any semantic information contained in a signal that can be interpreted by the targeted user. See 5.1.1
• Sound Object: A Sound Object is considered to be any entity in a sound system. Following the DSPOOM metamodel Sound Objects can also be classified into Processing Sound Object such as Instruments or Generators and Data Sound Objects such as Tracks or Notes. See section 5.1.2.
• Semantic Transmitter: Transmitter that, in the OOCTM, is in charge of analyzing, understanding, encoding and transmitting the content in a signal. See section 5.2.1.
• Semantic Receiver: Receiver that, in the OOCTM is in charge of receiving, decoding, interpreting, and synthesizing the transmitted content into a signal. See 5.2.2.
• Content-based Analysis: Multi-step signal analysis in which the goal is to extract content description. See 5.3.3.
• Content-based Transformation: Signal transformation that addresses the content-level by offering the user semantically meaningful control. The basic scheme is based on an analysis-synthesis process derived from the OOCTM (see 5.3.4).
• Instrument Object: Music object that receives input controls in the form of music events and maps them into Generator controls. See 6.1.
• Generator Object: A Generator is the minimum entity in an Instrument capable of producing sound by itself. See 6.1.
• Note Object: A musical Note is defined as a sound object that has a precise and explicit active lifespan (i.e. the note duration), a certain loudness, an optional pitch and other optional attributes. A Note Object is actually a placeholder for a Generator state and can be directly synthesized into audio. See 6.2
• MetriX: Framework that provides an implementation of the Object-Oriented Music Model and offers two languages: the MIDL and the MSDL. See section 6.4.
• MIDL: MetriX Instrument Definition Language. Language for describing an Instrument subclass behavior by specifying its Generators, Timbre Space and Parameter mappings. See 6.4.2.
• MSDL: MetriX Score Definition Language. Language for describing a musical score as a sequence of time ordered events. See 6.4.3.
• MetriXML: Implementation of MetriX in the CLAM framework, mapping concepts to DSPOOM metaclasses and obtaining XML representation for free.