Tempo change bug
I'm trying to put in a tempo change to 120 BPM, but for some reason it goes to 80 BPM when I play it back. The "follow text" checkbox in the Inspector is checked as 120 BPM, and I've tried deleting it and re-adding it, but the same thing happens every time.
Is this a bug? If it is, please fix as soon as possible as this is extremely important.
Thanks
Comments
For some reason it fixed itself when I added a double bar line... Why is that?
As usual, it's easier to help if you attach the score and give steps to reproduce the problem. Otherwise we can only guess.
But if I had to guess, I'd assume either
1) your score is in compound meter and hence you are disagreeing with MsueScore over whethert the tempo is being specified in quarter notes or dotted quarters
or
2) your score already has parts generated and you are running into #78416: Tempo text oddities in score with linked parts until save/reopen. In which case save/reload is known to work around the issue. Or, in the future, don't generate parts until you are closer to completion, which is also a good idea for performance reasons.
I've come across several funny happenings with tempo changes, also double bar lines. Here is one related to the Fermata and tempo change.
Load the attached score, notice that the Fermata is set to a time stretch of 2.00 in the Inspector.
Now play and see that it plays correctly.
Now simply delete the tempo (quarter=120) at measure #3
Now it should play at the tempo (quarter=80) marked at the first measure
But note that after measure #3 it still plays at the previous tempo of (quarter=120)
Deleting the Fermata fixes.
Or changing the Fermata time stretch fixes.
Save and close and reload fixes.
In reply to I've come across several… by MuseTone
Confirmed. Glitches like this have been reported and fixed before, but this particular one seems new. There was #100791: Wrong tempo after fermata if tempo change added in front which seems quite similar, but I guess the fix only handled the case of tempos being added, not deleted. Probably we need similar code elsewhere. Could you file a a formal bug report to the issue tracker (eg, using Help / Report a Bug, from within MuseScore)?