Musescore 4 crashes and doesn't reopen when other application managing a different audio driver is opened.

• May 20, 2023 - 17:48

Hello,

This is the way I reproduce the bug. Say I have Musescore 4 open and I want to use my DAW with asio4all while I'm scoring, so I open it. At that stage, Musescore 4 crashes and doesn't reopen.

I have:
1) Given priority to exclusive mode applications (otherwise my DAW will not play a sound - but not fail to load, like MS4 does in the opposite scenario).
2) Tried it with Ableton, and standalone VTSs.

I post this in case someone can replicate, I think it might be connected to the lack of audio driver functionality in MS4 in some ways. Honestly, we should be able to use asio4all. Let me know if you've seen this before!

Specs:
Processor Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz 2.90 GHz
Installed RAM 8.00 GB (7.88 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 10 Home
Version 22H2


Comments

You might need to un-check "Exclusive Mode" in Sound settings. It's not just MU4. Sibelius needs this turned off also.
Control Panel/Sound/select the audio device you are using then "Properties"/Advanced

In reply to by bobjp

I have already done that, see in my initial comment ("I have: (1)") what the outcome is.

However, MS3 is not having this issue, and I would not care at all how Sibelius handles things. I moved from Sibelius to MS3 because the latter was better, anyway.

Thanks for chipping in!

In reply to by bobjp

Dear Bob, I understand you are trying to help here, and I respect your time, so I'll tackle all the explicit and implicit comments you are making one by one.

0) When I post a potential bug, if you want to participate, please replicate with the steps I have included, and provide your response. Your Focusrite is hardly asio4all, with which I have replicated the issue multiple time and (crucially) to which my post refers.
1) It is not true that "you have to have everything you use open first, then open MU4". I have already tried this well before I posted the issue, again, with the particular (publicly available) components I am using. I don't have your Focusrite here with me.
2) "Yes, but the way MU4 works" & "If you have MU4 open and change audio settings, it will crash." I don't know what we're doing here. I am posting what I think is an issue and you are letting me know that it's a feature?

Best,
sik

In reply to by sikismymusicn

Then post your bug on GitHub. This is the place for discussion. I'm sorry my help doesn't meet your standards. There is more to things working, or not, than you may know. Just because software does something you don't expect, doesn't mean it's a bug.

0) I know about asio4all. But I don't need it for MU4. Does it show up as a driver In MU4? If not, that could be a problem. I mention the Focusrite for a good reason. We never know what might help

1) This is indeed true. If not there may be a driver problem. I don't have your system, so it's hard to tell. For that matter, no one has your system, so to help you, people need to mention all kinds of things in the hope that something might work.

2) I'm saying no such thing. If you are on the page where you activate Exclusive mode and you change something there (especially bit rate) you will get a message that whatever audio software you have open (like MU4) will close.

In reply to by sikismymusicn

No one on this forum is a developer. No one on this forum is works for MuseScore. We are just a bunch of users like yourself. We are all just trying to help each other. Anyone is welcome to jump in at anytime to help you. If you let them.
I hope someone does come along and help you. I would be interested in the answer. This how we all learn about MuseScore. That's what this forum is for.

I have the same issue but it's every time i plug in / pull off my earphones... i keep forgetting ms4 crashes when i do that so i lost a few minutes of work multiple times over this

Do you still have an unanswered question? Please log in first to post your question.