The automated numbering of consecutive measures of rest may be controlled via the multi.number attribute on the scoreDef or staffDef elements.
which is implemented in verovio:
Click for MEI data
```xml
Verovio
Transcoded from Humdrum
```
The question is: How to control the numbering behavior on a case-by-case example? For example, if there are only a few repeated measures, then it is not necessary to number them. In such cases, does a <staffDef> turning off @multi.number need to be added, and then turned back on after the mRept section of music? That seems quite contrived. It would perhaps be better to have a way of controlling the minimum number of repeated symbols before numbers are added above the mRpt. And/or allowing @multi.number to be attached to <mRpt> to allow changing the numbering behavior contrary to the global setting in <staffDef>.
One possibility would be to utilize mRpt@n which could be used to set the number explicitly:
@n (optional) Provides a number-like designation that indicates an element's position in a sequence of similar elements. May not contain space characters. Value conforms to data.WORD.
But adding @n to the mRpt does not change the number currently, and it cannot be used to turn off the numbers in any case (although setting to 0 could be assigned the meaning of suppressing the number).
This also impinges on how to deal with automatic numbers in musical excerpts. Currently the number above the repeat sign always starts with 2:
Click for MEI data
```xml
Verovio
Transcoded from Humdrum
```
But what if the repeat number should not start at 2?
Indirectly related: is there a way of adding repetition numbering above repeated measures? In other words, orchestral parts often have repetition numbers above notated music that is equivalent to an expanded mRpt. Each measures in the following example would have a number above it (probably staring with "2" above the second measure):
Click for MEI data
```xml
Verovio
Transcoded from Humdrum
```
Here is an example from a Finale plugin documentation page:
lpugin
commented
2 years ago
How are numbers above
<mRpt>controlled in refined cases? Numbers are currently added above the mRpt automatically by default:Click for MEI data
```xmlTranscoded from Humdrum
In the documentation for mRpt: https://music-encoding.org/guidelines/v4/elements/mrpt.html
In the remarks section:
which is implemented in verovio:
Click for MEI data
```xmlTranscoded from Humdrum
The question is: How to control the numbering behavior on a case-by-case example? For example, if there are only a few repeated measures, then it is not necessary to number them. In such cases, does a
<staffDef>turning off@multi.numberneed to be added, and then turned back on after the mRept section of music? That seems quite contrived. It would perhaps be better to have a way of controlling the minimum number of repeated symbols before numbers are added above the mRpt. And/or allowing@multi.numberto be attached to<mRpt>to allow changing the numbering behavior contrary to the global setting in<staffDef>.One possibility would be to utilize
mRpt@nwhich could be used to set the number explicitly:But adding
@nto the mRpt does not change the number currently, and it cannot be used to turn off the numbers in any case (although setting to0could be assigned the meaning of suppressing the number).This also impinges on how to deal with automatic numbers in musical excerpts. Currently the number above the repeat sign always starts with 2:
Click for MEI data
```xmlTranscoded from Humdrum
But what if the repeat number should not start at 2?
Indirectly related: is there a way of adding repetition numbering above repeated measures? In other words, orchestral parts often have repetition numbers above notated music that is equivalent to an expanded mRpt. Each measures in the following example would have a number above it (probably staring with "2" above the second measure):
Click for MEI data
```xmlTranscoded from Humdrum
Here is an example from a Finale plugin documentation page:
https://usermanuals.finalemusic.com/Finale2014Mac/Content/Finale/Number_Repeated_Measures_Plug_in.htm
Related to (same as) issue https://github.com/humdrum-tools/verovio-humdrum-viewer/issues/464
Also related somewhat to issue https://github.com/music-encoding/music-encoding/issues/741, but that is a separate problem.