gestural alternative – music with the body
I’ll try to give an answer to these questions later on in my talk, from the point of view of music technology.
Music as memory – from the perspective of music with technology the challenge is to allow music to become memory in the first place. Preservation of interactive, real-time, live electronics works is a daunting task that has to be tackled in a novel way.
[If we look at electroacoustic music, the situation is comparatively quite good. Once the original analogue supports have been converted to digital, preservation is ensured. True, the passage from analog to digital is difficult, and many works from the 50s and 60s where conceived with the idiosyncrasies of early recording, mixing and diffusion equipment in mind [another exemple of non-neutral technology!]. Those peculiarities became an essential part of the work, as it has been shown time and again in the works of Berio, Stockhausen, Schaeffer, etc.]
To get back to live electroacoustic music, as we should call live electronics, the obvious problem is the longevity of technologies, hardware and software, their rapid change, the commercial, hence temporary, nature of many of the devices used and the overall lack of documentation from the composers and interpreters. To maintain a piece using obsolete technology is very difficult, sometimes downright impossible. If a piece is not performed anymore, then it ceases to be an active agent in cultural and music life. This is too bad.
The role of the research centres
IRCAM – it has certainly helped to shape the contemporary music scene, and its contribution cannot be played down. Boulez managed to create something that lasted and thrived for many years, expanding in more directions as time went by. If we compare this with the UK experience or the Italian experience, for example, IRCAM has been an outright success. In the UK, the efforts to create a National Centre for Electronic Music were never taken seriously by the government, and in Italy, a place like the Centro Tempo Reale in Florence, founded by the late Luciano Berio, never took off properly, and was widely regarded to be just Berio’s own technology plaything – of course this says more about the difference in character between the two composers (Boulez and Berio) than about local obstacles to achieve a similar goal.
IRCAM, nevertheless, as a growing big institution has suffered from many organisational and structural problems, that have become often artistic problems, like the establishment of an IRCAM style that can be quickly recognised – again, technology, the means of producing music with technology, are never neutral, but they affect every aspect of the creative compositional process.
Computers are not neutral tools. Software and hardware impose their own architecture. As any composer that works with technology will tell you, when you are working on a new piece and sit down at the computer to do any of a number of things (analyse, design, edit and mix sounds, prepare your own compositional material by using algorithms, note generators, etc., put together your performance environment and so on), your frame of mind changes, and you have to adapt and limit your thought processes to those that the machine, the software you’re using will allow. It is all very well to say that if you need to alter the software you are interacting with, or if you are unhappy with it you can modify or write your own – in practice you can’t transform yourself in a programmer – apart from the vast amount of time that would be needed, if you do it you will need to distance yourself even more from your musical mind, the one that initially triggered the need.
So again, technology is not neutral. And if a composer works on the technology with a musical assistant, this creates another layer between the musical mind and the machine, another constraint. (Critique of IRCAM) At IRCAM and elsewhere, the main policy has been for many years to support composers through musical assistants, acting as a filter between the composer and the machine. It is no wonder that the software developed at IRCAM has never reached the simplicity of use, the fluidity that one would expect from an institution with such great minds and resources behind it. The maintenance and documentation of the software has also been always very patchy. Obviously a pachydermic institution like IRCAM has a built-in inertia that makes change difficult, but creating simple tools for musicians has never been one of the IRCAM’s priorities.
Maintenance and preservation are also thorny issues. We are trying to find a possible solution to these issues with the Integra project.
Technology is the beast. From a philosophical standpoint, music technology offers a very exciting challenge: artists working with computers, altering the code, hacking it, to realise things that were not planned by the software designers, fulfill the historical role of art: disrupting received knowledge, reordering, reassembling the symbols and objects of our society in an original, critical way. But can we apply to technology the same concepts that worked for art in the past? I doubt it.
Technology is so embedded in our lives, but we still feel the distance from it. It’s here but it’s not here. We think we have the philosophical tools to dominate it, to explain and describe technology, but in reality we don’t. Technology is a self-feeding monster, what can be realised will be realised. There is no goal in technology, no purpose, everything is outside our human horizon of meaning. We are now learning to find a new vocabulary to deal with this monster, but it is early days.
Technology has no memory, Technology has no meaning. Why technology in music? We have to humanise it, and adopt standards. The fundamental issue with technology lies in its unlimited potential and its self-replicating nature: technology is inherently meaningless. If we are going to use it in music we will have to ask ourselves some hard questions. Why do we need it? How can it be musical? How can it be controlled? In order to be harnessed, technology should be brought back to a human dimension, and considered just like another musical instrument – a polymorphous one, to be sure, but still an instrument – that we can learn and play. To achieve this, we should simplify music technology, and to establish a standard vocabulary to describe it.
The word “standard” is often disliked, but we should not forget that the musical instruments employed in our concerts are themselves “standard”, in fact quite limited ones: nevertheless, they allow the transmission of an extremely complex and diversified musical message.
Integra is not alone in this effort towards more user-friendly technology, although it is only recently that usability, good interface design and a preoccupation for how humans operate have started to appear in technology products. Sadly, as far as the history of music technology is concerned, we are still living in the colonisation phase. I like to compare our current experience with the Wild West: new territories are conquered every day, there are no common laws, survival depends from individual initiative. And we are all still digging in search of that elusive gold mine.
This explains the proliferation of do-it-yourself systems over the past three decades, when each work, even by the same composer, required a different technological setup (hardware, software, or both). The often-poor documentation of the electronic parts and the rapid obsolescence of the original hardware and software have prevented the adoption of a core repertoire of works using live electronics in mainstream concert programmes.
Design – usability = make it simple! We need to trade the technological DIY approach (temporary, non-standard, often undocumented) with a user-centered approach, to ensure more performance opportunities and long-term preservation. Standards and limitations in technology can be an incentive for creativity.
Integra environment outline
Integra namespace – class hierarchy describing all the modules, parameters and functionalities, including time. Built-in inheritance. Everything is an object. The namespace is OSC-compliant for interaction with other software, network performance, etc., but not internally. OSC is one of the possible implementation of the Integra namespace model.
Database [postgres sql]
•Integra modules [the building blocks of the system]
•Composition metadata [documentation on the work, the composer, the technical setup, etc.]
•Composition performance data [control and audio network and signal flow, behaviour in perfomance]
All data is encoded in XML format. All the XML files that constitute a work can be downloaded and will automatically generate modules and connections in the GUI.
GUI [any graphic library, prototype realised with Max/MSP using custom graphic library]
•interface for the musician, fine-tuned for the three main modes of utilisation: composition, rehearsal, live performance
•modular and powerful: everything is an object, every object can interact withj everything else
•uses new paradigms to represent concurrent timelines [Iannix]
•generates xml files
•talks to the engine in real-time
•visualizes processes in real-time
Engine [any DSP application supporting the Integra namespace]
•runs Integra modules