Case Study 13 Final Report: Obsessed Again...

Transcription

1 Title: Case Study 13 Final Report: Obsessed Again... Status: Final (public) Version: 2.0 Submission Date: February 2004 Release Date: September 2007 Author: The InterPARES 2 Project Writer(s): School of Music, The University of British Columbia Project Unit: Focus 1 URL: ip2_cs13_final_report.pdf

2 Table of Contents Report Version History... ii A. Overview... 1 B. Statement of Methodology... 1 C. Description of Context... 1 Provenancial... 2 Juridical-administrative... 2 Procedural... 2 Documentary... 2 Technological... 2 D. Narrative Answers to the 23 Core Research Questions... 3 E. Narrative Answers to Applicable Domain and Cross-domain Research Questions Policy Cross-domain Description Cross-domain F. Selected Bibliography G. Glossary of Terms H. Preliminary Models Appendix 1: Towards a Strategy for the Preservation of Electroacoustic Music InterPARES 2 Project, Focus 1 i

3 Report Version History Date Version Notes Individual 18 Feb Final report Scott Amort 29 Aug Revised final report Randy Preston 29 Sep Revised final report Scott Amort 23 Sep Final copy editing, addition of Appendix 1 Randy Preston InterPARES 2 Project, Focus 1 ii

4 A. Overview Obsessed Again... is a work for bassoon and interactive electronics written in 1992 by Canadian composer Keith Hamel. The work was composed to fulfil a commission from bassoonist Jesse Read, who requested a piece involving interactive electroacoustic elements, and was premiered on May 9, 1992, at De IJsbreker, Amsterdam, the Netherlands. The work realized these interactive elements by utilizing the Max music software environment along with a commercial Proteus 1 synthesizer and an IVL pitch-to-midi converter. Although the composition was designed to use state-of-the-art commercial hardware and software, the equipment required to perform Obsessed Again... is quickly becoming obsolete - the computer files are incompatible with current operating systems and some are stored on older single-sided computer disks, and much of the hardware used is ageing and will soon be inoperable. The work has not been performed for several years, but Dr. Read has expressed a desire to reintroduce it into his repertoire in a form that can be performed easily using current technology (both hardware and software). To meet this requirement, the composition will require recovery and a substantial reworking of both the interactive and electronic elements. In addition, migration strategies will be investigated so that the current scenario does not repeat itself. However, before any such attempts are undertaken, it is necessary to identify and determine the current state of the component elements of Obsessed Again... B. Statement of Methodology The primary information gathering activity for this case study was a series of interviews with the composer, Keith Hamel and performer, Jesse Read. The interviews were designed to obtain enough information from each interview subject to answer the required twenty-three core questions (see Sections D and E for the specific questions and their answers). C. Description of Context The composition Obsessed Again... is represented by a musical score, which notates and provides instructions governing the interaction of all of the elements making up the piece the performer/bassoonist, a Barkus Berry pick-up (microphone), an IVL pitch-to-midi converter, a Macintosh computer with a MIDI interface running the Max software, an external Proteus 1 synthesizer and a sound amplification system (i.e., amplifier, mixer and speakers). By accurately following the score, the sonic entity that is the musical work will be produced. Achieving this sonic event will involve two creative processes: the composition of the musical work (i.e., the preparation of the score) and the performance (i.e., the act of realizing the musical work through an accurate interpretation of the score). InterPARES 2 Project, Focus 1 Page 1 of 41

5 Provenancial The primary individual responsible for the creation of Obsessed Again... is the composer, Keith Hamel. He is the sole creator of the musical work. However, as performer, Jesse Read plays an essential role in contributing to the dissemination of this work and is also responsible for additional entity creation (i.e., recordings). Additionally, Dr. Read collaborated with Dr. Hamel during the compositional process, testing many aspects of the work. Dr. Read considers his role as one of an 'interpreter' of Dr. Hamel's musical work. Also of importance is that by virtue of being the commissioning agent, Dr. Read did provide the initial impetus for the creation of this work and dictated the basic framework within which Dr. Hamel would create Obsessed Again... (i.e., a specification for a musical work for solo bassoon involving the use of interactive electronics). Juridical-administrative There are no specific or extraordinary regulations or laws that affect musical composition. Of interest, though, is the use of Copyright law as the main legal instrument of authenticity and ownership. Procedural No generally accepted or documented procedural rules or schemes exist for entities created through musical composition and performance. Documentary The documentation process is chiefly the responsibility of the composer, in whose fonds the composition still resides, 1 and as with the procedural element above, there are no generally accepted rules or schemes. Technological The original digital environment used for the creation of Obsessed Again... was an Apple Mac II computer (68020), running Mac OS 7. However, this environment has been updated to an Apple PowerBook laptop computer (G4), running Mac OS X As well, the initial Max software (version 2), has been upgraded to Max/MSP (version 4.2). Additionally, a NeXT computer was used for additional file storage and backups. Although initial compositional work for Obsessed Again... occurred away from a digital environment (involving basic sketches of overall form and determination of pitch material and rhythmic aspects for the bassoon part), most of the remaining work occurred at the computer. The Proteus 1 synthesizer was also used as a test platform, simulating the MIDI input provided by the IVL converter. This allowed Dr. Hamel to construct and test many of the interactive elements without requiring a bassoonist to be present. 1 While the composition still resides in the fonds of the composer, technically it should belong to the performer, Jesse Read, who commissioned the work. InterPARES 2 Project, Focus 1 Page 2 of 41

