No audio!
Reported version
3.5
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
No
Project
I updated to OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.2.311459983, revision: 465e7b6
Playback is disabled.
I try Edit->Preferences->IO->Port Audio->API
There are no options. Same for all other drop downs in that section.
Comments
See https://musescore.org/en/faq#faq-301733
It looks like it was a problem with an installation gone wrong.
When I installed the new version, it had a couple of conflicts with some kind of Qt file.
It rebooted my system at the end of the install, which is when I noticed the io/audio/playback problem.
I tried uninstalling Musescore, got the Qt file conflict again, let it reboot again.
I got a blue screen of death, twice, before Windows tried to roll back to the last good save point.
When windows finally booted again, somehow Chrome, Garratin, and loopMIDI were all messed up. The aria player and VST plugins were gone from Garratin (but the samples were still there), and Chrome wouldn't launch. LoopMIDI would not launch.
So, I reinstalled Chrome (fortunately Edge would still launch) and loopMIDI, and then musescore.
Musescore now correctly connects to loopMIDI and I can get MIDI in Reaper. I still need to reinstall Garratin.
So I don't know how the installation got SO messed up (I assume something about the recovery point for Garratin and loopMIDI, but no clue why that would bother Chrome), but I'd recommend that you test something like this sequence:
Run musescore 3.5.0
install Garratin personal orchestra
install loopMIDI (I didn't need ASIO4ALL because I use my focusrite asio which usually has fewer problems)
run reaper with a Garratin VST and point it at loopMIDI
try to connect musescore with loopMIDI (mine failed; it would find loopMIDI but would revert from ASIO to MME regardless of accept or okay)
make sure chrome is running
let musescore get the update for MuseScore version (64-bit): 3.5.2.311459983, revision: 465e7b6
run the installer without manually exiting musescore or closeing loopMIDI, reaper, and chrome. Close musescore when you get conflicts and then allow the installer to retry, then let it reboot.
Then try to recover. Hopefully it goes just as poorly for you as it did for me. ;-P
I know, I know, you said in the installer to make sure nothing else is running while the update is running, but ALL installers say that and this install of musescore is the ONLY time in the last TWO DECADES I've actually had problems if I ignore the warning. Anything you can do to make installs more robust would be appreciated.