MuseData Example: slur orientation - Revision history

Craig at 19:11, 30 January 2011

2011-01-30T19:11:14Z

← Older revision		Revision as of 19:11, 30 January 2011
Line 59:		Line 59:
	//		//
	</pre>		</pre>



			{{MuseDataExamples}}

Craig at 15:45, 25 January 2011

2011-01-25T15:45:12Z

← Older revision		Revision as of 15:45, 25 January 2011
Line 1:		Line 1:
	Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u</tt> to a slur. More information can be found in the [[Media:Stage2-specs.html \| official MuseData specification]]. The following graphical notation example was printed from the MuseData source code found below using [[muse2ps]].		Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u</tt> to a slur starting code. Slur starting codes are the characters "<tt>(</tt>", "<tt>[</tt>", "<tt>{</tt>", and "<tt>z</tt>" anywhere in columns 32 through 43 of note/rest data lines. Slur orientations are stored in print suggestion lines which start with "<tt>P</tt>" and contains a list of print suggestions referenced to the previous non-sound/print line, and indexed by column number, offset from 1. In the following examples the slur start code "<tt>(</tt>" is found in the 32nd column of the line, so a print suggestion to indicate that the slur should be placed above the notes is "<tt>C32:o</tt>" which means ''pass the "<tt>o</tt>" parameter to the attribute found (starting) at column 32 of the previous non-sound/print line''. In the following example, this attribute is a slur, and an "<tt>o</tt>" print suggestion means place the slur over the notes to which it applies. The first two lines in the following example are just comments which number the columns in the text so that it is easier to see that the 32nd column is where the
			slur is located.
			<pre>
			@ 1 2 3
			@2345678901234567890123456789012
			C4 1 1 q u (
			P C32:o
			</pre>

			More information can be found in the [[Media:Stage2-specs.html \| official MuseData specification]]. The following graphical notation example was printed from the MuseData source code found below using [[muse2ps]].

	<center>		<center>

Craig at 10:45, 25 January 2011

2011-01-25T10:45:07Z

← Older revision		Revision as of 10:45, 25 January 2011
Line 10:		Line 10:
	Header Record 2		Header Record 2
	Header Record 3		Header Record 3
	~~Header Record 4~~		01/24/2011 C. Sapp
	WK#:1 MV#:1		WK#:1 MV#:1
	Header Record 6		Header Record 6

Craig at 23:28, 24 January 2011

2011-01-24T23:28:42Z

← Older revision		Revision as of 23:28, 24 January 2011
Line 1:		Line 1:
	Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u</tt> to a slur. More information can be found in the [[~~File~~:Stage2-specs.html\|official ~~stage 2~~ specification]].		Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u</tt> to a slur. More information can be found in the [[Media:Stage2-specs.html \| official MuseData specification]]. The following graphical notation example was printed from the MuseData source code found below using [[muse2ps]].

			<center>
			[[File:mdex-slur-orientation.png]]
			</center>

			<pre>
			@muse2psv1==z21jT^Print directive: slur orientation^
			Header Record 1
			Header Record 2
			Header Record 3
			Header Record 4
			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
			//
			</pre>

Craig: created page

2011-01-24T23:00:35Z

created page

← Older revision		Revision as of 23:00, 24 January 2011
Line 1:		Line 1:
	Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u></tt> to a slur. More information can be found in the [[File:Stage2-~~spec~~.html\|official stage 2 ~~specificiation~~]].		Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u</tt> to a slur. More information can be found in the [[File:Stage2-specs.html\|official stage 2 specification]].

Craig: created page

2011-01-24T22:59:48Z

created page

New page

Slurs can be forced ''over'' or ''under'' by giving the print suggestion <tt>o</tt> or <tt>u></tt> to a slur. More information can be found in the [[File:Stage2-spec.html|official stage 2 specificiation]].