6 D. Narrative Answers to the 23 Core Research Questions 1. What activities of the creator have you investigated? This study examined the compositional process utilized to create Obsessed Again..., and the procedures that Keith Hamel uses to maintain the elements comprising his musical work. As well, an additional party (a performer, in this case Jesse Read) is required to fully realize the sonic event that is the end result of the compositional process. The role of the performer has also been investigated, as it contributes to the creative process. 2. Which of these activities generate the digital entities that are the objects of your case study? The compositional process can be considered an ongoing event, directly involving the act of maintaining and updating the musical work and component elements. This overall process generates the main digital entities being examined. Additionally, Obsessed Again... is disseminated by way of performance, and this act may also generate digital entities. 3. For what purpose(s) are the digital entities you have examined created? There are two purposes for the digital entities comprising Obsessed Again...: (1) to provide the necessary data and instructions with which a performer can (re)produce a performance of the musical work, and (2) to provide a framework allowing the composer to continue the compositional process as deemed necessary (i.e., updates, revisions, etc.). 4. What form do these digital entities take? Dr. Hamel maintains three digital entities: (1) a representation of the musical score, (2) the software patch for Max/MSP, which contains a digital description of the computer 'instrument' and additional MIDI sequencer data, and (3) the Proteus Editor/Librarian file, which describes the sounds to be used by the Proteus 1 synthesizer. 4a. What are the key formal elements, attributes, and behaviour (if any) of the digital entities? For (1), the digital representation of the musical score: NoteWriter music notation software computer files, contained on Dr. Hamel's Apple PowerBook computer. The following four files are stored, located in the file folder Grisey9.2/Documents/NoteWriter Files/OBSESSED AGAIN: 1. Obsessed-Bsn (contains the Bassoon part only) 2. Obsessed-final (contains the Bassoon part along with information about the electronic part) InterPARES 2 Project, Focus 1 Page 3 of 41

