Dartmouth Symposium on the Future of Computer Music Software: A
Total Page:16
File Type:pdf, Size:1020Kb
Eric Lyon Dartmouth Symposium Bregman Electronic Music Studio Department of Music Dartmouth College on the Future Hanover, NH 03755 USA [email protected] of Computer Music Software: A Panel Discussion Downloaded from http://direct.mit.edu/comj/article-pdf/26/4/13/1853611/014892602320991347.pdf by guest on 23 September 2021 [Editor’s note: This article is an edited transcript field of entertainment, whether film music or the of a panel discussion, moderated by Eric Lyon, at various technology-drenched genres of rap, techno, Dartmouth College in October 2001. See ‘‘About rock, and pop. This Issue’’ on page 1 for more information.] The distinction between experimental music and what might be termed ‘‘normative music’’—that is, Eric Lyon: I think it’s fair to say that without the work of today’s speakers, computer music as we music based on accepted stylistic norms—is mir- know it would not exist. Now that we have them rored in our software. On the normative side of all together, we have an unprecedented opportunity software are utility programs such as mixers, se- both to focus on their individual achievements quencers, and reverberators. On the experimental and to assess the bigger picture of where computer side are the programs that we discuss today. This music software is today and where it might be software is open, extensible, and invariably used in heading. ways unanticipated by its creators. While such soft- At the end of a 1989 comprehensive survey of ware does not command a market on the scale of computer music languages and systems, Gareth normative utility programs, it is arguably much Loy wrote the following: ‘‘It is remarkable how few more influential in the long run, as it facilitates the of the languages and systems documented above creation of the music which today exists only in are generally available.’’ Among the reasons postu- our collective imagination. And the experiments of lated for software’s demise were the obsolescence today will lead inevitably to the norms of tomor- of the host computer system, competition from row. This debt is even occasionally acknowledged, other languages, and discontinuation of support by such as when the Beatles put Stockhausen on the the programs’ creators. This symposium takes cover of their album Sgt. Pepper’s Lonely Hearts Gareth’s observations as a point of departure. But Club Band, or more recently when Radiohead sam- we turn the question around and ask not why so pled (and credited) Paul Lansky on their album Kid much software has disappeared, but why a few ex- A which went platinum. ceptions have been so persistent and have devel- My hope is that this will be a little less like a oped a loyal and even fanatical following among panel discussion and more like a town meeting, computer musicians. given the people in the audience. I am going to In the world of recorded music, which comprises start by asking one or two questions, then open it most of what we listen to these days, the term up to questions from the audience. ‘‘computer music’’ is redundant. The prevalence of I would like to start by discussing various aspects the use of computers in today’s music demands an- of different kinds of software, different specific other distinction; at its outset computer music pieces that we know and love. Perhaps this is more meant experimental music, carried out in laborato- or less about survival paradigms, which is to say ries and universities. This experimental work con- that specific pieces of software and ideas have been tinues here and at many other institutions, but filtered through—have made it through—the 40- most of today’s computer music is created in the odd years of computer music. In particular, we see the ‘‘Music N’’ paradigm represented by the Music Computer Music Journal, 26:4, pp. 13–30, Winter 2002 N environments and of course Csound, and we ᭧ 2002 Massachusetts Institute of Technology. see the graphic layout and connection of signal of Lyon 13 Figure 1. Max Mathews and Jon Appleton. nent can be worked on separately so that you don’t have to keep ‘‘glomming’’ on things to one environ- ment to make them do what you want. David Zicarelli: I don’t know if this is related to what you are asking, but I am currently working on a project to make Csound work inside MSP. It Downloaded from http://direct.mit.edu/comj/article-pdf/26/4/13/1853611/014892602320991347.pdf by guest on 23 September 2021 won’t be ideal, because of the way each program is written, but at least you have a beginning, and it certainly should be possible to do that with other systems. I see two directions for Max: one is that, because the API is relatively simple and well- documented, it should be possible to incorporate other software into it as an object, such as Csound or even the SuperCollider language, and the other thing is that Max/MSP is eventually going to be a library that can be used for the purpose of custom- Max/MSP, and finally we see the pattern-based and izing other software. The first example of this al- syntactical sort of object-oriented idea of Super- ready exists, called Pluggo, which is a runtime Collider. environment for VST plug-ins that can work inside To start our discussion, I would like to ask how a sequencer so you develop software in Max and you feel about the idea of ‘‘software cannibalism’’ then put it in a particular location on your com- and how that may suggest a direction for the fu- puter and open it as a plug-in to process audio in an ture. In other words, now that we have software audio sequencing environment. The same kind of models that are very clear and palpable, it also thing could be true of a Web browser or video ef- seems that we are opening them up and trying to fects program, movie editor, or something like that. grab ideas from other sources and absorb them into So, I am not sure that’s cannibalism, but at least it our languages. is a way that things can work together. Max Mathews: The more the better, because that’s Unfortunately, as any programmer knows, the in- progress as well. I think the model for that is the terface between the two worlds is always where all mathematician, which I believe Miller [Puckette] the action is, and it’s usually where all the bugs is, and mathematicians do not go back to axioms to are, so the impulse of the programmer to do this prove things if possible. They find somebody else’s because it seems easy is usually rewarded many theorem and just continue from there. Of course that imposes rather strong requirements on the times over with incredibly difficult implementa- theorems. They really have to be true under all tion problems. sorts of conditions to not introduce errors into Lyon: Barry, I would be curious to hear your reac- other theorems that depend on them. So if canni- tion, since in a sense, without even attempting to balism is going to be successful, then our algo- do so, Csound by absorbing the music and the rithms have to be very robust with regard to the world around it has necessarily taken in so many environments to which we are going to subject other things. them. Barry Vercoe: Yes, well I guess the secret is to keep James McCartney: Another idea that is the oppo- remaking yourself. And it is not necessarily true site of cannibalism and absorption is deconstruc- that you have to, in an industry analogy, gobble up tion, like the CARL system; and the way I am all the dot-coms in order to survive; you can actu- doing SuperCollider now is to divide things up into ally do your own thinking and grow along particu- their simplest components. That way, each compo- lar lines that are probably consistent. For 14 Computer Music Journal instance, we might say that SAOL is an outgrowth running in Paris. I am not sure if that’s true, but of NetSound, when in point of fact, there are a lot that’s where the genesis seemed to be. of deficiencies in the SAOL structure that I wish Miller Puckette: I have yet to sort it out. It borrows weren’t there. We really did know better than that, from that, but also from the synthesizer idea and but there were reasons why I needed to let a stu- also from RTSKED and who knows—it’s too com- dent go ahead and do something on his own. So it’s plicated to figure it out. Downloaded from http://direct.mit.edu/comj/article-pdf/26/4/13/1853611/014892602320991347.pdf by guest on 23 September 2021 ended up that the SAOL structure is much less effi- Vercoe: Yes, but the fact that David might now cient than Csound, certainly than XTCsound. I consider ‘‘burying’’ Csound inside of Max things is think that if I had it to do over again, I would sim- nicely self-symmetric, I suppose. So it may be self- ply take the XTCsound card away from hand-held cannibalism or something; there is a nice com- devices and put it into MPEG. It would have been pleteness about things like that happening within twice as fast, and what I see happening right now is the community. I think these things are driven by that the sound community is going back and forth the user-created process, by what composers want, trying to get to the bottom of things that have al- what composers need.