MuseScore gets stuck on splash screen if USB audio interface is not connected to computer
This has just started happening in the last month or so. It took some time to figure out the connection because I didn't really pay attention to when my USB interface was in use or not.
I have tried (multiple times) re-setting MuseScore to defaults, restarting, re-installing, and re-configuring the I/O to use anything except the audio interface. MuseScore will not move past the splash screen if the audio interface is not already connected, it just gets stuck drawing around 30-40% CPU. I have left it for over an hour and that doesn't change.
OS: Windows 10 Home v1909 build 18363.900 (64-bit)
MuseScore version (64-bit): 3.4.2.9788, revision: 148e43f
I used a program called SysInternals Process Monitor to capture the behavior of MuseScore starting, with and without my USB interface connected. CSV files here. I hope that is useful.
Comments
There is no attachment.
Try 3.5 Beta or a later 3.x development build, those to send some output to the splash screen, giving information what they are working on
In reply to There is no attachment. Try… by Jojo-Schmitz
Shit, it said it was attached.
Will try the development version in the meantime.
Files are here: https://gofile.io/d/VVcODv
In reply to Shit, it said it was… by ohnoitsalobo
And here now too, but zipped to not exceed the allowed size for attachments
In reply to And here now too by Jojo-Schmitz
Thank you. Is there anything useful in those logs from Process Monitor?
In reply to Thank you. by ohnoitsalobo
No idea how to interpret those
In reply to There is no attachment. Try… by Jojo-Schmitz
No luck. I installed the development version and it does not start, stuck on splash screen.
In reply to No luck. I installed the… by ohnoitsalobo
What is the last output on that splash screen?
In reply to What is the last output om… by Jojo-Schmitz
"Initializing sequencer and audio driver" Imgur
This happens with both the 3.5 Beta and the latest 'nightly' build.
Again, they start up okay IF my USB audio interface is connected.
In reply to "Initializing sequencer and… by ohnoitsalobo
Better attach here directly:
![u5tKXCN.png]( "u5tKXCN.png")
In reply to Better attach here directly … by Jojo-Schmitz
I tried, but for some reason it is not allowing me to attach files. I can select files but it doesn't get 'attached' to the comment. I don't know why this is.
In reply to I tried, but for some reason… by ohnoitsalobo
See https://musescore.org/en/node/289899
In reply to See https://musescore.org/en… by Jojo-Schmitz
That's what I'm saying, for some reason it doesn't work, the files are "selected" but not getting "attached" to the post when I submit. That page doesn't tell me anything helpful.
Anyway, I have other ways to send files, I still have no clue what exactly is causing MuseScore to become so dependent on my audio interface. I tried the beta and nightly versions with no success.
In reply to That's what I'm saying, for… by ohnoitsalobo
Maybe reverting to factory settings helps?
In reply to Maybe reverting to factory… by Jojo-Schmitz
I mentioned up in the original post, resetting MuseScore to default settings doesn't seem to help. Unless you mean my laptop, which I am considering as a last resort but I really don't want to have to reset my laptop.
In reply to "Initializing sequencer and… by ohnoitsalobo
OK, so it seems to really got stuck where it is to be expected in this case.
Not sure why though
In reply to OK, so it seems to really… by Jojo-Schmitz
I haven't solved why it happened, but it seems I've fixed it by uninstalling another audio-related app. It seems to be working again.
In the past few weeks I was experimenting with an app called Voicemeeter and it seems there was some behind the scenes fuckery in the audio devices which resulted in MuseScore not being able to start if the USB interface was disconnected.
Again, I didn't make the connection until now because I wasn't regularly using the Voicemeeter app, also not paying explicit attention to when exactly I was or wasn't using my USB interface.
I haven't solved why it happened, but it seems I've fixed it by uninstalling another audio-related app. It seems to be working again.
In the past few weeks I was experimenting with an app called Voicemeeter and it seems there was some behind the scenes fuckery in the audio devices which resulted in MuseScore not being able to start if the USB interface was disconnected.
Again, I didn't make the connection until now because I wasn't regularly using the Voicemeeter app, also not paying explicit attention to when exactly I was or wasn't using my USB interface.
In reply to I haven't solved why it… by ohnoitsalobo
Maybe add this to https://musescore.org/en/handbook/known-incompatibilities ?
In reply to Maybe add this to https:/… by Jojo-Schmitz
Perhaps I would, but it's not well-defined. I don't know what the specific incompatibility was, it may have been due to the specifics of my setup, not VoiceMeeter itself. Impossible to say.
I experience the same behavior (Musescore getting stuck in start up, trying to "initialize sequencer and audio driver). I suspect the issue is a conflict between my a USB driver/interface for a Yamaha THR10 amplifier or the associated Steinberg Cubase software that came with the THR10. From the command line, Musescore starts without problem when I use the "-s" flag to disable the audio capabilities, but I actually need the Musescore audio.
I have an identical laptop where I don't have this other audio software installed, and Musescore is working on that machine. Ideally I'd like to be able to use all my software on the same machine, even if that meant switching audio drive configurations back and forth. Right now, I don't know if the issue is a registry setting, or driver software that isn't configurable, or if this is something that could actually be fixed.