Audio device changes don't "stick"

• Aug 11, 2020 - 00:57
Reported version
3.5
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
MuseScore

Ever since installing the latest update, when I try to change my audio device or API in the I/O settings, it won't actually change -- the apply button is greyed out, and when I reopen the window after pressing OK, the API and device are back to DirectSound and the original device I started with.

(Which is a problem, because when using DirectSound I don't get any audio and the play button doesn't do anything, for whatever reason.)

Things I've tried:
- Restarting audio devices from inside Musescore
- Restarting Musescore

I'm using Windows 10.

Comments

• Aug 12, 2020 - 08:44
Workaround No ⇒ Yes

I'm also getting the same problem. I think this may have something to do with changes to how Preferences are applied. When you change the API or Device, the apply button doesn't activate (still greyed out), however, if you change something else in the preferences in addition to API or Device, then the changes are applied.

Also using Windows 10

Reply

• Sep 12, 2020 - 21:26
Frequency Once ⇒ Many
Workaround Yes ⇒ No

The workaround provided works, thankfully, but I feel like this is something that really shouldn't need a workaround for.
I hope this would be considered as a priority for 3.5.1. I'm just bumping this thread in the hopes that the devs see it and agree on its importance, especially because this wasn't broken in previous versions. (I considered using 3.2.3 - the most recent officially available version before 3.5 - before I decided to look this problem up)

Reply

• Sep 12, 2020 - 21:28
Regression No ⇒ Yes
Workaround No ⇒ Yes

oh. that's how the workaround check box works. oops.

i should tick the regression box too while i'm at it.

Reply