Cannot choose ASIO driver

• Dec 19, 2022 - 10:17
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
MuseScore

Nice job with MS4

but it seems so CPU demanding that both when I insert notes with my keyboard and with the playback the latency is so high that it is impossible to work with, and even if I wait the 4/5 seconds for the playback to start the result is an awful glitchy mess.

I think the main problem is that MS is using the lame integrated sound drivers, while it seems I cannot choose to use my ASIO drivers (focusrite asio, to be more precise).

Is there anyway to fix this problem?

MAny thanks

Comments

• Jan 7, 2023 - 13:53
Workaround No ⇒ Yes

Hello Guys :)

Before we see the fix for the ASIO system, I suggest a simple way to work around the problem (maybe not perfect, but it works and can be used as in MS3.6)

  1. I assume that anyone who has a latency problem has an external audio interface (FocusRite, Behringer, Steinberg, etc.)

  2. Connect the midi keyboard to the interface.

  3. Run any VST instrument in the background (e.g. Sampletank) and set it to play from the interface

  4. Set Musescore to be played from the computer's built-in sound card (e.g. High definition audio device)

  5. By typing music, mute the internal card with the windows mixer and listen from the ASIO interface.

  6. Playing with Musescore unmute built-in sound card :)

I know it's a bit weird and it's better that MS4.0 has built-in ASIO but you have to deal with it.

P.S.

Fortunately, I have an external Alesis mixer, so when I enter music, I mute the internal one and when I listen, I turn the sound back on.

I hope I helped and that you will be able to use MS4.0 fully before we see a working ASIO API.

Regards

David (TipyPata)

Reply