7.1 The Staff Definition7.1.1 Defining the Notation7.1.2 The Instrument Setup and Tuning7.2 Encoding Tablatures7.2.1 Basic Structure7.2.2 Vertical Organisation in German Lute Tablature
This chapter describes the MEI.stringtab module (which will be renamed to MEI.tablature in a future version). The MEI.stringtab module is used to record basic tablature notation. It is designed primarily for plucked-string instruments, such as guitar and lute.
Tablatures come in a variety of types or notations, varying according to instrument but also according to historical context. The notation used is defined on the staffDef element using the notationtype attribute. Possible values are: tab.guitar, tab.lute.italian, tab.lute.french and tab.lute.german.
The lines attribute on the staffDef element is used to define the number of horizontal lines used in a staff.
Because string tablatures specify which frets and strings to play on the instrument, rather than abstract pitches, it is necessary to know the tuning and setup of the instrument.
Guitar-like instruments can be described in terms of the number of strings they have, but often the strings are grouped and notated as if those groups were a single string. Examples include mandolins and 12-string guitars. To make this distinction explicit, we use "string" exclusively to refer to physical strings. To refer to the notated version, which may consist of one or more physical strings, we use the historical term, "course". Thus, both a 6-string and a 12-string guitar are 6-course instruments.
The course tuning for 6- and 12-string guitars are the same — so they can both play from the same tablatures. Our tuning specification supports indicating course tunings on their own, or string tunings as well.
The tuning element is used inside staffDef to describe the pitches of the open strings of the instrument. In the simplest cases, the tuning can be named from a standard list. For example, to specify the most common tuning of the guitar:
or, for six-course lute:
Custom tuning may be needed when no existing tuning.standard value applies. The course element gives the tuning of each course. n captures the course number (counting from the course closest to the player’s feet when the instrument is played), pname the pitch information and oct the octave information.
For standard classical guitar tuning, the tuning element might look like this:
Chromatic alteration of the open string’s pitch may be indicated by adding the accid. For example, a guitar in E-flat tuning might look like this:
Where the specific instrumental setup is important, the stringing of the instrument can also be specified. The example below is a common way to string and tune a 6-course renaissance lute. The pitch on course indicates how the resulting note would normally be transcribed in score, and would often be derived from the lowest sounding pitch.
Unlike CMN, note elements in tablature do not have an explicit pitch, but indicate playing instructions (i.e., where to place fingers on the fingerboard and when to play the strings). The tab.course attribute is used to capture which course is to be struck, and tab.fret specifies on which fret of the fretboard the player should stop the course. A value of 0 for tab.fret refers to an unstopped, open course; a value of 1 refers to the first fret; and so on. Course order is the same as that given in the course elements.
A set of vertically-aligned symbols is indicated by tabGrp, i.e., a chord whose notes are played at the same time, and have the same (minimum) notated duration. The duration of a tabGrp may be indicated visually with a rhythm symbol, whose presence is encoded using the tabDurSym element. In many cases, the rhythm sign is omitted where it would repeat the previous value. For this reason tabDurSym is optional, and the durational value of the tabGrp is encoded as dur.
As with CMN, rhythm flags joined together can be indicated using beam. Since every note in a beam group always has a rhythm sign, tabDurSym should be used for beamed notes.
Tablatures usually indicate a rest by a rhythm sign that has no symbols for notes underneath. We can encode this with a tabDurSym that is the only element of a tabGrp.
In some rare cases, special rest symbols may also appear below the rhythm sign. This can be encoded by adding a rest to the tabGrp.
Unlike other types of lute tablature, German lute tablature encodes the course and the fret information simultaneously, and in that sense is different from the staff-based (i.e., Italian and French) lute tablature types. Vertical positioning thus does not correspond to the course to be played, and may instead reflect aesthetic or layout conventions or, in some cases, indicate voice leading. Mechanisms for encoding vertical organisation of the tablature notes in horizontal strands (i.e., ‘rows’ or ‘lines’) are thus required.
The mechanisms presented in this section may be used to encode German lute tablature according to the following four scenarios. Note that, in the encoding, the order of notes in tabGrp is significant — the first encoded note is the top symbol drawn in the chord, while the last encoded note that is a child of tabGrp is the bottom symbol in the chord.
Example encoding:
Example encoding — note the usage of tab.align on the staffDef:
Example encoding (m. 1) — note the usage of lines and tab.anchorline on the staffDef:
Example encoding (m. 1) — note the usage of lines and tab.anchorline on the staffDef:
Example encoding (mm. 1–3) — note the usage of lines on the staffDef and tab.line on the notes.
In the above example, it is the case that the vertical positioning is suggestive of voice-leading. To explicitly capture this information, layers can be specified via layer on note. These can be associated with a layer definition in the layerDef within the staffDef if desired.
Example encoding (m. 3) — note the usage of layer on the notes.