MuseScore 4 Sounds very fast and an octave higher than it should

• Dec 11, 2022 - 03:16 In this video you can see that it is definetely way faster than 120, which is what it should be. The flute is also way too high pitched. Every instrument is like this with and without muse sound on. I have restarted muse score, restarted my computer, uninstalled muse score, reset MuseScore to factory settings, basically anything you can think of and it still doesn’t work. I was very excited to try out muse sounds but now I am feeling a little defeated that I can’t get it to work right.


This is a known incompatibility with certain audio drivers. The cause is apparently already identified and it should be fixed before release. Meanwhile, changing output devices will probably work around the problem.

I had the same problem in MuseScore 4.1. Intersting fact: playback speed was EXACTLY 4 times expected speed (setting tempo to 30bpm results in playback at 120bpm.)

Confirmed: something to do with the audio driver. I use ASIO Link Pro, for its routing options. Switching back to FocusRite worked.

Trying to switch back to ASIO Link Pro wouldn't work - MuseScore 4 had control of "audiodg.exe". Ending that task broke MuseScore 4, and now I'm back to the 4.0 problem: it just won't open (audio driver related).

In reply to by Marc Sabatella

Makes some sense. My driver is set to 44.1, but I wonder if it starts higher under the hood and resamples down to 44.1 at a later stage.

Anyway, hopefully all this audio driver problems get fixed. It's keeping me on MuseScore 3 (better workaround for me than changing drivers/sample rates).

I wonder what about MuseScore 4 is so unique. I work with so many other audio programs (Reaper, Resolve, Zoom), and none of them have driver issues. It's like MuseScore4 needs system access at a higher level than even those programs.

I've been a MuseScore user for quite some years now, if I recall correctly, since version 1.3. Used it in Windows and Linux. Accepting the limitations, back then compared to Sibelius and Finale, was a no-brainer for me, as I tend to use open source software as much as I can. Also, I've always had an easy time solving my issues, specially with Marc's help - and others - in the forum.

I don't want to complain, I really don't. When I watched Martin's video stating that he was taking over the UI and basically managing the project, I got really stoked. And the first demos of MS4 were mindblowing. But it's been a rollercoaster to trying to get it working.

My audio PC is fine tuned to work with all kinds of music and video software (Reaper, NI stuff, Premiere, Resolve, etc), other "obscure" software like trackers (Renoise, Schism and OpenMPT) and even streaming with OBS. And I never had severe issues like these: 4.0 wouldn't start - had to download those beta "portable" versions - and now with 4.1 the playback is pitched and sped up.

Not to mention MuseHub, an unresizable app that disappears when you click away, hides in the tray with no way to control that behaviour whatsoever...

Again, I don't want to complain. After all, it's free and lots of good people are working on these issues. But no, I won't change the sample rate of my audio interface. It just doesn't make sense. It's like having a car and whenever I go to a specific motorway - let's call it the M4 :) - I need to change the tires.

I will continue working with 3.6 until all these issues are solved, and if you guys need help with testing, I can make videos and screenshots.


In reply to by Marc Sabatella

Yay, glad it's being worked on!

Default workflow for video (and some musicians), is 48 kHz. And some musicians, with good reason, prefer to work at 96 kHz.

My sample rate stays 44.1 kHz. It's just that my preferred driver, even at 44.1, triggers this MuseScore glitch. For me, the inconvenience of changing drivers is what's barely keeping me on MuseScore 3.

In reply to by Marc Sabatella

There are a few reasons why I'm working with 48kHz, main one being that is generally what video folks use and I don't want to spend time converting audio material or resampling stuff in the DAW. Also, my other machine's audio interface runs natively at 48kHz, so it just makes sense to work that way - always have, for the past 7 or 8 years.

btw, enjoyed your last Café video, I'll try to be there for the next one. Keep up the good work!

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