Humdrum Representation for Metric Hierarchy
**metpos -- position in metric hierarchy
representation consists of simply a set of numerical
values indicating the order of events.
spine simply encodes a set of ascending integers
marking the succession of events:
representation also recognizes **kern-like
The presence of an equals-sign
in the first column of a
spine is used to denote a barline.
Immediately after the equals sign there may follow an optional integer value
indicating the measure number (e.g.
-- for measure 107).
In addition, a lower-case alphabetic character may be appended to the measure
number -- as in:
This convention permits the user to distinguish measure numbers for
first and second endings.
Measure numbers refer to the information immediately
following the barline, thus the token
occurs just prior to the encoded beats for measure 23.
Double barlines are indicated by using two or more successive equals signs
Several consecutive equals signs may be encoded
in order to enhance readability (e.g.
An additional attribute for barlines is the
-- which is represented by the-- icolon (;).
Thus the token
means that the barline starting measure number 4 has a
pause written above or below it, while the token
means that a double barline contains a pause indication.
It is recommended that files containing predominantly
data should be given names with the distinguishing `.mtp' extension.
The following table summarizes the
mappings of signifiers and signifieds.
Summary of **metpos Signifiers
|.||fractional delimiter; null token|
A sample document is given below:
The following Humdrum commands accept **metpos encoded data as inputs:
The following Humdrum command produces **metpos data as output:
|synco||measure degree of metric syncopation|
|urrhythm||characterize the rhythmic prototypes in a passage|
|metpos||generate metric position values for timebase-formatted
**kern or **recip inputs|
The following tandem interpretations can be used in conjunction with
Tandem interpretations for **metpos