This page lists exclusive interpretations (**adata, **bdata and **cdata) that display data spines as text in graphical music notation.

Certain tandem spines are be displayed by default when rendering music notation from Humdurm data. This page describes how to display data spines that are otherwise ignored. This can be done by using **adata, **bdata, **cdata or *vdata spines to display other spine types as lines of text in the music notation.

As an example, **harm is one data format that is converted from text format into a more graphical form when displaying music:

Other exclusive interpretations that are displayed by default in graphical notation include **deg, **degree, **dynam, **fb (figured bass), **fa (figured bass above the staff), and **fing (fingerings).

To display **harm data spines as text in the score rather than graphical renderings, change **harm to **cdata, where “cdata” means “chord-like data”:

The data type of the original spine can be preserved by adding a dash after **cdata followed by original exclusive interpretation:

Here is an example of restoring the original exclusive interpretations in a file using the shed filter:

Here is an example of showing the original text along with the rendered version using the extract and shed filters:

extract -s 1,2,2 (no spaces in the spine list unless you enclose in quotes) will duplicate the second spine, shed -s $ applies the shed filter only to the last (new) spine, and shed -e "s/^harm$/cdata-harm/X changes the exclusive interpretation “harm” to “cdata-harm”.

Staff placement of **cdata

Data can be placed above the staff by using the *above tandem interpretation, and *below to return display of the data spine below the staff.

When there are multiple data spines to display above or below the staff, tandem spines from left to right will be placed near to far with respect to the staff:

**adata and **bdata

The **adata and **bdata data types are similar to **cdata, but will display spines above/below the staff respectively by default.

In addition, the tag after **adata- or **bdata- will displayed as a label before the first data token in the spine:

Here is an example of placing data text above the staff using the shed filter (data labels):

Without initial data labels:

Coloring data

Each data spine’s text can be given a different color:


Another text-rendering exclusive interpretation is **vdata, which converts data into verse-like text rather than chord-like text.

Here is an example of given a label to the spine data in the score *v: followed by a label will be displayed at the start of the music, and *vv: labels will repeat at the start of each system. This feature is not available for **adata, **bdata or **cdata.