![]() ![]() MusicXML provides two XSLT stylesheets to convert back and forth between the two document types. Having two different structures does not work well if there is no automatic way to switch between them. The measure is primary, and musical parts are contained within each measure. For a timewise document, the root element is. The musical part is primary, and measures are contained within each part. For a partwise document, the root element is. This is why MusicXML has two different score formats, each with its own root element. David Huron, a music cognition specialist and the inventor of Humdrum, advised us to make sure we could represent music both ways, and be able to switch between them easily. The answer is different for every music application. ![]() How do we reconcile this? Should the horizontal organization of musical parts be primary, or should the vertical organization of musical measures? XML represents data in a hierarchy, but musical scores are more like a lattice. It has multiple parts, one per player, and multiple measures. Say we have a piece of music for two or more people to play. The Structure of MusicXML Files Adapting Musical Scores to a Hierarchy ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |