Difference between revisions of "MusicXML for Efficient Rehearsals"
| (22 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | By: Yuan Wen | ||
| + | |||
'''The Problem:''' | '''The Problem:''' | ||
| + | |||
In orchestra rehearsal, I often see my professor change a bow marking or ask us to emphasize a dynamic not written in the original piece. Only a certain number of students have a pencil to document the change. When playing, the music becomes harder to read after crossing out the arranger’s originally printed markings. There are also inconsistencies when some document the change and some do not. A section can be off by a bow marking that is visually unappealing and affects the dynamic allotted from an up bow vs a down bow. | In orchestra rehearsal, I often see my professor change a bow marking or ask us to emphasize a dynamic not written in the original piece. Only a certain number of students have a pencil to document the change. When playing, the music becomes harder to read after crossing out the arranger’s originally printed markings. There are also inconsistencies when some document the change and some do not. A section can be off by a bow marking that is visually unappealing and affects the dynamic allotted from an up bow vs a down bow. | ||
I want to research and propose a feasible way for the entire orchestra to be on the same standard for the piece. Students absent will still know the changes documented for that day. In the technology era, I find it inefficient to document changes by pen and paper when resources like the computer and internet are available. | I want to research and propose a feasible way for the entire orchestra to be on the same standard for the piece. Students absent will still know the changes documented for that day. In the technology era, I find it inefficient to document changes by pen and paper when resources like the computer and internet are available. | ||
| + | ''MIDI vs MusicXML'' | ||
| + | |||
| + | MusicXML contains dynamics markings, tempo markings, slurs, and specific semantics about the piece. MIDI contains the information about a performance. MIDI does not know the difference between a F-Sharp and G-Flat. It also does not represent stem direction, beams, repeats, slurs, measures, and many other aspects of notation. | ||
'''The Plan:''' | '''The Plan:''' | ||
| + | |||
It is the user’s responsibility to know the copyright laws of the piece they are modifying. | It is the user’s responsibility to know the copyright laws of the piece they are modifying. | ||
Whenever the orchestra starts a new piece, it is on paper. There is software that interpret sheet music or printed scores into editable or playable form. [1] The software is called optical music recognition software. Once captured digitally, the music can be converted to a MusicXML file. MusicXML is a markup language used to represent sheet music. Reading and writing a MusicXML file is the same thing as a HTML file. | Whenever the orchestra starts a new piece, it is on paper. There is software that interpret sheet music or printed scores into editable or playable form. [1] The software is called optical music recognition software. Once captured digitally, the music can be converted to a MusicXML file. MusicXML is a markup language used to represent sheet music. Reading and writing a MusicXML file is the same thing as a HTML file. | ||
| Line 10: | Line 17: | ||
When the School has enough money, tablets should be locked on music stands for electronic viewing of the most recent MusicXML file of their piece. Alternatively, the professor can print out a most recent copy for the orchestra to play. | When the School has enough money, tablets should be locked on music stands for electronic viewing of the most recent MusicXML file of their piece. Alternatively, the professor can print out a most recent copy for the orchestra to play. | ||
| − | [[File:Ywenmain.png|1200px | + | [[File:Ywenmain.png|1200px]] |
'''The Technologies Available:''' | '''The Technologies Available:''' | ||
| + | |||
IMSLP: for public domain music pdfs | IMSLP: for public domain music pdfs | ||
| + | |||
PDF/Image -> MusicXML Converter: Audiveris, Myriad | PDF/Image -> MusicXML Converter: Audiveris, Myriad | ||
| + | |||
MusicXML editing programs: Finale, Sibelius, MuseScore, SmartScore | MusicXML editing programs: Finale, Sibelius, MuseScore, SmartScore | ||
| + | |||
Online clouds: Apple cloud, WPI server, Google Drive, BlackBoard | Online clouds: Apple cloud, WPI server, Google Drive, BlackBoard | ||
| + | |||
Viewing MusicXML: HTML5 canvas element and Javascript within a web browser. Examples include: installing Myriad Music Plug in, Finale Notepad | Viewing MusicXML: HTML5 canvas element and Javascript within a web browser. Examples include: installing Myriad Music Plug in, Finale Notepad | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
'''Trial Run''' | '''Trial Run''' | ||
| − | |||
| − | [[File:Convert.png|800px | + | Using Myriad PDFToMusic (Trial Version) and Finale NotePad 2012 |
| + | |||
| + | Video: | ||
| + | |||
| + | <mediaplayer>http://media.wpi.edu/Academics/Depts/HUA/Manzo/ywen2/VideoDemo.mp4</mediaplayer> | ||
| + | |||
| + | |||
| + | |||
| + | Conversion of PDF to MusicXML: | ||
| + | |||
| + | [[File:Convert.png|800px|Conversion of PDF to MusicXML]] | ||
| + | |||
| + | Measure 1 of XML: | ||
| + | |||
| + | [[File:Measure1.png|800px]] | ||
| + | |||
| + | Viewing of MusicXML before edit: | ||
| + | |||
| + | [[File:Before.png|800px|Viewing of MusicXML before edit]] | ||
| + | |||
| + | Added a crescendo marking: | ||
| + | |||
| + | [[File:Edit2.png|800px|Added a crescendo marking]] | ||
| − | + | Additional options are available, such as bowings: | |
| − | [[File: | + | [[File:Options.png|800px|Additional options are available, such as bowings]] |
| − | + | '''Conclusion''' | |
| + | |||
| + | After doing a trial run of Bach's piece, I found editing the sheet music very easy. In practicality's sake, I would recommend the orchestra to use musicXML for the finalized concert version only. The only way the orchestra can constantly be up to date with updated bowings is to print out a updated copy each rehearsal(waste of paper), or use ipads for music stands (a hope but financially expensive. At the conclusion of this research project, I think the conductor should keep a master musicXML file and edit on that. When the concert comes, he/she should print out the most up to date version, and pass it out among the students. The students would then add any additional markings by hand. As an alternative, the conductor may share the musicXML file and students can use Finale Notepad to add any additional markings. | ||
| + | Finale Notepad 2012 was free for download and use. The PDF to MusicXML program by Myriad costs $199 for personal use. Audiveris is open source and free, but I personally had trouble using it. | ||
| Line 48: | Line 79: | ||
5) "MusicXML." Wikipedia. Wikimedia Foundation, n.d. Web. 14 Apr. 2015. <http://en.wikipedia.org/wiki/MusicXML>. | 5) "MusicXML." Wikipedia. Wikimedia Foundation, n.d. Web. 14 Apr. 2015. <http://en.wikipedia.org/wiki/MusicXML>. | ||
| + | |||
| + | [[Category:Pedagogy, Theory, and Research Resources]] | ||
Latest revision as of 19:02, 30 April 2015
By: Yuan Wen
The Problem:
In orchestra rehearsal, I often see my professor change a bow marking or ask us to emphasize a dynamic not written in the original piece. Only a certain number of students have a pencil to document the change. When playing, the music becomes harder to read after crossing out the arranger’s originally printed markings. There are also inconsistencies when some document the change and some do not. A section can be off by a bow marking that is visually unappealing and affects the dynamic allotted from an up bow vs a down bow. I want to research and propose a feasible way for the entire orchestra to be on the same standard for the piece. Students absent will still know the changes documented for that day. In the technology era, I find it inefficient to document changes by pen and paper when resources like the computer and internet are available.
MIDI vs MusicXML
MusicXML contains dynamics markings, tempo markings, slurs, and specific semantics about the piece. MIDI contains the information about a performance. MIDI does not know the difference between a F-Sharp and G-Flat. It also does not represent stem direction, beams, repeats, slurs, measures, and many other aspects of notation.
The Plan:
It is the user’s responsibility to know the copyright laws of the piece they are modifying. Whenever the orchestra starts a new piece, it is on paper. There is software that interpret sheet music or printed scores into editable or playable form. [1] The software is called optical music recognition software. Once captured digitally, the music can be converted to a MusicXML file. MusicXML is a markup language used to represent sheet music. Reading and writing a MusicXML file is the same thing as a HTML file. Once the MusicXML file is read, the professor uploads the file to an online cloud (ex. Google Drive.) All members of the orchestra have access to the cloud. Now, whenever the professor wants to change a bowing, he/she opens up a MusicXML editing software like Finale, makes the edit, and pushes the change to Google Drive. It is important to also document the change for timeline reference. All members of the orchestra have the change. When the School has enough money, tablets should be locked on music stands for electronic viewing of the most recent MusicXML file of their piece. Alternatively, the professor can print out a most recent copy for the orchestra to play.
The Technologies Available:
IMSLP: for public domain music pdfs
PDF/Image -> MusicXML Converter: Audiveris, Myriad
MusicXML editing programs: Finale, Sibelius, MuseScore, SmartScore
Online clouds: Apple cloud, WPI server, Google Drive, BlackBoard
Viewing MusicXML: HTML5 canvas element and Javascript within a web browser. Examples include: installing Myriad Music Plug in, Finale Notepad
Trial Run
Using Myriad PDFToMusic (Trial Version) and Finale NotePad 2012
Video:
The media player is loading...
Conversion of PDF to MusicXML:
Measure 1 of XML:
Viewing of MusicXML before edit:
Added a crescendo marking:
Additional options are available, such as bowings:
Conclusion
After doing a trial run of Bach's piece, I found editing the sheet music very easy. In practicality's sake, I would recommend the orchestra to use musicXML for the finalized concert version only. The only way the orchestra can constantly be up to date with updated bowings is to print out a updated copy each rehearsal(waste of paper), or use ipads for music stands (a hope but financially expensive. At the conclusion of this research project, I think the conductor should keep a master musicXML file and edit on that. When the concert comes, he/she should print out the most up to date version, and pass it out among the students. The students would then add any additional markings by hand. As an alternative, the conductor may share the musicXML file and students can use Finale Notepad to add any additional markings. Finale Notepad 2012 was free for download and use. The PDF to MusicXML program by Myriad costs $199 for personal use. Audiveris is open source and free, but I personally had trouble using it.
The Sources:
1) " English German Japanese Music in MusicXML." MusicXML. MAKEMUSIC, INC, 2015. Web. 14 Apr. 2015. <http://www.musicxml.com/music-in-musicxml/>.
2) "HTML5 MusicXML Viewer." HTML5 MusicXML Viewer. N.p., n.d. Web. 14 Apr. 2015. <http://musicxml-viewer.com/>.
3) "MuseScore." File Format. N.p., n.d. Web. 14 Apr. 2015. <https://musescore.org/en/handbook/file-format>.
4) "Music OCR." Wikipedia. Wikimedia Foundation, n.d. Web. 14 Apr. 2015. <http://en.wikipedia.org/wiki/Music_OCR>.
5) "MusicXML." Wikipedia. Wikimedia Foundation, n.d. Web. 14 Apr. 2015. <http://en.wikipedia.org/wiki/MusicXML>.