Next: , Previous: Settings, Up: Reference


5.6 Marks

This is a listing of FOMUS's marks. Some marks accept an optional string or numerical argument (or both). The arguments are given in a syntax similar to how they appear in a .fms file, enclosed by brackets. To create marks in languages such as Lisp or SAL, use a symbol or string to specify the mark and if the mark has arguments, enclose the mark ID and arguments in a list (parentheses in Lisp and braces in SAL). For example, a text mark would be specified as ‘[x "my text"]’ in a .fms file, ‘{"x" "my text"}’ in SAL and ‘'("x" "my text")’ in Lisp. An accent would be ‘[>]’ in a .fms file and ‘">"’ in SAL or Lisp.

!
arguments: [!]

Staccatissimo articulation.

((..
arguments: [((..]

Begin higher-level slur or phrase articulation. Use to indicate phrases marks over slurs created with `(..' and `..)' marks. The `((' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `((r..', `((-..' and `((r-..'.

(..
arguments: [(..]

Begin slur or bowing articulation. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `(r..', `(-..' and `(r-..'.

*
arguments: [* string_text]

Vocal/lyric text syllable.

+
arguments: [+]

Stopped/left-hand pizzicato symbol.

-
arguments: [-]

Tenuto articulation.

.
arguments: [.]

Staccato articulation.

.((.
arguments: [.((.]

Continue higher-level slur or phrase articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `((' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.((r.', `.((-.' and `.((r-.'.

.(.
arguments: [.(.]

Continue slur or bowing articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.(r.', `.(-.' and `.(r-.'.

..)
arguments: [..)]

End slur or bowing articulation. The `)' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..)r', `..)-' and `..)r-'.

..))
arguments: [..))]

End higher-level slur or phrase articulation. Use to indicate phrases over slurs created with `(..' and `..)' marks. The `))' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..))r', `..))-', and `..))r-'.

..<
arguments: [..<]

End crescendo wedge. The `<' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..<1', `..<-' and `..<1-'.

..>
arguments: [..>]

End diminuendo wedge. The `>' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..>1', `..>-' and `..>1-'.

..dash)
arguments: [..dash)]

End dashed slur or bowing articulation. The `)' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..dash)r', `..dash)-' and `..dash)r-'.

..dash))
arguments: [..dash))]

End higher-level dashed slur or phrase articulation. Use to indicate phrases over slurs created with `(..' and `..)' marks. The `))' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..dash))r', `..dash))-' and `..dash))r-'.

..dot)
arguments: [..dot)]

End dotted slur or bowing articulation. The `)' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..dot)r', `..dot)-' and `..dot)r-'.

..dot))
arguments: [..dot))]

End higher-level dotted slur or phrase articulation. Use to indicate phrases over slurs created with `(..' and `..)' marks. The `))' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..dot))r', `..dot))-' and `..dot))r-'.

..grace)
arguments: [..grace)]

End grace note slur articulation. (FOMUS automatically adds these.) The `)' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..grace)r', `..grace)-' and `..grace)r-'.

..ped
arguments: [..ped]

End piano pedal mark. `ped' may be followed by one or more of the following flag characters: `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..ped1', `..ped-' and `..ped1-'. To insure that this mark appears below the bottom staff, it should be defined in a mark event and not attached to a note.

..tup
arguments: [..tup integer>=1]

End a tuplet on this note. If the optional number argument is given, end a tuplet at that nested level.

..x!
arguments: [..x! string_text]

End text spanner in bold face. The text for this usually appears above the staff. The `x!' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..x!1', `..x!-' and `..x!1-'.

..x^
arguments: [..x^ string_text]

End text spanner in italics. The text for this usually appears above the staff or in the middle of a grand staff. The `x^' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..x^1', `..x^-' and `..x^1-'.

..x_
arguments: [..x_ string_text]

End text spanner in italics. The text for this usually appears below the staff or in the middle of a grand staff. The `x_' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `..x_1', `..x_-' and `..x_1-'.

.<.
arguments: [.<.]

Continue crescendo wedge. FOMUS begins/ends wedge marks where these continue marks start/stop. The `<' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.<1.', `.<-.' and `.<1-.'.

