Part export automatic numeration of same instruments

• Apr 5, 2014 - 17:06
Reported version
3.0
Type
Graphical (UI)
Severity
S5 - Suggestion
Status
closed
Project
MuseScore
Tags
easy

Currently, when pressing the "new all" button in the part export window, if there are more than one instruments of the same kind in the score, they are enumerated.
However, in a musically incorrect way:
Trumpet
Trumpet-1
Trumpet-2

e.g: nameOfPart = "InstrumentName"+"-"+"(numberOfSameInstruments - 1)"

when it should be:
Trumpet 1
Trumpet 2
Trumpet 3
Trumpet 4.

e.g: partName = "InstrumentName"+"\s"+"numberOfSameInstruments"

Comments

• Apr 5, 2014 - 17:55

You are right, when you have more then one same instrument,

I might be perfectionist but if you have one piccolo and 3 flute, only flute should be numerated
(so i think that 's why there was -1 (0 isn't visible)

Reply

• Apr 5, 2014 - 18:19

You are absolutely right. Any auto-numbering mechanism should kick in only if there actually are duplicates.

In practice, I have concerns - some people want to see "Flute 1" and "Flute 2", others "Flute I" and "Flute II", others "!st Flute" and "2nd Flute". Probably other variations in other languages. Trying to make this cover all cases, with radio buttons to select numbering style, etc - could be a drag. Still, I'd be happy with "Flute 1" and "Flute 2" by default and making people with other preferences edit the names. Wouldn't be any worse than it is now.

Reply

• Nov 30, 2014 - 08:46

We could use a method similar to the special symbols in headers/footers, by using some variables in the partnames (like the $n mentioned above) and have different variables for Arabic numbers, Roman numerals, letters.
And different variables whether we want a 1 even if there is no 2nd instrument, like:

  • $n for Arabic numbers (1, 2, 3, 4...), if more that one
  • $N for Arabic numbers even if only one
  • $r for Roman numerals (I, II, III, IV...), if more that one
  • $R for Roman numerals even if only one
  • $a for lower case letters (a,b,c), if more that one
  • $A for lower case letters even if only one
  • etc...

On the other hand this could get fix via the use of templates, or by tweaking staff properties before part extraction

Reply