next up previous contents index
Next: Integra modules Up: libIntegra: a system for Previous: libIntegra: a system for   Contents   Index


Introduction

libIntegra is part of the Integra project, a 3-year project led by UCE Birmingham Conservatoire in the UK and part financed by Culture 20001. One aspect of Integra is to develop a new software environment to facilitate composing and performing in the context of interactive and live electronic music. In general, the project attempts to address the problems of persistent storage, portability and standardized intercommunication between different software (and hardware) systems for electronic music. It is a priority that all data relating to supported musical works, including scores, electronic parts, information about different versions and renderings of these works, biographical data, etc., should be stored on a web-accessible database, and that this data should be transferable to a variety of usable target applications.

Integra started as a way of standardising the construction of modules, and providing a generalised OSC namespace within the Max/MSP environment. As such it has similarity with the Jamoma[3]2 and Jade projects3. However, it now differs substantially from either of these in that it has a strong emphasis on software independence, and persistent storage. Two other projects that aim to tackle problems that are similar to those which Integra attempts to address are Faust [1][2]4 and NASPRO5. Furthermore, Integra is closely related to documentation and migration initiatives such as the PD Repertory Project[4], Mustica[5], and the CASPAR Project6, though the scope of the latter is much wider than that of Integra.

The Integra library is being developed as a foundation for the software development aspect of the Integra project. Its purpose is to make it possible to retrieve data (in particular the electronic sound processing part of the piece in question - the Max/MSP or PD patch for example) from the Integra database, and seamlessly load it into the required pieces of software. It is also our mission that it should be possible to load the same 'Integra collection' file (see [*]) in, or redirect parts of it to, a variety of different targets. Once loaded into its given target(s) the module collection will be addressable using a common OSC address space. The library should also support the instantiation of a module collection across multiple target applications for audio and multimedia.


next up previous contents index
Next: Integra modules Up: libIntegra: a system for Previous: libIntegra: a system for   Contents   Index
Jamie Bullock, Henrik Frisk