7 3. Obsessed-lib1 (graphic images used in the scores) 4. Obsessed-lib2 (more graphic images used in the scores) Additionally, these files have been converted to postscript format for backup storage. For (2), the software patch(es) for Max/MSP: 15 Max/MSP patches (computer files) + 15 MIDI computer files, also stored on Dr. Hamel's Apple PowerBook computer, in the file folder Grisey9.2/Documents/MAXFiles/OBSESSEDNew: 1. BASSOON-MASTER (the master patch file, which will load all other required Max/MSP elements) 2. FX1.midi, FX2.midi, etc. (the MIDI files containing musical data sent to the Proteus synthesizer) For (3), the Editor/Librarian file: A Proteus Editor/Librarian computer files, also stored on Dr. Hamel's Apple PowerBook computer, in the file folder Grisey9.2/Documents/MAXFiles/OBSESSEDNew: 1. Bassoon-Voices (description of voices (sounds) to be assigned to the Proteus 1 synthesizer) 4b. What are the digital components of which they consist and their specifications? The format of each digital entity is dictated by the specifications of the individual software programs with which each file was created. The NoteWriter (.nwr), Max/MSP and Editor/Librarian files are proprietary, binary formats, and as such, their specifications are unreleased. The MIDI files used by the Max/MSP patches are standard text files following the MIDI specification. 2 4c. What is the relationship between the intellectual aspects and the technical components? The main intellectual aspect of Obsessed Again... (the interaction of bassoon and electronics) is completely realized and documented by the technical components. 4d. How are the digital entities identified (e.g., Is there a [persistent] unique identifier? Each of these digital entities is identified through the assignment of a semi-descriptive filename. 2 Available at: InterPARES 2 Project, Focus 1 Page 4 of 41

8 4e. In the organization of the digital entities, what kind of aggregation levels exist, if any? As described above, two aggregation levels exist: (1) the digital score entities, and (2) the digital entities necessary to provide the electronic interaction. 4f. What determines the way in which the digital entities are organized? The organization method is at the sole discretion of Keith Hamel. 5. How are those digital entities created? Each digital entity was created/maintained through the use of a commercial computer software program. The original 1992 version of Obsessed Again... utilized Max version 2.0 (for the Max patches), Performer version 5.5 (for creating the MIDI sequences and saving them as standard MIDI files), NoteWriter (for the score) and version 1.0 of the Galaxy Editor/Librarian (for the Proteus Editor/Librarian file). Recently, Dr. Hamel has updated many of the digital entities in preparation for recreating this piece. Newer software includes Max/MSP version 4.2 and NoteAbility (a replacement for NoteWriter). 5a. What is the nature of the system(s) with which they are created? (e.g., functionality, software, hardware, peripherals, etc.) As it is possible to consider two distinct but related creative processes (creation of the musical work, and creation of the performance), there are also two creative systems. For the creation of the musical work and its digital elements, the original digital system used was an Apple Mac II computer (68020), running Mac OS 7 (as mentioned above, this environment has recently been updated to an Apple PowerBook laptop computer (G4), running Mac OS X ). Additionally, a NeXT computer was used for additional file storage and backups. These computers executed software designed to create each of the necessary digital entities (see above for a list of the software employed). The system required to actually perform the work consists of: (1) a platform running Max/MSP (the generator of the electronic elements) loaded with all of the required patches, (2) the Proteus 1 synthesizer (which converts the digital MIDI data output from Max/MSP to an analogue sound signal) loaded with the necessary Editor/Librarian patches, (3) a microphone (to record the sound of the bassoon as an analogue sound signal), (4) an IVL pitch-to-midi converter (to convert the analogue bassoon signal to digital MIDI data for input into Max/MSP), and (5) a sound amplification system (necessary to output the analogue signal produced by the Proteus synthesizer). 5b. Does the system manage the complete range of digital entities created in the identified activity or activities for the organization (or part of it) in which they operate? Yes, all operations performed on the digital entities occur within the confines of the above two digital systems. InterPARES 2 Project, Focus 1 Page 5 of 41

9 6. From what precise process(es) or procedure(s), or part thereof, do the digital entities result? The digital entities are a direct result of the personal compositional process as employed by Keith Hamel. This process is unique to each composition, but can be generally summarized (in the case of Obsessed Again...) as follows: (1) pre-compositional ideas were sketched, using pencil and paper away from the computer and included items such as the overall form of the work, the working out of basic pitch and harmonic content and determination of the nature of the interaction between the instrument and electronics; (2) working from this initial draft, the interactive elements were created at the computer using the necessary software; (3) these interactive elements were then tested (utilizing the Proteus synthesizer as a virtual performer) and modifications to both the draft score and software files were made as necessary; until, (4) final versions of the digital entities were created and a final score was prepared in digital format. 7. To what other digital or non-digital entities are they connected in either a conceptual or a technical way? Is such connection documented or captured? The three digital entities are connected to each of the remaining non-digital elements of Obsessed Again... summarized at the beginning of this section (i.e., the additional hardware necessary to perform the piece). The connection is documented in a general sense through the musical score, although the composer admits that he has not adequately notated the electronic entities involved, and that the score is more focused on the musical elements (i.e., traditional pitches and rhythms) that the bassoonist is required to produce. This was a result of a performerfocused attitude, and the fact that the performer did not need to know the details of these entities to satisfactorily perform the piece. Dr. Read echoes this last sentiment; however, as a performer, he does not feel that a more accurate notation for the electroacoustic entities is necessary. 8. What are the documentary and technological processes or procedures that the creator follows to identify, retrieve, and access the digital entities? The digital entities are accessed through generally employed computer usage (i.e., files are stored on disk and accessed from within the associated software program), and are identified through the use of semi-descriptive file names. 9. Are those processes and procedures documented? How? In what form? Although not specifically focused on accessing the digital entities of Obsessed Again..., instruction manuals exist for each of the software programs utilized that describe the general procedures necessary to interact with their digitally stored materials. However, specific information concerning filenames and versions directly employed by Obsessed Again... are available only through communication with Dr. Hamel. InterPARES 2 Project, Focus 1 Page 6 of 41

10 10. What measures does the creator take to ensure the quality, reliability and authenticity of the digital entities and their documentation? Specific procedures are not in place to ensure these qualities; however, by being the sole possessor of all the digital entities in question, Dr. Hamel is able to maintain what he views as an adequate level of control over the distribution of authentic digital elements to performers or other agencies. No specific procedures would prevent a second-hand distribution (i.e., by the performer or agency to another performer), but a general sense of respect for the composer is usually found in these instances. Dr. Read states that as a performer, he feels a responsibility to the composer to be certain that any further dissemination of the piece occur only as prescribed by Dr. Hamel. 11. Does the creator think that the authenticity of his digital entities is assured, and if so, why? Dr. Hamel is the sole arbiter of authenticity and the only preserver/distributer of these digital entities, and as such, is confident that they are authentic. However, no specific procedures are in place that would allow a third party to independently confirm this authenticity. Additionally, no technological method (i.e., encryption technique, digital signature, etc.) is employed to prevent a third party from redistributing these digital entities and/or compromising their authenticity. However, the creative work as a whole is copyrighted, and Dr. Hamel feels this is a reasonable deterrent against unauthorized alteration and reproduction. 12. How does the creator use the digital entities under examination? The digital entities are stored for future dissemination to performers and/or for alteration as judged necessary by Dr. Hamel. 13. How are changes to the digital entities made and recorded? All alterations are made by the composer himself, and he does not record these changes in any formal manner. 14. Do external users have access to the digital entities in question? If so, how, and what kind of uses do they make of the entities? External users do not have access to the master copies of the digital entities, as maintained by Dr. Hamel. However, duplicates are made and distributed to potential performers and/or other interested parties (e.g., students, arts organizations, etc.). These distributions may result in a fragmentary dissemination of the work, as certain individual elements (most notably the score) are often the only object duplicated. Of course, the most likely scenario for a distribution would be to allow for a performance of the work. InterPARES 2 Project, Focus 1 Page 7 of 41

11 15. Are there specific job competencies (or responsibilities) with respect to the creation, maintenance, and/or use of the digital entities? If yes, what are they? Basic technical knowledge of computer hardware, as well as specific proficiency in the software applications involved, is necessary for maintenance and use of the digital entities. Additionally, an adequate musical training and an ethical responsibility and respect for the composer's work are both necessary for any performance-related interaction and revision. 16. Are the access rights (to objects and/or systems) connected to the job competence of the responsible person? If yes, what are they? This question is somewhat inapplicable to the current study; however, as stated in the answer to the previous question, a certain level of competence with computer hardware and software, as well as an adequate level of musical training, is required to intelligently access/modify the digital entities. As a result, access is in a sense restricted to persons in possession of these abilities. 17. Among its digital entities, which ones does the creator consider to be records and why? Dr. Hamel does not consider any of these entities to be records. As a composer, he is focused more on the present use of a work, not its past or future states. Many works have only a shortterm existence, and this is most evident with those involving technology. Limitations of current software and hardware, and the speed of advances in capabilities are the most limiting factors. All of the digital entities for Obsessed Again... are treated in a utilitarian, not archival, sense. 18. Does the creator keep the digital entities that are currently being examined? That is, are these digital entities part of a recordkeeping system? If so, what are its features? Although the creator does keep the digital entities in question, there is no formal recordkeeping system employed by Dr. Hamel. The digital entities are stored on computer disks, which remain in the possession of the composer. 18a. Do the recordkeeping system(s) (or processes) routinely capture all digital entities within the scope of the activity it covers? As answered above, no such system exists, but Dr. Hamel does capture and store all the digital entities he feels are required by the work. 18b. From what applications do the recordkeeping system(s) inherit or capture the digital entities and the related metadata (e.g., , tracking systems, workflow systems, office systems, databases, etc.)? Not applicable. InterPARES 2 Project, Focus 1 Page 8 of 41

12 18c. Are the digital entities organized in a way that reflects the creation processes? What is the schema, if any, for organizing the digital entities? The digital entities reflect the creation process in so much as they are organized by file type (i.e., the individual files are dictated by the software program used to create them). 18d.Does the recordkeeping system provide ready access to all relevant digital entities and related metadata? Again, no system exists, but Dr. Hamel currently has ready access to all relevant digital entities. 18e. Does the recordkeeping system document all actions/transactions that take place in the system re: the digital entities? If so, what are the metadata captured? No such documentation exists. 19. How does the creator maintain its digital entities through technological change? Initially, no active actions were taken to protect against technological advance. However, as described in the overview to this report, a recent attempt to reintroduce this work into the active repertoire has forced a re-examination of this decision. As of the writing of this report, Dr. Hamel has translated many of the original entities into forms accessible by current technology. Unfortunately, it does appear as though particular elements the editor/librarian patch for the Proteus 1, specifically will be impossible to update due to obsolete software, and as a result will need to be recreated. Additional concerns have been raised with regards to the age of some of the non-digital entities (the aforementioned Proteus 1 and the original Macintosh computer). While these entities can be updated to current hardware versions (or possibly of more benefit to future storage, be converted to a software representation), these changes will alter the nature of the composition (i.e., sound production will change, overall sound quality will differ, etc.), and may also require alteration to connected elements. As a result, the sonic event that is Obsessed Again... will be fundamentally different. It is interesting to note, however, that Dr. Hamel does not view this outcome in a negative manner, and in fact, he is quite pleased to rework elements of his piece. Dr. Hamel sees the process of archiving not as an act of historical preservation, but instead, as a means of ensuring his composition's future existence. This focus will require a more complete musical score with much more detailed indications of the interaction between the acoustic and electroacoustic elements, and the inclusion of a digital recording of an authentic version of the work by which future performances can be judged. 19a. What preservation strategies and/or methods are implemented and how? The main preservation strategy implemented by Dr. Hamel has been to reduce the hardware dependence of Obsessed Again... and re-implement as many of the interactive elements as possible in software. Currently, the Proteus 1 synthesizer is no longer required, and its InterPARES 2 Project, Focus 1 Page 9 of 41

13 sound production procedure has been implemented as a software synthesizer patch in Max/MSP. Dr. Hamel has identified Max/MSP as the current best option for software/hardware amalgamation. Although not currently employed, Max/MSP pitch-to- MIDI converters do exist, which would allow for the additional replacement of the IVL converter. 19b. Are these strategies or methods determined by the type of digital entities (in a technical sense) or by other criteria? If the latter, what criteria? Yes. Dr. Hamel's ultimate goal is to remove external hardware dependencies (with the exception of the system necessary to run Max/MSP) and re-implement them as a Max/MSP patch. 20. To what extent do policies, procedures, and standards currently control records creation, maintenance, preservation and use in the context of the creator s activity? Do these policies, procedures, and standards need to be modified or augmented? There is currently very little in the way of formalized policies, procedures or standards involved with Obsessed Again... The creation of such elements is seen as a priority for the composer, with respect to both this specific work and as a means to introduce standardized procedures and policies for archiving electroacoustic music as a whole. 21. What legal, moral (e.g., control over artistic expression) or ethical obligations, concerns or issues exist regarding the creation, maintenance, preservation and use of the records in the context of the creator s activity? As composer, there is no external moral or legal responsibility concerning the creation, maintenance, preservation and use of the digital entities that comprise Obsessed Again... 3 There is, however, a more internal moral dedication to ensuring the future life of this work. 22. What descriptive or other metadata schema or standards are currently being used in the creation, maintenance, use and preservation of the recordkeeping system or environment being studied? No such schema or standards are used. 23. What is the source of these descriptive or other metadata schema or standards (institutional convention, professional body, international standard, individual practice, etc.)? Not applicable. 3 It appears that Obsessed Again constituted an informal, verbal commission with no legal obligations. Moreover, as noted in question 17, Dr. Hamel does not consider any of the digital entities comprising Obsessed Again to be records. InterPARES 2 Project, Focus 1 Page 10 of 41

14 E. Narrative Answers to Applicable Domain and Cross-domain Research Questions Policy Cross-domain 4.4 What legal or moral obligations exist regarding the creation, maintenance, preservation, and use of the records of artistic and scientific activities? As discussed above, the composer feels a moral obligation to ensure the future existence of his work, but no real compulsion towards preservation for archival purposes. Legal obligations do exist, focused mainly on copyright and authorship issues (for authenticity verification, performing rights, etc.); however, these do not constitute a pressing concern for Dr. Hamel. 4.5 (a) What principles should guide the formulation of policies, strategies and standards related to the creation of reliable, accurate and authentic records in the digital environments under investigation? The main concern for Dr. Hamel is that the future existence of his work be ensured. This principle should guide all policy formulations. Specifically, Dr. Hamel feels that priority should be given to the development of descriptive procedures that can ensure that the creation of the electroacoustic elements of Obsessed Again, as well as the descriptive documentation of the interaction between performer and computer, results in digital entities that are reliable, accurate and authentic. Combined with existing music notation procedures (which can be described as adequately accurate and authentic), these descriptive procedures would allow for a complete account of the actions necessary to (re)create Obsessed Again 4.5 (b) What principles should guide the formulation of policies, strategies and standards related to the appraisal of those records? As explicitly stated above, the accuracy and authenticity of all digital entities must be assured. Description Cross-domain 6.8 (a) What is the relationship between the role of descriptive schemas and instruments needed by the creator and those required by the preserver to support the archival processes of appraisal, preservation and dissemination? It would seem likely that a means to ensure accuracy and authenticity could be integrated into the descriptive schemas developed as described above in question 4.5a. Separate schemas for the creator and preserver would not be necessary. InterPARES 2 Project, Focus 1 Page 11 of 41

15 6.9 What is the role of descriptive schemas and instruments in rights management and in identifying and tracking records components, versions, expressions, performances, and other manifestations, and derivative works? This would be a vital role, as it is an examination of these attributes that will allow for others to ensure the accuracy and authenticity of the work (and its digital components) (a) Is it important to be able to relate the record of artistic and scientific activity to the associated expression, performance, product, work, or other manifestation of it? Yes it is important, however, not necessarily for the creator. Documentation of the processes involved in creating Obsessed Again may have a historical value to musicologists or others, but for the composer, it is the musical work that must be preserved. For his purposes, all digital entities must ultimately relate to the future (re)creation of this work (b) and, if so, in what ways can descriptive activities facilitate it? Descriptive facilities are the core means of ensuring the accuracy and authenticity of Obsessed Again during its (re)creation, and the preservation of its accuracy and authenticity over the long-term. Current efforts at creating a text-based meta-language for digital storage of musical scores can already be seen to facilitate a complete digital description of the musical work. Examples such as GUIDO and MusicXML (see bibliography) are also extensible, allowing for the addition of means to help ensure the accuracy and authenticity of electroacoustic musical works. InterPARES 2 Project, Focus 1 Page 12 of 41

16 F. Selected Bibliography Anthony, D., Charles Cronin and Eleanor Selfridge-Field (2001). The Electronic Dissemination of Notated Music: An Overview. In The Virtual Score: Representation, Retrieval, Restoration, W. B. Hewlett and E. Selfridge-Field, eds. (Cambridge, MA: MIT Press, 2001), Bari, Andrea, Sergio Canazza, Giovanni De Poli and Gian Antonio Mian (2001). Toward a Methodology for the Restoration of Electroacoustic Music Journal of New Music Research 30(4): Canazza, S. and A. Vidolin (2001). Introduction: Preserving Electroacoustic Music, Journal of New Music Research 30(4): Castan, G., M. Good, and P. Roland (2001). Extensible markup language (XML) for music applications: An introduction. In The Virtual Score: Representation, Retrieval, Restoration, W. B. Hewlett and E. Selfridge-Field, eds. (Cambridge, MA: MIT Press, 2001), Chadabe, Joel (2001). Preserving Performances of Electronic Music, Journal of New Music Research 30(4): Davies, Hugh (2001). The Preservation of Electronic Musical Instruments, Journal of New Music Research 30(4): Hamel, Keith A Obsessed Again for Bassoon and Interactive Electronics. Hoos, Holger, Keith Hamel, Kai Renz and Jürgen Kilian (2001). Represented Score-Level Music Using the GUIDO Music-Notation Format. In The Virtual Score: Representation, Retrieval, Restoration, W. B. Hewlett and E. Selfridge-Field, eds. (Cambridge, MA: MIT Press, 2001), Max/MSP Software, (accessed 16 February 2004). MIDI Specification, (accessed 16 February 2004). InterPARES 2 Project, Focus 1 Page 13 of 41

17 G. Glossary of Terms Term commission composer electroacoustic instrument library interactive electronics interpreter Max/MSP microphone MIDI music music notation music notation software musical score musical work patch performance performer Definition (in context of this report) A contract directing a composer to create a musical work. The creator of the musical work. Aural events generated by an electronic device. A series of specifications for use with a synthesizer, dictating the specific sound output (timbre) to be produced. Electroacoustics generated by an interaction between a performer and an electronic device. The creator of the musical performance. A digital sound processing (DSP) software application, designed to provide a platform to produce interactive electronics. An electronic device designed to translate aural events into an electronic signal Musical Instrument Digital Interface. A standardized means of representing acoustic information (i.e., pitch, dynamics, etc.) in digital format. A temporal experience of specific aural events. Text or graphical symbols designed to convey musical meaning. Computer software designed to aid in the production of a musical score. A means of providing instructions in the form of musical notation to the performer/interpreter, resulting in the musical performance. The composed music itself, as well as the musical score and any other descriptive documentation required to interpret this score. In the case of electroacoustic music, or mixed acoustic/ electrocacoustic music, it also includes the technology required to reproduce any digital components (i.e., interactive electronics). Computer code designed to produce an expected output given a specified input. Used with Max/MSP to design specific interactions between the performer and the Proteus synthesizer. To translate the musical score into an acoustic reality. The interpreter of the musical work. InterPARES 2 Project, Focus 1 Page 14 of 41

18 pitch-to-midi converter synthesizer An electronic device designed to translate analogue electronic sound signals (provided by a microphone) into a digital format (MIDI). An electronic device designed to produce electroacoustics. Utilizes an instrument library to create a variety of unique sound outputs. May be coupled with a standard piano-like keyboard to control specific pitch output, or may rely on MIDI communication for musical parameters (i.e., pitch, dynamics, length, etc.) InterPARES 2 Project, Focus 1 Page 15 of 41

19 H. Preliminary Models IDEF0 Activity and Entity Relationship models follow, with definitions. InterPARES 2 Project, Focus 1 Page 16 of 41

20 IDEF0 Activity Model: Diagrams InterPARES 2 Project, Focus 1 Page 17 of 41

21 InterPARES 2 Project, Focus 1 Page 18 of 41

22 InterPARES 2 Project, Focus 1 Page 19 of 41

23 InterPARES 2 Project, Focus 1 Page 20 of 41

24 InterPARES 2 Project, Focus 1 Page 21 of 41

25 IDEF0 Activity Model: Definitions Case Study 13: Obsessed Again... IDEF0 Model: Activity Definitions Activity Name Activity No. Activity Definition Activity Note Compose Obsessed A0 To fulfil the Commission. Involves conceiving, programming, notating, producing other representations and evaluating. Again Conceive A1 To produce Musical Ideas. May involve activities such as sketching, brainstorming, doodling, etc. Program A2 To represent applicable Musical Ideas as Involves developing code, testing code and revising code. Functional Computer Code. Develop Code A2.1 To produce Computer Code. Involves writing Computer Code to provide an expected output given a specified input. Computer Code developed here is untested, and may not be Test Code A2.2 To determine whether Computer Code is functional. functional. Involves evaluating Computer Code (by the composer and/or performer) for functionality. If the Computer Code produces an expected output given a specified input, it is functional, otherwise it is faulty. Revise Code A2.3 To repair Faulty Computer Code. Involves revising Computer Code that has been evaluated as faulty (nonfunctional). Defects in the Computer Code must be identified and corrected. Notate A3 To represent applicable Musical Ideas as Involves developing notation, testing notation and revising notation. Functional Score Elements. Develop Notation A3.1 To produce Score Elements. Involves writing Score Elements to provide instructions to the performer on how to produce specific element(s) of the musical work. Test Notation A3.2 To determine whether the Score Elements are functional. Involves ensuring that the Score Elements accurately represent the musical idea, and that it is practical for the performer to realize the Score Elements in Revise Notation Represent Alternatively Evaluate Aesthetically terms of playability. A3.3 To repair Faulty Score Elements. Involves revising Score Elements that have been evaluated as faulty (nonfunctional). Defects in the Score Elements must be identified and corrected. A4 A5 To represent applicable Musical Ideas as Other Representations. To determine whether an element is aesthetically acceptable. Involves creating any representation that is not Computer Code or Score Elements, possibly including verbal instructions, and graphic doodles. Involves aesthetically judging functional musical ideas (represented by computer code, score elements or other representations) for inclusion in the final musical work. InterPARES 2 Project, Focus 1 Page 22 of 41

26 Case Study 13: Obsessed Again... IDEF0 Model: Arrow Definitions Arrow Name Arrow Definition Arrow Note Code A set of computer readable instructions May consist of Max/MSP patches, MIDI data or other helper utility code. designed to produce an expected result from a specified input. Commission Contract between the commissioner and the The commission may be the generative impulse for creating a composition. composer for production of a musical composition. Commission Specifications The specific attributes that the final composition must posses. The commission specifications may include elements such as a requirement of originality, instrumentation (musical instruments and associated musical technology available), length of the piece, completion date and fee. Composer The creator of the musical work. Keith Hamel. Faulty Computer Code Computer code that does not produce the expected output given a specified input. Faulty Score Elements Final Computer Code Final Other Representations Final Score Elements Financial & Time Resources Functional Computer Code Functional Score Elements Score elements that do not properly convey a specific musical meaning, or require a musical action that is impossible to perform. Computer code that will be used in the final musical work. Other representations that will be used in the final musical work. Score elements that will be used in the final musical work. Time and financial constraints upon the composer. Computer code that has passed the testing phase. Score elements that have passed the testing phase. Computer code will be judged faulty by the composer or performer when it fails during the testing phase (i.e., does not function as expected). This code cannot be used in a faulty state, and therefore must be revised to function correctly. A score element will be judged faulty by the composer or performer when it fails during the testing phase (i.e., does not convey a musical meaning as expected, or produces results that are unperformable). This score element cannot be used in a faulty state, and therefore must be revised to function correctly. Certain musical ideas represented by computer code will be judged as aesthetically acceptable by the composer, and will be included in the final musical work. Certain musical ideas represented by other representations will be judged as aesthetically acceptable by the composer, and will be included in the final musical work. Certain musical ideas represented by a score element will be judged as aesthetically acceptable by the composer, and will be included in the final musical work. May limit any/all steps of the composition process. Computer code will be judged functional by the composer or performer when it passes the testing phase (i.e., functions as expected). A score element will be judged functional by the composer or performer when it passes the testing phase (i.e., conveys a performable musical meaning). InterPARES 2 Project, Focus 1 Page 23 of 41

27 Case Study 13: Obsessed Again... IDEF0 Model: Arrow Definitions (cont.) Arrow Name Arrow Definition Arrow Note Legal System Relevant rules and laws affecting the composer's work. May include concepts such as author copyright, performance rights for both composer and performer, software licensing agreements, etc. Musical Ideas The basic creative elements of the musical work. Abstract creative elements that will be transformed into more concrete components of the musical work (i.e., score element, computer code, other representation) Other Representations Any representation of a musical idea that is May include musical ideas or instructions described either graphically or Other Representations to be Discarded Performer Recordkeeping Needs Revised code Revised Score Elements Score Elements Score Elements to be Discarded Social and Professional Environment State of Technology not computer code or a score element. Other representations that will not be used in the final musical work. The individual responsible for the sonic production of specific element(s) of the musical work. The needs of the composer for storing and making accessible the work and entities generated in the course of its creation. Faulty computer code that has been altered and is in need of (re)testing. Faulty score elements that have been altered and are in need of (re)testing. A text or graphical symbol designed to convey a specific musical meaning. Score elements that will not be used in the final musical work. The social and professional environment in which the composer is active. Technology currently available to the composer. verbally. Certain musical ideas represented by alternative representations may be judged as aesthetically unacceptable by the composer. These will be discarded, and will not be included in the final musical work. The bassoonist (Jesse Read). May involve practical constraints in size and format for maintaining the material and distributing it to interested parties, as well as reduce Financial and Time Resources. Computer code that has been deemed faulty will be revised to correct any functional defects. A score element that has been deemed faulty will be revised to correct any functional defects. Instructions to the performer on how to produce specific element(s) of the musical work. May consist of traditional music notation, but may also be extended to provide more specialized instructions. Certain musical ideas represented by score elements may be judged as aesthetically unacceptable by the composer. These will be discarded, and will not be included in the final musical work. Constraints on aesthetics choices such as form, materials, etc., will be dictated by the specific time and place in which the composer is active. Constraints on technological functions of the work due to speed, storage capacity, and general functionality of current technology. InterPARES 2 Project, Focus 1 Page 24 of 41

28 Entity Relationship Model: Diagram OBSESSED_AGAIN( Display 1 / <Main Subject Area> 1, 1 / 1, 1 13:34:41, 02/17/2004 InterPARES 2 Project, Focus 1 Page 25 of 41

29 Entity Relationship Model: Definitions Case Study 13: Obsessed Again... Entity Relationship Model: Definitions Entity Name Attribute Names Entity Definition Entity Note Alternative Representation ar_id (PK) performer_id (PK) (FK) composer_name (PK) (FK) The composer's name. composer_affiliation (PK) (FK) Any professional affiliations the composer may have. composition_id (PK) (FK) composition_date (PK) (FK) The date of composition. composition_copyright_notice A notice of copyright for the (PK) (FK) composition. composition_title (PK) (FK) The title of the composition. ar_hardware_specification Hardware required to perform the composition. ar_software_specification Software required to perform the composition. ar_hardware_setup Instructions on how to set up the hardware components. ar_software_setup Instructions on how to set up the software components. Code code_id (PK) code_filename (PK) A unique, semi-descriptive filename identifier. performer_id (PK) (FK) composer_name (PK) (FK) The composer's name. composer_affiliation (PK) (FK) Any professional affiliations the composer may have. composition_id (PK) (FK) composition_date (PK) (FK) The date of composition. composition_copyright_notice A notice of copyright for the (PK) (FK) composition. ar_id (PK) (FK) composition_title (PK) (FK) The title of the composition. May include professional organizations such as the Canadian League of Composers or SOCAN. Notated in text on the title page or first page of the score. In the usual format of Copyright (c) Year by Composer Name. Dictates the necessary hardware: computer, pitch rider, synthesizer, etc. Dictates the necessary software: Max/MSP, etc. Specifications for how the hardware must be connected. Specifications for how the software must be set up (i.e., which patches should be loaded, etc.) A means of identifying specific code for use with ar_software_specification, ar_software_setup, etc. May include professional organizations such as the Canadian League of Composers or SOCAN. Notated in text on the title page or first page of the score. In the usual format of Copyright (c) Year by Composer Name. InterPARES 2 Project, Focus 1 Page 26 of 41

30 code_type The type of code used. The specific computer language or program used. May include Max/MSP patches, MIDI, etc. Composer composer_name (PK) The composer's name. composer_affiliation (PK) Any professional affiliations the composer may have. May include professional organizations such as the Canadian League of Composers or SOCAN. Notation notation_id (PK) notation_medium (PK) The notation medium used. May include digital formats such as postscript or applicationspecific file types, as well as standard printed notation. performer_id (PK) (FK) composer_name (PK) (FK) The composer's name. composer_affiliation (PK) (FK) Any professional affiliations the composer may have. May include professional organizations such as the Canadian League of Composers or SOCAN. composition_id (PK) (FK) composition_date (PK) (FK) The date of composition. composition_copyright_notice (PK) (FK) A notice of copyright for the composition. Notated in text on the title page or first page of the score. In the usual format of Copyright (c) Year by Composer Name. composition_title (PK) (FK) notation_type The type of notation employed. May include possibilities such as common Western music notation, abstract graphical notation or even text instructions. Obsessed Again composition_id (PK) composition_date (PK) The date of composition. composition_copyright_notice (PK) A notice of copyright for the composition. composition_title (PK) The title of the composition. composer_name (PK) (FK) The composer's name. composer_affiliation (PK) (FK) Any professional affiliations the composer may have. composition_duration The length of the composition. Performer performer_id (PK) Notated in text on the title page or first page of the score. In the usual format of Copyright (c) Year by Composer Name. May include professional organizations such as the Canadian League of Composers or SOCAN. InterPARES 2 Project, Focus 1 Page 27 of 41

31 Appendix 1: Towards a Strategy for the Preservation of Electroacoustic Music Introduction Electroacoustic music, that is, music written strictly for performance through electronic means, presents a variety of challenges for the archivist. Unlike traditional acoustic music where various physical records are created by the composer during the composition process such as sketches and the musical score, for example electroacoustic composition often only leaves digital entities behind for the archivist. Aside from a recording, possibly itself in digital format (e.g., wave, mp3, etc.), these digital entities are left in a proprietary software format that is generally usable only by a specific software program. Although an instrument such as the violin will most likely be available for future musicians (in more or less the same state available to musicians today), the digital and electronic components that are utilized for a particular electro acoustic composition are almost guaranteed to be obsolete within a very short time period after the work s creation. The technology employed by composers over the last half-a-century has progressed dramatically, and both hardware and software components are routinely discarded for newer, faster solutions. Towards a Strategy Obsessed Again, a musical composition for bassoon and interactive, live electroacoustic music, has provided an excellent case study from which to develop strategies for digital music preservation. The electronic components for this work include a variety of software components, plus two major hardware requirements. It is the latter that demonstrates the most obvious preservation problem. A hardware sound synthesizer (the Proteus) and a hardware pitch-to-midi converter are essential to the original conception of the piece. However, they are now technologically obsolete, and the units in the possession of Dr. Keith Hamel (the composer) are very much in danger of ceasing to function. Currently, the clearest course for the future recreation and study of this work is to model the hardware requirements in the software realm. The specific sounds made by the Proteus synthesizer can relatively easily be copied and stored as a digital object. The most obvious form for this digital entity is currently a Max/MSP (Max) patch. Max is the software used to govern the InterPARES 2 Project, Focus 1 Page 28 of 41