Parts with multi-measure rests at beginning of piece do not "print" tempo markings.
In parts that are extracted from a score and start with a multi-measure rest, the tempo markings do not appear. Do I need to split the multi-measure rest into a single measure followed by a multi-measure rest to have the tempo appear?
Comments
Which version of MuseScore, what OS, and can you share the score?
It should indeed work right out of the box in any version of MuseScore. Be sure you have added actual tempo markings and not used staff text. If you continue to have trouble, do attach your score so we can see what might be happening.
In reply to It should indeed work right by Marc Sabatella
I used Add-Tempo Marking from the top menu to put the tempo in. It only appears in the parts that have notes in the first measure.
In reply to I used Add-Tempo Marking from by aedsb
So I repeat: Which version of MuseScore, what OS, and can you share the score?
From another post I see it is 2.0.3.1 on Mac. So we now only need to see the score to tell what is going wrong and why
In reply to So I repeat: Which version of by Jojo-Schmitz
Here's a short score showing the issue.
In reply to Here's a short score showing by aedsb
Your Tempo sign is grey so it's "invisible" go to the Inspector and clic the case "visible"
In reply to Your Tempo sign is grey so by Raymond Wicquart
Note that there are two pieces of information. One is the metronome marking (which is greyed out) and the tempo marking of Allegro which is only found in the parts that have notes in them.
In reply to Note that there are two by aedsb
It's unnecessary to have 2 tempo marks. Just use the Allegro and in the inspector uncheck follow text and set the tempo to 132. If you don't do this, what tempo do you expect MuseScore to use? They're both on the same spot and MS doesn't care that one is invisible.
In reply to Here's a short score showing by aedsb
It is the presence of two separate tempo texts in the same place that is causing the problem - see #38941: Staff texts after the first are ignored in multimeasure rests. I consider this a bug, but in any case, the workaround is simple - don't use two separate texts here. There is no need - the Allegro itself can be set to have the desired playback effect, so you don't need the other one.