Playback Tempo

• Jun 2, 2019 - 04:17

The tempo in the playback is 10% faster than the one marked. This is happening across all my scores. I haven't adjusted any of the play panel settings. However, when I export a mp3 file, it plays at the correct tempo. Is there any thing I could have done accidentally?


In reply to by Marc Sabatella

Well, I can confirm that the play panel does say 100%, 126 bpm, but I don't think its the play panel because it's happening to all my scores. But I updated to 3.1 only yesterday, so it might have something to do with that.

I just tried restarting my MuseScore (going through all the keyboard and language preferences, etc. again), and it's working normally now. (I probably should of tried that before pestering you guys).

I still don't understand how the problem happened, but anyway, thanks for your help

In reply to by Timothy Beer

Are you in the US with a non US sold computer? If so, I suspect you would be using a transformer to change from ~220 to ~115 volts. What doesn't change in these is the cycle rate. Europe uses 50 Hz while the US uses 60 Hz. This is the only way I can think of that all scores would play too fast and the exact amount would be 12%.

This started is happening to me too. The Beat Detector app is telling me that crochet=100bpm in Musescore is playing back at 109bpm.

I'm also in Australia on a recent MacBook Pro...

I'm having this problem too. I'm on a Mac in the US. It happens across all my scores, and it started after I hooked my AirPods up and restarted the audio settings to send the audio to my AirPods. It worked, but the score I am working on began playing at 220 bpm, even though I had it marked at 200 and the program said 200 everywhere in it. It's not a score problem, definitely a program bug, I'm just not sure how to fix it. This happened to me once before, and it didn't fix itself until the next update for Musescore came out. This time around, I'm using Musescore for a class assignment and I don't have the time to wait around for another Musescore update.

In reply to by Ethan Scartelli

It is certainly conceivable that there is a bug somewhere, but if so it would seem to be one that seems to only affect a few systems and/or your score, since. Or it could be a setting you've overlooked, or perhaps a bug in macOS that causes the clock rate to be handled incorrectly. We'd need you to attach your score, or a relevant excerpt of it, in order to begin investigating what is going on. First, though, I recommend trying to reboot and see if that clears it up - I kind of do suspect a macOS glitch based on what I'm seeing here.

Do you still have an unanswered question? Please log in first to post your question.