Conflict between MuseScore 3 and FL Studio 12 (Sharing ASIO driver 2.14)

• Oct 12, 2021 - 16:34
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

It appears that when FL Studio 12 and MuseScore 3 were installed together (FL before MuseScore) there is a major conflict when MuseScore 3 is opened. The following error message is triggered by ASIO driver on starting MuseScore:
"FL Studio ASIO Error Couldn't initialize rendering in shared mode! Code:-2004287473"
and thereafter the computer is no longer able to play any sounds or music (as though as the sound card is now disabled), until the computer is restarted (a disable/re-enable of audio drivers does not work). This however does not happen when FL Studio is opened instead. I am using ASIO driver 2.14 and speaker: Realtek High Definision Audio(SST). Is there a fix for this?

The only trace logs I can find on the Windows Event Viewer tool is this warning when any sound is trying to be played after the ASIO driver crash:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{...}
and APPID
{...}
to the user [...] from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy SID (...). This security permission can be modified using the Component Services administrative tool.

Attachment Size
FL Studio ASIO Error.PNG 4.58 KB

Comments

Workaround No Yes

I think I might found a workaround... apparently upgrading ASIO4ALL to the latest beta (2.15 beta 2) might fix it.