Difference between revisions of "MuseData Example: slur orientation"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
Header Record 2 | Header Record 2 | ||
Header Record 3 | Header Record 3 | ||
− | + | 01/24/2011 C. Sapp | |
WK#:1 MV#:1 | WK#:1 MV#:1 | ||
Header Record 6 | Header Record 6 |
Revision as of 10:45, 25 January 2011
Slurs can be forced over or under by giving the print suggestion o or u to a slur. More information can be found in the official MuseData specification. The following graphical notation example was printed from the MuseData source code found below using muse2ps.
@muse2psv1==z21jT^Print directive: slur orientation^ Header Record 1 Header Record 2 Header Record 3 01/24/2011 C. Sapp WK#:1 MV#:1 Header Record 6 Header Record 7 Header Record 8 Group memberships: score score: part 1 of 1 $ Q:1 T:4/4 C:4 @ default location of slur is under the notes: C4 1 1 q u ( D4 1 1 q u E4 1 1 q u F4 1 1 q u ) measure 2 @ force the slur over the notes by giving "o" print directive for slur at column32: C4 1 1 q u ( P C32:o D4 1 1 q u E4 1 1 q u F4 1 1 q u ) measure 3 @ default location of slur is over the notes: C5 1 1 q d ( D5 1 1 q d E5 1 1 q d F5 1 1 q d ) measure 4 @ force the slur under the notes by giving "u" print directive for slur at column 32: C5 1 1 q d ( P C32:u D5 1 1 q d E5 1 1 q d F5 1 1 q d ) mheavy2 /END /eof //