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.įortunately, 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. Playing with Musescore unmute built-in sound card :) High definition audio device)īy typing music, mute the internal card with the windows mixer and listen from the ASIO interface. Set Musescore to be played from the computer's built-in sound card (e.g. Sampletank) and set it to play from the interface Run any VST instrument in the background (e.g. I assume that anyone who has a latency problem has an external audio interface (FocusRite, Behringer, Steinberg, etc.)Ĭonnect the midi keyboard to the interface. Are there any buffers or resource configurations I can adjust?īefore 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) I do have a question for the engineers - is Musescore 4 multi thread capable and to use all available system memory? I have a big computer and Musescore just doesn't seem to be using much of it. It takes a long time to show or hide instruments, when editing my 200 measure 16 part score.Īll I can suggest is get the Windows 10 update (if you use it) and wait until the optimization is studied. My MS4 is still having trouble switching instrument track visibility. Remarkably, the zoom and panning is now much improved. I was having severe issues, until yesterday, when a forced update of my Windows 10 was performed. There is a 'todo' scheduled to investigate and improve performance, so perhaps when they have time it will help. I have another post in this forum about this same issue with large scores. It was been in Github and, if we are speaking of the same issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |