How can we establish the original score?

Historical musical pieces make their way to us through multiple documents and it often happens that multiple sources introduce differences and variants in the music.” In the 15th and 16th centuries music was not published, as patrons required composers to produce music for their sole use, not allowing public access to the scores. These restraints led to many audience members notating the music during or after performances, generating scores for the general public for playing and scholarly research. This has left us with multiple scores of music from these periods, which have differences and variations clearly shown in the notation.

MeiView is a sample web application that displays the variants found in 15th and 16th century music scores. The application works by the user hovering over green dots on a score (in common western music notation). These dots allow the user to view the variations in notation for  a particular bar. If there is no variation, then there will be no green dot above the bar. MeiView is an open source development, using MEI-to-VexFlow and VexFlow (explained later in the post).

1a

1b

With great success, meiView begins to answer traditional research questions, such as “Which is the original notation of 15th century music?”. Within music, scholars and individuals have been interested in finding the original copies of the music discovered during the 15th and 16th centuries. This application allows an academic, student or researcher to analyse the displayed data. They can see the variations and make a detailed conclusion on what the original piece would have sounded like. This is the first application of its sort that I have come across. There are many music applications which display musical notation, written documents or allow the user to notate music. However, this is the first application that I have discovered that begins to answer research questions, and actually starts to compare music for you. Therefore this application begins the process of fully embodying the concept of digital humanities research.

MEI- the Music Encoding Initiative was developed by the scholarly community to display western music notation, relevant to historical study of music. It is an independent platform, based on XML standards, allowing for scholarly analysis and a variety of both digital and print rendering possibilities. Using XML standards like MEI provide a standardized way to transfer information understood at both ends. Aware of other XML based music standardization systems, such as MusicXML, “MEI was conceived through a need for storage and exchange of scholarly manuscripts”. Though both MusicXML and MEI both encode music notation (notes, staves, key signatures etc.) expressed in XML, MusicXML was devised to allow the representation of music notation, used by sheet music companies to display music to be printed, or played from online scores. MEI allows for the digitization of sheet music, like MusicXML, but goes further than MusicXML to allow for the encoding of information about the notation in a controlled structure. These two pieces of software were conceived by different groups of people, for the use of different groups of people. MusicXML was made for publishers, and those who want to view sheet music online, whereas MEI was conceived by music scholars for scholarly use. Therefore MEI is not just purely compatible with Common Western Notation, but supports historical western music notation systems such as mensural notation and neume notation.

Whilst looking into MEI, I discovered a list of their current and previous projects, allowing me to establish that no other MEI projects had begun to use music notation software the way meiView has. MeiView allows not only the displaying of data, but also the display of analysis of scores. Past MEI projects include projects which display pages from books, written accounts, scores and notation software. MeiView shows the ability of software instigating research in musicology, which could allow for a more concise set of data.

MeiView, along with being a part of the Music Encoding Initiative, also uses VexFlow. VexFlow allows ways to create, share and publish music online. This includes its sub-programs such as My VexFlow, which allows the embedding of playable music notation within blog-posts. This application uses the generic code for The Vex Flow, which allows you to render music notation within applications. On both the MEI and MusicXML webpages, neither discusses nor suggests any alternatives to VexFlow is frequently suggested as the best engraving engine for music notation.

With meiView’s ability to display variants in scores and its developments in analysis, I feel there is so much more we can hope for in the future of music digital technologies. If we could gain concrete statistics about the similarity between varying scores, the findings of musicologists could be seen as more ‘reliable’ and consistent. This could be done by creating a likelihood that certain bars are accurate, not requiring just the findings of what we believe is the correct piece of music, but the percentage chance each variant is correct. The use of percentages creates a useable formula; consistent with all musical analysis to be developed; reducing individual bias and variants in the consistency of language analysis. This application opens up the opportunity to analyse music in different ways; an example of using a structural analysis for music, is the project SALAMI. Could it take a more mathematical approach, comparing statistics, and relationships through figures? This could be approached through creating a deviation coefficient. It could be worked out how similar notes are from one another. For example, if one note given for a specific bar was an F and the other F#, the difference could easily be put down to faults in aural skills of the transcriber, as the notes are very close together. However, if the notes were a considerable distance apart, for example at a 5th, then it will be harder to determine the correct music for that bar. Using a mathematical approach to music analysis could allow for a greater level of consistency between academics research, rather than the variants imposed by individuals’ use of language. This coefficient analysis would not be successful in performances either played wrong or purposefully varied. However, this in itself could generate an interesting analysis of the variations in performances of certain genres or composers. The use of a more quantitative research approach would also allow for more inter-disciplinary music research.

MeiView is a timely and useful application; however its usability lets the application down. It is an innovative idea, showing the similarities and differences between scores. However, the source of the music transcripts used as comparisons are not clearly stated. The list is unclear, and not in a generic catalogue system, which you would expect from a program such as meiView. The application suffers from a lack of a simple database, showing clearly the information known about these sources; such as, the date it was notated, who notated it and information about where the user could locate its original copy. The creation of a simple database in the already open source code would allow for easy additions to be made to the information about each score. This allows for the program to develop at the rate our knowledge about the music displayed does. A database which clearly lays out the data would also allow for a simple way to find trends and patterns within the data. This currently limits the suitability of the program for multiple audiences. Clear titles of music, and the ability to play the music aloud, would give access to children and the general public. The addition of named sources, and additional information on why certain sources have been chosen as a ‘main source’, would allow for humanities academics to understand the programs use and how it was collated.

Overall, this software marks a trend towards academic music software that answers current and traditional research questions. This program has a long way to go, with potential features such as a database and mathematical analysis making it much more powerful. MeiView at current purely displays information, and does not take it upon itself to actually become an interactive tool, to being to generate answers to questions independently. Programs such as Mendeley; a reference manager, has its own database of papers. The software allows you to search referencing details of papers you have downloaded, identifying the paper in an individual library. The brilliant thing about software like Mendeley is it allows academics to share annotations with other academics, allowing for the building of ideas and collaboration inter-disciplinary. If MeiView were developed to allow these collaborations and sharing of academic information; by allowing individuals to add sources, edit details and write their findings and opinions on which is the original music. There may come a time when the question of which was the original piece of 15th or 16th century music can be correctly answered based one true facts.

Advertisements

Can our brain directly generate music?

L. J. Rich’s recent article on the BBC discusses a project led by Professor Eduardo Miranda, who has made a living out of “music neurotechnology“. The ‘composer’ (the person whose brain is going to ‘create’ the music) puts on a brain cap which has electrodes on the back. These electrodes pick up brainwaves from the visual cortex.The brain waves are input into a computer, which generates music influenced by the brain waves received. The composer is required to choose a visual prompt to concentrate on, one of four moving checkered patterns. These patterns flicker at different rates, stimulating the brain to create a sympathetic electrical signal. The program then uses the brain’s sympathetic electrical signal, to select from pre-composed musical phrases to complete the composition.  Read more