The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.09 - September (1999 vol.32)
pp: 26-34
ABSTRACT
<p>The typical orchestra manages a huge amount of information. A symphonic work's main score often runs to more than 100 pages, while an operatic score can run 600 or more. From the main score, the conductor draws some 15 to 30 different instrumental parts and distributes them to 40 or more lecterns so that 70 musicians can play from them during rehearsals and performances. This overhead increases significantly if the piece requires a chorus as well. A typical performance ranges from a few minutes to more than two hours. Individual musicians often make simple changes to the score, writing them manually on their parts during rehearsals, most often by adding interpretation symbols such as dynamics, expression marks, and string bowings. More complex changes-such as arrangements for different instruments, transpositions, and the deletion or addition of music sections-must be decided by the conductor. Operas, ballets, and new symphonic works frequently require such time-consuming modifications. Many performing organizations and publishers could benefit from a computerized option that allows storage of multiple versions and reduces the amount of repetitive work involved. The authors discuss their approach: the Music Object-Oriented Distributed System.</p>
CITATION
Pierfrancesco Bellini, Fabrizio Fioravanti, Paolo Nesi, "Managing Music in Orchestras", Computer, vol.32, no. 9, pp. 26-34, September 1999, doi:10.1109/2.789748
15 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool