Reading and writing over the centuries has mostly relied on a person's ability to see. It was not until the 1800s that Louis Braille invented a system of raised dots that allowed the visually-impaired to read by substituting the sense of touch. In similar fashion, the blind have been deprived of playing and singing from musical scores for most of history, since reading and writing music on a staff also relies on the ability of sight. Fortunately, Braille also developed a system to represent written music as raised dots.
Braille music notation is noticeably different from the standard musical notation of representing notes on a staff, as shown below.
Happy Birthday" in Braille Music
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠩⠼⠉⠲⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠼⠁⠀⠐⠑⠄⠵⠫⠱⠀⠳⠟⠀⠑⠄⠵⠫⠱⠀⠪⠗⠀⠑⠄⠵⠨⠱⠺⠀⠓⠄⠷⠻⠫
⠨⠙⠄⠽⠺⠳⠀⠪⠗⠣⠅
Braille music notation is not only different from standard musical notation, but also just as complex and difficult to master. Not only do blind persons need special training in reading Braille music notation, but those sighted persons seeking to transcribe music into Braille need extensive training in how the two notations correspond and where they differ.
This raises the question: what happens the day when a visually-impaired yet excellent singer wants to sing in the MIT Concert Choir? Assuming he or she is able to read Braille music notation, there needs to be a way of providing him or her with the translated repertoire.
One way of doing so is to invoke the services of a transcriber. However, because of the complexities explained beforehand, there are very few transcribers available to do this. Another solution is to use transcription software available on the open market. The problem is that said software tends to be very expensive. But what if there existed free software that could do the same? And that is exactly what the Braille music transcriber, BMT, I have been developing is.
I started developing BMT in July 2011 under a direct funding UROP as part of the music21 project, a project in MIT Music and Theater Arts which aims to develop software useful for musical analysis. Using knowledge borrowed from my years of training in both music and computer science, borrowing from code already written for music21, and consulting very closely with a certified Braille transcription manual[1], I have come up with a rudimentary transcriber.
Right now, BMT is capable of translating melodies such as the example presented beforehand––melodies containing musical elements including, but not limited to, notes, rests, bar lines, key signatures, and time signatures. Each of the musical elements corresponds to a Braille character or series of characters. Some more complex elements supported include fingering, slurs, changes of key or time signatures, and beaming. In short, most of the concepts in twelve of the first sixteen chapters of the transcription manual have been implemented, with more than 100 examples found within those chapters being transcribed correctly.
However, there is functionality that I aim to add during this UROP. The most notable of these is support for chords, or set of notes played or sung at once. Not only are chords omnipresent in keyboard music, but also harmonies of instruments in pieces with multiple parts played or sung in unison can always be boiled down to chords. Hence, chords are used as a method of instruction in musical composition classes not only at MIT but also at universities across the world. Implementing chords would be a big step towards being able to translate an introductory composition text such as Marjorie Merryman's The Music Theory Handbook[2] which is used at MIT. Chords and related concepts are covered over five chapters, approximately 100 pages, and are a leap beyond single melodies because one needs to deal with the vertical aspect and the horizontal aspect of the transcription simultaneously.
Another concept to implement is musical repeats, bar lines at the beginning and ending of sections which are meant to be repeated for a given piece of music. This is a relatively simple concept in print, but the manual spends three chapters covering it, approximately 100 pages.
Other important concepts to add include division of long measures whose transcription would fall at the end of a Braille line limited to forty characters in length, as well as increased support for musical expressions and special note modifiers such as ornaments. In fine, the first sixteen chapters comprise only 150 pages of a 500+ page manual––there is much to be done before BMT can "become an official Braille music transcriber."
With a completed BMT, all the editable musical scores available online will become available to visually-impaired musicians. As alpha code, the music21 project also benefits, because every example needs to be translated into music21 objects before being transcribed into Braille, uncovering plenty of bugs and resulting in many new features being implemented or improved upon. I also believe that new coding techniques developed will carry over towards my musical improvisation software whose further development is currently on hiatus.[3] But most of all, I believe that this project will continue to give me more of the engineering confidence which I have been seeking over the course of my time at MIT.
[1] Introduction to Braille Music Transcription, Second Edition 2005, by Mary Turner De Garmo, revised and edited by Lawrence R. Smith, Music Braille Transcriber.
[2] Marjorie Merryman. The Music Theory Handbook. Schirmer, 1996.
[3] Jose Cabal-Ugaz. "fbRealizer: A 21st-Century Approach to a Centuries-Old Musical System." UROP Summer Proposal, 2011.
I'm also working on free/open source software for Braille music translation. Where can I get the code for your program?
ReplyDeleteHi Daniel -- the code is available as part of Music21 (http://web.mit.edu/music21/) or on Google Code (http://code.google.com/p/music21/). It's open source, but LGPL so if you use it directly please respect that. But you can definitely use it for ideas in your own code. We'd love to have more contributions to it if you'd like to go that route.
ReplyDelete