Tempo pallet unresponsive
Reported version
3.0
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Use pallet to set tempo.
drag and drop works OK
But when attempting to edit the tempo by clicking on the tempo and typing in a new tempo it reverts to 100 bpm. In some instances where tempo is changed in the chart playback will behave erratically. Occasionally stopping playback entirely.
Comments
In order to investigate, we would need you to attach the score with the problem and give us precise steps to reproduce the problem.
This one will play correctly after the tempo is inserted, but upon any pause in play or repeat it reverts to a slow tempo of about 60 BPM. Today it raced through the repeat at perhaps 1000 BPM. Now it is playing slow again.
it plays at 120 BPM for me, despite the 2 Presto tempo texts asking for 187 BPM
And then, all of a sudden it speeds up
Definitely not stable, Possibly a clock speed reference error in the programming. It stubbornly plays at its own tempo. I also could not manually set tempo to a BPM. Mostly the program just ignored my input.
Looking at the MSCX file within the MSCZ archive, I see another tempo marking with a blank line for a text, placed at the start repeat, set to what seems to be a crazy value that is probably confusing things. I deleted all the tempo markings from within MuseScore by clicking the first, Ctrl+C to copy, then right-clicking, Select / All Similar Elements, then Delete, then pasted the original back. It works fine at that point. Somehow the crazy "invisible" tempo marking seems to have been causing problems, I think.
In reply to Looking at the MSCX file… by Marc Sabatella
I'm curious if the OP entered a tempo and deleted it by putting the tempo into edit mode and deleting all of the text. IMHO this should delete all reference to the tempo mark, not make it invisible and very difficult to deal with.
It normally does. But not, apparently, if you leave a carriage return or spaces or something else that is "there" but not visible.
I discovered that if I delete all Parts, then select New All, the problem goes away. This indicates a problem with refreshing parts when changes are made to the main score.