Does not show I/O devices

• Feb 4, 2020 - 00:04
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
Yes
Workaround
Yes
Project
MuseScore

Start MuseScore
Press P to hear sound - no sound
Click Edit Preferences I/O to set headphones - no options shown

Attachment Size
2020-02-03 (3).png 303.99 KB

Comments

• Feb 4, 2020 - 08:28
Title Newly-installed MuseScore 3419660 does not show I/O devices - no sound - previous version worked fine - see screenshot. Yes I reset to factory settings yes I restarted computer yes I restarted MuseScore. ⇒ Newly-installed MuseScore 3.4.1-9660 does not show I/O devices - no sound - previous version worked fine - see screenshot. Yes I reset to factory settings yes I restarted computer yes I restarted MuseScore.
Severity S1 - Blocker ⇒ S3 - Major
Status active ⇒ needs info

Doesn't stop you at all from using MuseScore to see and enter scores, so certainly not a blocker.
Why should pressing P produce any sound? It just opens the piano tool, for starting playback hit the space bar
Also try to use that 'Enable MIDI' button (twice to toggle off and on, it has helped in other cases og missung sound

Reply

• Feb 4, 2020 - 11:24
Title Newly-installed MuseScore 3.4.1-9660 does not show I/O devices - no sound - previous version worked fine - see screenshot. Yes I reset to factory settings yes I restarted computer yes I restarted MuseScore. ⇒ Does not show I/O devices

Reply

• Feb 4, 2020 - 14:24

Thank you for the two responses so far. Are you devs?

Yes I clicked in the piano keys to try to hear sound, result no sound. Should have said that also.

Yes I can still compose. Not being able to hear as I compose is a blocker.

I realize MS is open source community driven and I am a paid subscriber. Reporting bugs on new releases is a duty to keep MS available as we and it evolve. I run MS concurrently on three separate PC's and keep track of what versions they run and when / what issues may be. This new release I just installed on one machine and this new bug was immediately obvious.

For any devs: using bluetooth noise cancelling headset (sony) reproducing this bug. Same headset ok for last 12 months on current release minus one, minus two.

Also for devs: my best guess is in MS interaction with windows OS sound device setting. MS does not seem to recognize when bluetooth and usb headsets are swapped. It stays with the first setting and does not seem to update preference options. My workaround was to restart MS and manually select i/o devices and restart audio drivers every time I changed headset. On this release that workaround is defunct since no i/o devices are shown (see original screenshot). Still ok on release minus one.

Best Regards,
James

Reply

• Feb 4, 2020 - 14:32
Workaround No ⇒ Yes

You may be a paid subscriber of a Pro account on musescore.com, but that has no bearing whatsoever here on musescore.org or with the MuseScore program. Just in case you were not aware...

Bluetooth headsets are causing a lot of issues apparently, normal wired ones or normal (wired) speakers much less so, so there's a workaround

Reply

• Feb 4, 2020 - 14:46

Jojo, hello! Thank you for your response. What is the bluetooth workaround?

Regards,
James

PS Apologies if you took offense, none intended I assure you : )

Reply

• Apr 10, 2020 - 03:30
Regression No ⇒ Yes
Workaround Yes ⇒ No

> Same headset ok for last 12 months on current release minus one, minus two.
If this worked before in 3.3.2, i understand this should be flagged as regression. Also, i don't think advising the user to use different hardware should be considered a workaround - i'd expect a workaround to be something one can do software-wise to work around the issue until it is solved.

Also, should be maybe create an EPIC to gather all open issues regarding bluetooth connections, so we have them all in one place?

Reply

• Jul 18, 2022 - 01:11

Still a problem with 3.6.2.548021803 I got some new BT headphones Baseus Encok D02 Pro last week ( BT 5.0 ? ). I noticed Synth was greyed out, and I/O was missing Port Audio settings. I think the start up sequence/order may cause this. My normal on board audio loads API and Device no problem. If I close MS, change to BT headphones in Win 10, restart MS, all seems to be fine. But, If I start MS for the first time with Baseus BT already connected, then it seems to lose Port Audio settings... just a theory. I did not notice this problem with my Sennheiser LE-HD 458BT headphones, but then again, can't be sure which order I connected everything. I can go back to using them, but my work around is to start onboard audio first.

Reply