Musescore won't playback a score if audio device changes in the background, even if the program is active.
Basically, the app will refuse to play when the play button is pressed, if my headphones are unplugged, plugged in, or unplugged then plugged in, while the program is open, even in the background. What I mean by "refuse to play" is, all of the buttons turn gray like they would if the score was playing, but it just sits like that and doesn't play the score, and I have to restart
Comments
Did you try selecitng the new device in Edit / Preferences / I/O, and/or pressing the Restart Audio and MIDI Devices button in that dialog, or just toggling the MIDI button on the toolbar? This normally works on those systems that don't report the device change to MuseScore.
In reply to Did you try selecitng the… by Marc Sabatella
Yeah, but macOS does report it to every other application without a problem. This workaround does not cure the bug.
In reply to Yeah, but macOS does report… by [DELETED] 1831606
Ture, but it could be a question of how it reports it and if that's the place MuseScore expects it. I know nothing of macOS, but I know it works fine on my system, I can change devices all day long and MsueScore keeps up just fine. Hopefully either macOS can be persuaded to put the information where MuseScore looks, or more likely, someday MuseScore can learn where macOS puts the info and look there instead of the place it current does.
In reply to Ture, but it could be a… by Marc Sabatella
Firefox, Chrome, and every other audio-using app I know -- works correctly. If, in Russia, you don't understand Russian, don't try to persuade the Russians to speak English. If MuseScore doesn't register for the right kind of notification, that's not macOS' fault. I suspect QT is deficient and MS is stuck with it or this would have been fixed a year ago.
In reply to Firefox, Chrome, and every… by [DELETED] 1831606
s I said, I know nothing about MuseScore, I'm just explaining how the current situation likely came to be. if macOS has documented an alternate place to look for this info, it would be great if some programmer with macOS expertise could implement a check for that in MuseScore. Meanwhile, I'm just trying to help users on systems - like, apparently, macOS - where for whatever reason it doesn't work. I have no ability to fix it, only to explain how to workaround it, and to point out that it really does seem to affect only certain systems.
In reply to s I said, I know nothing… by Marc Sabatella
It affects macOS Catalina or newer (Big Sur) every time, without fail. It's not "intermittent". I click on the MIDI plug twice (I discovered that!) like I used to swat old vacuum-tube radios producing "too much static", just something you "have to do", but it looks unprofessional.
In reply to It affects macOS Catalina or… by [DELETED] 1831606
To be clear, I never used the word "intermittent". I just said it affect some systems but both others, which is true. Mostly, though, I just wanted to help the user who couldn't figure out how to get it work. I am not trying to make excuses for why MsueScore can't find the information on macOS, nor am I suggesting some clever macOS expert shouldn't try to fix this if possible. I am just trying to help users get the job done meanwhile.
In reply to Did you try selecitng the… by Marc Sabatella
Actually, my computer is pretty old, so it might not report the new device right away. Thanks
In reply to Actually, my computer is… by Soggy Crouton
This might be more device specific. My trusty old laptop just works no matter how many times I unplug and plug in the headphones. My new Surface running the same version of Windows is more fiddly. I hope that newer Mac OS's are better than the last time I work for a school that went Mac. We constantly had to tell the OS what output device was wanted when a different thing was plugged in.
In reply to This might be more device… by bobjp
macOS has no trouble, or any other macOS app. The problem is MuseScore. I don't have enough macOS audio knowledge to attempt to fix it myself. Very likely QT's audio capabilities are involved. The total time spent double-clicking the midi icon for the rest of my life would not be 1/100000 of the time spent figuring out how to fix it.