Musescore 4 Playback Speed too Fast
I recently installed Musescore 4 beta to mess around with Musesounds. When I did, I instantly noticed that my playback is way faster than what it should normally be. All of the pitches are way too high (presumably because of the time change) and playback essentially does not work.
I tried to look for any settings that could change playback speed like in Musescore 3 but couldn't find anything/don't really know what is causing the issue.
When I export as an mp3, the score sounds normal so I'm sure it's a playback issue.
Anyone have any insight?
Comments
First off, update to the RC if you didn't already.
And then, if you still have this issue, check for similar reports on Github (there are some). If none of them matches your setup enough, then open a new issue for it.
In reply to First off, update to the RC… by jeetee
Will do, thank you!
This is apparently known issue affecting a small number of audio drivers (eg, ones from Logitech), and apparently a fix has been developed. Not clear exactly when/how the fix will be made available. Meanwhile, switching to a different audio device will probably work around the issue.
In reply to This is apparently known… by Marc Sabatella
Ah ok. I am using Realtek audio drivers but I'll see if that issue is somewhat related! Thank you.
In reply to Ah ok. I am using Realtek… by Jeremiah Bang
I am having the same issue with RealTek and I have changed my output device and also disabled RealTek but it still does this. Have you found a fix yet?
In reply to This is apparently known… by Marc Sabatella
It's not just Logitech drivers. The ECHO Audio drivers I'm using for my Audiofire 8a also have the problem. And ECHO stopped supporting it years ago. I seem to recall Windows 8 was the last they officially supported. Yet the drivers do work under Windows 10, including with MuseScore 3.x . But no fix for them is going to be forthcoming to accomodate changes in Musescore 4.x that caused this problem to surface.
This is STILL happening. Playback speed is twice what it should be.
In reply to This is STILL happening… by MarkTheMartian
Set your audio device's sample rate down to 48 or 44.1 kHz. Apparently some drivers don't work well with MuseScore when set to 96 or higher.
This is still happening. I'm running my interface at 48000hz. My work flow forces me to have my DAW open while writing on MS4. The ONLY for MS4 to not speed up is to close my DAW and change my interface to run at 44100hz.
Which is preventing me to do my work properly. (Transcribe my own projects into notation in MS4). I personally want to work in 48000 because my client is in the TV industries. Changnig my DAW to 44100 is a workaround but it SHOULDN'T have to come to this.
This was working a week ago.
In reply to This is still happening. I'm… by Freddie Lo
So what changed between last week and now? No new MuseScore has been released yet, so it must be something else..
On the other hand, you might want to test a nightly build since they now include a possible fix for higher sample rates according to https://github.com/musescore/MuseScore/issues/15615
First, not a new user, just starting fresh on the site. Second, I have been having similar issues, but in this case it tends to go back and forth between super-fast on one occasion, and super-slow on another. Presently using MuseScore 4 on Windows 11 with RealTek sound drivers
I have the same problem...
ESI U168XT Interface. Have tried different Samplerates. Nothing changes the playback speed.
Ableton works fine on my system.
Ill have to use another software.
In reply to I have the same problem… by Zorg Inc
I just started having this issue recently myself, and there was no obvious trigger for it. I tried completely re-installing musescore, hub and its components, full reset of musescore preference, and everything else.
I have a Corsair Void Elite headset. My sample rate was at 48khz which should have been one of the OK ones, but my headphones are seen as an 8 speaker headphones due to the way it tries to simulate directional sound. Once I set the headphones to be seen as two speakers the issue resolved itself. I'd like to still be able to use the virtual surround of the headphones, but I'm not sure whether the bug is on Musescore's side, or the headphone company
In reply to I just started having this… by chris2746
I think that's the cause of the problem.
I have 4 speakers (2 front, 2 back) and when I configure my Windows audio appropriately (4-way) Musescore plays back horrible sped-up toybox sound.
If I configure Windows audio as just Stereo (2 speakers) then Musescore sounds normal.
(BTW I'm on latest stable Musescore release, Realtek audio drivers, 48kHz sampling rate).
In reply to I think that's the cause of… by jods
Thank You jods!
Your post solved my identical problem when I had almost given up.
I DO think that the Dev-team should adress this as it is a showstopper for more than one user!
Again: I'm really glad for your post jods
(Win 11, MSc 4.2.1, Realtek 24-bit 48k 5.1 (had to change to two-speaker set up))
I am seeing this also on an ECHO Audiofire 8a Firewire card.
If I disable surround sound, it presents itself as 4 pairs of channels, instead of one 8-channel interface.
I actually have a 4.1 setup in my home office and want to keep using the surround sound.
So, this bug alone has me revert back on Musescore 3.x .
In reply to I am seeing this also on an… by [DELETED] 35237410
Have you tried setting an explicit sample rate of 44.1 kHz? Higher samples rates are known to cause issues on some systems.
In reply to Have you tried setting an… by Marc Sabatella
Or rather due to this known issue? https://github.com/musescore/MuseScore/issues/17648 or
https://github.com/musescore/MuseScore/issues/22764
In reply to Or rather this known issue?… by cadiz1
Frankly, I just want a NULL output, and use my MIDI instruments connected to my mixer, and/or separate software synth. I have as much need for the built-in sounds as I do the Microsoft GS wavetable synth.
Anyway, I re-upgraded to 4.3.0 just to check it out .
1) 8 channel / 44.1 kHz is no different than 8 channel / 48 kHz . Both way too fast
2)if I switch the interface to 4 x 2 channels, it plays at the right tempo
3) if I change the audio output to my central Displayport LG monitor (it has speakers), then everything plays at the right tempo. But of course, sounds awful. More mono than stereo.
So, it's the second issue above.
Time to uninstall again and go back to 3.5.2 . That was incidentally the last release I had previously used for my scores, according to the version in the file. MIDI got broken in the very next release ...
In reply to Frankly, I just want a NULL… by [DELETED] 35237410
Your MIDI devices may produce better sound than a soundfont, but it's highly unlikely they produce better results than Muse Sounds. So it could be worth giving that a shot - both for the better playback you get with Muse Sounds but also the far better engraving you get with MU4 in general.
Also, no need to uninstall anything - Musescore 3 & 4 happily coexist on your system. So you can use MuseScore 4 & Muse Sounds and 4x2 audio when you need amazing playback and engraving, and MuseScore 3 when you need to be able to use your MIDI output devices and don't mind sacrificing playback or engraving quality.
In reply to Your MIDI devices may… by Marc Sabatella
March,
I still need MIDI support to work. I like my Roland Fantom XR. VirtualMIDISynth allows many sounds to be loaded. There are several very interesting harpsichord sound fonts over a virtual MIDI link. Munt also emulates a Roland MT-32 over a virtual MIDI link. I also have a physical MIDI keyboard to input notes - a double manual Roland VK-88 organ (along with a MIDI pedal board - wish I knew how to play that!), which I used in the past with MuseScore 3.x, since editing their length is much quicker than entering all the notes one by one with the mouse.
Unfortunately, MIDI in MuseScore is also broken on my system for any version after 3.52 . So, I really have no use for 4.0 .
I would also llike the ability to disable the audio output in Musescore, actually. I shouldn't have to go into the mixer to set the volume to zero every time I want playback. Or is there another option I missed to do that once and for all, and not each time I open Musscore ?
In reply to March, I still need MIDI… by [DELETED] 35237410
Once you’ve set the volume to zero for any given score, it should be saved with the score. So you should only need to do it once per score.
You could also remove the default soundfont from View / Synthesizer in MuseScore 3. At least I think that’s possible, unless that is disabled (not at my computer to test). Or you could hack the system a little if you have admin privileges on the system, by actually removing the soundfont from the installation. or install a dummy soundfont instead.
Mouse input is indeed the slowest possible way to enter notes. Fastest is usually typing the computer keyboard, but indeed, in some case MIDI input can be about as fast.
In reply to Once you’ve set the volume… by Marc Sabatella
Doesn't Musescore have a handwriting feature that would let users write on their device screen with a pen? Still slower than keyboarding but faster than mousy.
In reply to Doesn't Musescore have a… by FBXOPWKDOIR2
My handwriting is awfull, so that could never work. Selecting notes with a pen could certainly work, if one has a touch screen. None of the 3 monitors on my PC are.
In the 1980s, light pens were popular, and used for this very purpose on music workstations. There were some at my school in France - Thomas MO5/MO6 mostly. Unfortunately, light pens require a CRT monitor, so they aren't an option for me either. We do still one Sony CRT in one room, but it's mostly tehre to fill the cabinet space which is 4:3 aspect ratio. A 16;9 TV/monitor would look out of place.
But I personally find touch screens unreliable compared to physical keyboards. Certainly, if you know how to play, MIDI is the fastest option. I don't think there is any question that Musescore should drop MIDI support. This is only about making it work.
In reply to Doesn't Musescore have a… by FBXOPWKDOIR2
No, you’re thinking of StaffPad, which is part of the same company as MuseScore. I haven’t used it but have played with a couple of other programs that attempt to recognize music from handwriting. They were unbelievably frustrating. Typing is 100% accurate - type an A, get an A, every time with no doubt. But people do report StaffPad is not as bad as other programs at it. It’s not about how good your handwriting is, I know that much.
In reply to No, you’re thinking of… by Marc Sabatella
Thanks. I'm pretty sure I am much slower at handwriting than playing notes on a keyboard, even with 100% handwriting recognition. Wish I could achieve 100% keyboard accuracy too, but usually it's not too bad, and mostly fixing the note durations.
Anyway, I reinstalled Musescore 4 since it can coexist with 3 . I found a test case for a crashing bug, reproducible. Is there any kind of log or crash dump I can send ? Or do I need a debug build of MuseScore for that ?
In reply to Thanks. I'm pretty sure I am… by [DELETED] 35237410
"I found a test case for a crashing bug, reproducible. Is there any kind of log or crash dump I can send ? Or do I need a debug build of MuseScore for that ?"
First thing to do: attach a score (or test score) here, providing the steps leading up to the crash. If confirmed by others, and if it's not a duplicate, a bug report should be sent to Github: https://github.com/musescore/MuseScore/issues
In reply to Once you’ve set the volume… by Marc Sabatella
Well, setting the volume to zero doesn't persist. As I'm still facing a number of issues with 4.3.1, I must stick to 3.5.2 for getting stuff done, including just playback.
If I save in 4.3.1, the file will no longer be readable by 3.5.2, presumably, so I don't want to do that. Thus, I have to reset the mixer level every time I suppose I could maintain multiple copies, but that's a PITA if I start making changes in the wrong one.
While saving the mixer state in the score is certainly a good option, it doesn't have to come at the cost of a "no sound" option. If one only wants to use MIDI, why should this change have to be done over again for every score, when it can just be done once globally ? Also, there are probably people out there who prefer to notate without playing back. Maybe even deaf people. Beethoven kept composing, after all. So, the "no sound" option would be a good one to have, not just for MIDI users. Also, it would avoid this type of strange bug with the speed picking up due to an issue with the audio stream. Just clicking "no sound" once for the device is far easier and gets it done.
View / Synthesizer does work in MuseScore 3. Is there no MuseScore 4 equivalent ?
Even as an engineer, I think messing with soundfonts and possibly admin privileges is a much too complicated way to mute the sound. I don't see a valid reason to require that. If somebody wants to switch back to sound fonts, they will have to add them all back. Whereas switching the audio output is just one simple, easy step.
I realize it's not zero-cost to implement. ChatGPT tells me there already exists virtual audio drivers that can be used for this purpose, if the problem is not having too many forks in the playback code.
Not sure if any of them are open-source or if their license permits integration in MuseScore, though.
In reply to Well, setting the volume to… by [DELETED] 35237410
Feel free to open a GitHub issue requesting a program preference for disabling audio. I think the “View / Playback setup” dialog would be the logical place for it - a “MIDI output only” profile that could be selected. That’s also the closest equivalent to View / Synthesizer. MuseScore 3 had this limitation where whatever soundfonts you had loaded would always affect all scores. MuseScore 4 allows soundfonts to be specified per score, so it’s done in the mixer.
In reply to Have you tried setting an… by Marc Sabatella
Fellow (ex?) Pentaxian, my soundcard was set to 48 kHz. I didn't try to downgrade it to 44.1 kHz.
But changing it from 8-channels to 4 x 2 channels fixed the tempo bug.
Alas, not the MIDI problem (not working at all after for me 3.6.0 apparently).