No sound in MuseScore 3.3 RC1-3 after waking up from hibernation (Windows 10, 1903)
It occurs again and again that after waking the system from hibernation or suspend mode, no sound is played back. It affects MuseScore 3.3 RC1-3, but no other applications. So Windows doesn't seem to be to blame. Not only is the sound missing, it is as if something is hanging after pressing the Play button, there is also no playback line (or as you call it), i.e. there is no playback of the notes at all, not even noiselessly.
Has there been a major change in the audio engine since 3.2.3 (or earlier, in 3.2.3 the problem probably already existed, I will verify that again)? Or was there a newer version of Qt?
The workaround is Restart Audio and MIDI Devices. But this is no fun. Also, after pressing the Reset button and the OK button, the following happens:
I thought the menu bars might reset if I changed the window size, but as a result MuseScore crashed completely yesterday.
P.S.: MuseScore was of course still open at the time of the hibernation/suspend and was also put to sleep.
| Attachment | Size |
|---|---|
| Anmerkung 2019-10-28 134956.png | 15.49 KB |
Comments
https://musescore.org/en/handbook/3/revert-factory-settings ?
No changes to the audio system I am aware of, and while we updated the version of Qt we use on Windows, it's not really involved. Whatever is going on seems unique to your particular system - I haven't heard other reports of this. Could be something like, after waking up from hibernation, one of your audio drivers is resetting in a way that is similar to what happens when you connect a new device, and this triggers MuseScore to need you to restart its own audio via Edit / Preferences / I/O. Other programs that don't need to be reset on on change of device would naturally also not need to be reset after hibernation, if this thery is correct.
In reply to No changes to the audio… by Marc Sabatella
Maybe it really is a unique system-related experience. What made me suspicious was the fact that at some point before version 3.2.3 there were no such problems. That's why I assumed that something had been changed in the audio engine or something like that. Of course, a Windows update could also be responsible for this.
What I have tried so far:
(1) I uninstalled all installations of MS 3.x and now only use the 3.3 RC3. Besides, version 1.3+2.3.2 are still installed (I think that doesn't cause any problems, it never did in the past).
(2) My speaker is a sound bar fixed to the monitor and connected via USB. It was connected to the monitor USB hub all the time, now it is connected directly to the PC. The USB devices should be directly available as soon as Windows wakes up from its Sleeping Beauty nap. With the other configuration, it might have made a difference which device (monitor or PC) was turned on first.
So far it seems to be working, I'll keep watching.
In reply to No changes to the audio… by Marc Sabatella
"...and this triggers MuseScore to need you to restart its own audio via Edit..."
Well, this is the annoying thing! I connect new devices all the time. It might be a projector, an USB audio port, an AUX cable to the headphone port. Sometimes even just connecting my headphones requires me to restart the audio to remove the audio output from the speakers to my headphones. I remember the old days, when you had the sound in your laptop speaker. Then you connected your headphone and just by that the speakers muted and sound was in the headphones.
Other software seem to have similar requirements. You have to rescan audio devices before you can use newly connected devices. There should be a shortcut for that!
In reply to "...and this triggers… by jotti
@jotti, try toggling (off and back on) the MIDI button in the toolbar.
In reply to @jotti ry using the MIDI… by Shoichi
That sounds like a good workaround, because the button is right there. Compared to digging up that "Restart the audio devices", which is not even in the list of functions that could be assigned hot keys.
I call it a workaround, because I believe there is a proper way to deal with audio devices, which won't make Windows, nor Musescore confused, the way Microsoft coders have thought programs ought to work. And the way users are supposed to do the connecting and disconnecting of devices. I haven't found out the proper way. What I do is I just plug in devices and disconnect them on the fly, thinking the system and the program recognise what's happening. They don't always.
In reply to That sounds like a good… by jotti
There are all kinds of things I have to "dig up". Though I would never claim to be an expert. There are things I can do while the program is running, and there are things that I probably shouldn't do. this is true of any program.
I also have this problem in OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.3.0.8737, revision: 4761df6, but Edit -> Preferences -> Sound -> Restart Audio and MIDI Devices helped.