.>.
arguments: [.>.]

Continue diminuendo wedge. FOMUS begins/ends wedge marks where these continue marks start/stop. The `>' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.>1.', `.>-.' and `.>1-.'.

.dash((.
arguments: [.dash((.]

Continue higher-level dashed slur or phrase articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `((' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.dash((r.', `.dash((-.' and `.dash((r-.'.

.dash(.
arguments: [.dash(.]

Continue dashed slur or bowing articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.dash(r.', `.dash(-.' and `.dash(r-.'.

.dot((.
arguments: [.dot((.]

Continue higher-level dotted slur or phrase articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `((' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.dot((r.', `.dot((-.', and `.dot((r-.'.

.dot(.
arguments: [.dot(.]

Continue dotted slur or bowing articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.dot(r.', `.dot(-.' and `.dot(r-.'.

.grace(.
arguments: [.grace(.]

Continue grace note slur articulation. FOMUS begins/ends slur marks where these continue marks start/stop. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.grace(r.', `.grace(-.' and `.grace(r-.'.

.ped.
arguments: [.ped.]

Continue piano pedal mark. `ped' may be followed by one or more of the following flag characters: `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.ped1.', `.ped-.' and `.ped1-.'. To insure that this mark appears below the bottom staff, it should be defined in a mark event and not attached to a note.

.x!.
arguments: [.x!. string_text]

Continue text spanner in bold face. The text for this usually appears above the staff. FOMUS begins/ends text marks where these continue marks start/stop. The `x!' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.x!1.', `.x!-.' and `.x!1-.'.

.x^.
arguments: [.x^. string_text]

Continue text spanner in italics. FOMUS begins/ends text marks where these continue marks start/stop. The text for this usually appears above the staff or in the middle of a grand staff. The `x^' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.x^1.', `.x^-.' and `.x^1-.'.

.x_.
arguments: [.x_. string_text]

Continue text spanner in italics. FOMUS begins/ends text marks where these continue marks start/stop. The text for this usually appears below the staff or in the middle of a grand staff. The `x_' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `.x_1.', `.x_-.' and `.x_1-.'.

/
arguments: [/]

Attach a slash to a group of grace notes.

/.
arguments: [/.]

Mezzo staccato or portato (combined tenuto and staccato mark) articulation.

0
arguments: [0]

Harmonic symbol.

<..
arguments: [<..]

Begin crescendo wedge. The `<' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `<1..', `<-..' and `<1-..'.

>
arguments: [>]

Accent articulation.

>..
arguments: [>..]

Begin diminuendo wedge. The `>' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `>1..', `>-..' and `>1-..'.

^
arguments: [^]

Martellato articulation.

arco
arguments: [arco]

String arco text marking. You usually shouldn't specify this directly (see the `pizz' marking). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

arp
arguments: [arp]

Arpeggio. Applies to all notes in the same chord and only if a chord (two or more simultaneous notes) exists.

arp^
arguments: [arp^]

Upwards arpeggio. Applies to all notes in the same chord and only if a chord (two or more simultaneous notes) exists.

arp_
arguments: [arp_]

Downwards arpeggio. Applies to all notes in the same chord and only if a chord (two or more simultaneous notes) exists.

artharm-base
arguments: [artharm-base]

Indicates that the note is the base pitch to play on the string in an artificial harmonic.

artharm-sounding
arguments: [artharm-sounding]

Indicates that the note is the sounding pitch in an artificial harmonic.

artharm-touched
arguments: [artharm-touched]

Indicates that the note is the place to touch on the string in an artificial harmonic.

bellsup
arguments: [bellsup]

"Bells up" text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

break<
arguments: [break<]

System break, occurring at the barline at or after the attack time of the note.

break>
arguments: [break>]

System break, occurring at the barline at or after the release time of the note.

breath
arguments: [breath]

"Breath tone" text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

breath<
arguments: [breath<]

A breath mark placed before the note.

breath>
arguments: [breath>]

A breath mark placed after the note.

cuivre
arguments: [cuivre]

Cuivré (or brassy) text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

damp
arguments: [damp]

Dampen symbol (cross plus circle).

dash((..
arguments: [dash((..]

Begin higher-level dashed slur or phrase articulation. Use to indicate phrases marks over slurs created with `(..' and `..)' marks. The `((' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `dash((r..', `dash((-..' and `dash((r-..'.

dash(..
arguments: [dash(..]

Begin dashed slur or bowing articulation. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `dash(r..', `dash(-..' and `dash(r-..'.

dot((..
arguments: [dot((..]

Begin higher-level dotted slur or phrase articulation. Use to indicate phrases marks over slurs created with `(..' and `..)' marks. The `((' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `dot((r..', `dot((-..', and `dot((r-..'.

dot(..
arguments: [dot(..]

Begin dotted slur or bowing articulation. The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `dot(r..', `dot(-..' and `dot(r-..'.

downbow
arguments: [downbow]

Down-bow symbol.

dyn
arguments: [dyn number]

An unknown dynamic marking. The numeric dynamic value for the note event is scaled to a proper dynamic text mark using the settings `dyn-range' and `dynsym-range'. An optional numeric argument overrides the note event's dynamic value.

etouf
arguments: [etouf]

Dampen text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

f
arguments: [f]

Forte dynamic level.

ferm
arguments: [ferm]

Fermata marking.

ferm-long
arguments: [ferm-long]

Long fermata marking.

ferm-short
arguments: [ferm-short]

Short fermata marking.

ferm-verylong
arguments: [ferm-verylong]

Very long fermata marking.

ff
arguments: [ff]

Fortissimo dynamic level.

fff
arguments: [fff]

Fortississimo dynamic level.

ffff
arguments: [ffff]

Fortissississimo dynamic level.

fffz
arguments: [fffz]

Triple forzando dynamic marking.

ffz
arguments: [ffz]

Double forzando dynamic marking.

flaut
arguments: [flaut]

"near the fingerboard" text marking.To use, insert `flaut' markings on every note that is to be played flautando. FOMUS then places "flautando" and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

flt
arguments: [flt]

Fluttertongue text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

fp
arguments: [fp]

Forte-piano dynamic marking.

fz
arguments: [fz]

Forzando dynamic marking.

fzp
arguments: [fzp]

Forzando-piano dynamic marking.

gliss<
arguments: [gliss<]

Glissando sign, connecting to the previous note in the same voice.

gliss>
arguments: [gliss>]

Glissando sign, connecting to the next note in the same voice.

grace(..
arguments: [grace(..]

Begin grace note slur articulation. (FOMUS automatically adds these.) The `(' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `grace(r..', `grace(-..' and `grace(r-..'.

leg
arguments: [leg]

Legato text marking. To use, insert `legato' markings on every note that is to be played legato. FOMUS then places "legato" and "non legato" texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

legno
arguments: [legno]

"with the wood" text marking. To use, insert `legno' markings on every note that is to be played col legno. FOMUS then places "col legno" and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

longtr
arguments: [longtr]

The main note of a trill. This should be used together with `longtr2' on two simultaneous notes to specify the entire trill. The `FIXME' setting specifies whether trills greater than a single step are automatically notated as unmeasured tremolos instead (unison trills are always converted to tremolos). Otherwise a small note in parentheses is used.

longtr2
arguments: [longtr2]

The auxiliary note of a trill, usually notated as an accidental above or below the trill sign. This should be used together with `longtr' on two simultaneous notes to specify the entire trill. The auxiliary note is deleted during FOMUS's processing, so any additional marks should be placed in the base `longtr' trill note.

lv
arguments: [lv]

"Let vibrate" text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

mf
arguments: [mf]

Mezzo-forte dynamic level.

moltoleg
arguments: [moltoleg]

Molto legato text marking. To use, insert `molto legato' markings on every note that is to be played molto legato. FOMUS then places "molto legato" and "non legato" texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

moltovib
arguments: [moltovib]

Molto vibrato text marking. To use, insert `moltovib' markings on every note that is to be played molto vibrato. FOMUS then places "molto vib." and "non vib." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

mp
arguments: [mp]

Mezzo-piano dynamic level.

mute
arguments: [mute]

Mute text marking. To use, insert `mute' markings on every note that is to be played with the mute on. FOMUS then places "con sord." and "senza sord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

natharm-sounding
arguments: [natharm-sounding]

Indicates that the note is the sounding pitch in a natural harmonic.

natharm-string
arguments: [natharm-string]

Indicates that the note is the pitch of the open string in a natural harmonic.

natharm-touched
arguments: [natharm-touched]

Indicates that the note is the place to touch on the string in a natural harmonic.

nonleg
arguments: [nonleg]

Nonlegato text marking. You usually shouldn't specify this directly (see the `leg' and `moltoleg' markings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

nonvib
arguments: [nonvib]

Non vibrato text marking. You usually shouldn't specify this directly (see the `vib' and `moltovib' markings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

o
arguments: [o]

Open string/unstopped symbol.

ord
arguments: [ord]

Naturale/ordinario/normale text marking. You usually shouldn't specify this directly (e.g., see the `pont' and `tasto' markings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

p
arguments: [p]

Piano dynamic level.

ped..
arguments: [ped..]

Begin piano pedal mark. `ped' may be followed by one or more of the following flag characters: `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `ped1..', `ped-..' and `ped1-..'. To insure that this mark appears below the bottom staff, it should be defined in a mark event and not attached to a note.

pizz
arguments: [pizz]

String pizzicato text marking. To use, insert `pizz' markings on every note that is to be played pizzicato. FOMUS then places "pizz." and "arco" texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

pont
arguments: [pont]

"near the bridge" text marking. To use, insert `pont' markings on every note that is to be played sul ponticello. FOMUS then places "sul pont." and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

port<
arguments: [port<]

Portamento sign, connecting to the previous note in the same voice.

port>
arguments: [port>]

Portamento sign, connecting to the next note in the same voice.

pp
arguments: [pp]

Pianissimo dynamic level.

ppp
arguments: [ppp]

Pianississimo dynamic level.

pppp
arguments: [pppp]

Pianissississimo dynamic level.

ppppp
arguments: [ppppp]

Pianississississimo dynamic level.

pppppp
arguments: [pppppp]

Pianissississississimo dynamic level.

punta
arguments: [punta]

"at the tip" text marking. To use, insert `punta' markings on every note that is to be played punta d'arco. FOMUS then places "punta d'arco" and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

rf
arguments: [rf]

Rinforzando dynamic marking.

rfz
arguments: [rfz]

Rinforzando dynamic marking.

ric
arguments: [ric]

Ricochet or jeté text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

salt
arguments: [salt]

Saltando text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

sf
arguments: [sf]

Sforzando dynamic marking.

sff
arguments: [sff]

Double sforzando dynamic marking.

sfff
arguments: [sfff]

Triple sforzando dynamic marking.

sfffz
arguments: [sfffz]

Triple sforzato dynamic marking.

sffz
arguments: [sffz]

Double sforzato dynamic marking.

sfp
arguments: [sfp]

Sforzando-piano dynamic marking.

sfz
arguments: [sfz]

Sforzato dynamic marking.

sfzp
arguments: [sfzp]

Sforzato-piano dynamic marking.

slap
arguments: [slap]

"Slap tongued" text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

snap
arguments: [snap]

Snap pizzicato symbol.

snappizz
arguments: [snappizz]

Snap pizzicato symbol.

spic
arguments: [spic]

Spiccato text marking. To use, insert `spic' markings on every note that is to be played spiccato. FOMUS then places "spicc" and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

sul
arguments: [sul integer0..128]

Mark for indicating which string to play on. The `sul-style' setting specifies how this is to be interpretted and printed in the score.

table
arguments: [table]

"near the soundboard" text marking. The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

tall
arguments: [tall]

"at the frog" text marking. To use, insert `tall' markings on every note that is to be played al tallone. FOMUS then places "al tallone" and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

tasto
arguments: [tasto]

"on the fingerboard" text marking. To use, insert `tasto' markings on every note that is to be played sul tasto. FOMUS then places "sul tasto" and "ord." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

tempo
arguments: [tempo string_text real>0]

Tempo marking. The string argument is placed above the staff at the location of the mark. If a `*' character is found in the string, it is replaced by a note that represents the value of the `beat' setting in that measure. If two `*' characters are found with a rational or mixed number between them, then this value overrides the value of `beat'. If a `#' character is found in the string and a numerical argument is supplied, the `#' is replaced by that number. For example, the string "Allegro, * = #" and a numerical argument of 120 translates to "Allegro, quarter-note = 120" (where `quarter-note' is an actual notated quarter note and the value of `beat' is 1/4 for that measure). The string "Allegro (*1/8* = #)" and a numerical argument of 108 translates to "Allegro (eighth-note = 108)". The string "Allegro (*3/8* = #)" and a numerical argument of 108 translates to "Allegro (dotted-quarter-note = 108)". An empty string and a numerical argument of 60 translates to "quarter-note = 60" (assuming `beat' is set to 1/4). To insure that this mark appears above the top staff, it should be defined in a mark event and not attached to a note.

trem
arguments: [trem rational>0]

A tremolo. The optional numeric argument indicates the duration of a single tremolo beat. No argument indicates an unmeasured tremolo. When used together with `trem2' on two sets of simultaneous pitches/chords, specifies a keyboard-style tremelo with `trem' indicating the first chord and `trem2' indicating the second. The `FIXME' setting specifies whether unmeasured semitone/wholetone tremolos are automatically notated as trills instead.

trem2
arguments: [trem2]

The second chord in a keyboard-style tremelo. This must be used with `trem'.

tup..
arguments: [tup.. integer>=1]

Begin a tuplet on this note. If the optional number argument is given, begin a tuplet at that nested level.

unmute
arguments: [unmute]

Unmute text marking. You usually shouldn't specify this directly (see the `mute' marking). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

upbow
arguments: [upbow]

Up-bow symbol.

vib
arguments: [vib]

Vibrato text marking. To use, insert `vib' markings on every note that is to be played with vibrato. FOMUS then places "vib." and "non vib." texts over the correct notes automatically. (This behavior can be disabled if desired–see the 'mark-group-defs' and 'mark-groups' settings). The precise text that appears in the score is controlled by the `default-marktexts' and `marktexts' settings.

x
arguments: [x string_text]

Text marking attached to a notehead. The text for this usually appears above the note in a normal (non-italic) typeface.

x!
arguments: [x! string_text]

Text marking in bold face. The text usually appears above the staff.

x!..
arguments: [x!.. string_text]

Begin text spanner in bold face. The text for this usually appears above the staff. The `x!' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `x!1..', `x!-..' and `x!1-..'.

x^
arguments: [x^ string_text]

Text marking in italics. The text usually appears above the staff or in the middle of a grand staff.

x^..
arguments: [x^.. string_text]

Begin text spanner in italics. The text for this usually appears above the staff or in the middle of a grand staff. The `x^' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `x^1..', `x^-..' and `x^1-..'.

x_
arguments: [x_ string_text]

Text marking in italics. The text usually appears below the staff or in the middle of a grand staff.

x_..
arguments: [x_.. string_text]

Begin text spanner in italics. The text for this usually appears below the staff or in the middle of a grand staff. The `x_' may be followed by one or more of the following flag characters: `r' (the mark can span rests), `n' (the mark cannot span rests), `1' (the mark can span one note), `m' (the mark cannot span one note), `-' (the beginning and ends of the mark can touch) and `|' (the beginning and ends of the mark cannot touch). Examples are `x_1..', `x_-..' and `x_1-..'.

~
arguments: [~]

Forces a tie to the next note.