Closed bel28kent closed 1 year ago
@craigsapp Do I have your permission to add "!!!system-decoration: {(*)}" to the files you encoded? Also, how do you recommend encoding **dynam spines for piano music with three or four staves?
You can add a system decoration record to the files (you are allowed to do anything you want to the files, even if I disagree :-). When there are two staves, the default is !!!system-decotration: {(*)}
(so it is not necessary):
https://verovio.humdrum.org?t=KiprZXJuCSoqa2VybgoxQwkxY2MKPQk9CjFFCTFlCj0JPQoqLQkqLQo=
For three or more staves, the default system decoration is:
!!!system-decoration: [*]
(so bracket on the left across all staves, and barlines not connected between staves.
For **dynam
spines in three or for staves, you would place a **dynam
spine immediately to the right of the **kern
spine to which they are attached:
The above example is for single staff instruments but not for the grand staff. For grand staff, place the **dynam
spine to the immediate right of the top staff of the grand staff. For double grand staff, there will be two **dynam
spines: one to the right of each top staff:
The interpretations such as *staff1/2
and *staff3/4
means to center (by default) the dynamics between the two staves of the grand staff. (You can instead add *center
to the **dynam
spine rather than using the *staff1/2
system, but you need the staff labels for the system decoration record anyway.
There are complicated cases where a dynamic needs to be attached to the bottom staff (either above or below it). In this case you can use a layout command such as !LO:DY:a=2
or !LO:DY:b=2
to display the following dynamic above or below the bottom staff of the grand staff:
*center
, *above
and *below
can also be used to change the default position of the dynamics (until the next default placement is made), but *center=2
, *above=2
and *below=2
are not (yet) implemented.
There can be more complicated cases where two dynamics marks are needed at the same time on the same staff, which involves spine splits:
This issue is for the branch to add phase2 edits to corpus.