Allow Bluetooth-, other Sound- and MIDI-devices to be turned on after MuseScore loads
Type
Functional
Frequency
Many
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Using MuseScore 2.3.2 on a Mac.
If I have MuseScore open, and I connect a bluetooth speaker or headphones, the audio won't play out of that device, even when I check my computer's sound settings to make sure that the audio output is set to the bluetooth device.
This is not an issue when plugging an audio device into the audio jack. I recently upgraded my OS to macOS Mojave, but this issue was also present before the update.
A current workaround is to quit MuseScore, and reopen it after the bluetooth device is connected.
I'm looking to get involved as a dev on this project, but I haven't become too familiar with it yet. Could someone point me at a good place to start resolving this issue?
Comments
Bluetooth and midi devices have to be plugged in and turned on prior to starting MuseScore. This is a known, documented limitation. Perhaps this should be changed to S5-Suggestion for it to be fixed, rather than a bogus bug report. I'm not a programmer, so I don't know what's causing this limitation.
An easier workaround is to toggle (off and back on) the MIDI button in the toolbar (looks like a 5-pin DIN connector).
Or to use Preferences > I/O > Restart Audio and MIDI devices
In reply to An easier workaround is to… by Jojo-Schmitz
It doesn't seems to work. Maybe this is an unsolved issue in Musescore (the fact that there are no output devices in Preferences > I/O when I connect my Bluetooth headphones). I say this because I investigated a lot about this problem, and I didn't find a solution. I mean, there is not an answer that solve this.
I'll leave you an image below so you can see the problem. When I click the Device box ("Dispositivo"), no option is displayed. It's like an useless box when my Bluetooth device is connected.
Anyway. I hope this problem can be solved. This software is amazing anyway. Thanks for the great work. I hope I can understand the code in a future to join this community.
That workaround does work, at least in a large majority of cases
Just to perhaps provide some extra bit of information for the devs, I've always had the exact same issue as well, and the workaround @Jojo-Schmitz described does work for me, in MuseScore version 3.6.2.548020600, on a Late 2013 MacBook Pro running macOS High Sierra (10.13.6).