MuseScore 4 won't start

• Dec 23, 2022 - 12:36

I know others had the same issue: I was very excited to try MuseScore4 when I got the mail announcing the new version.

I installed the Win 64bit version (with and without musehub, I tried both), but MuseScore 4 won't open. Splashsreen appears but disapperares after some seconds an that's it :-(

Is there a solution for that issue??

Regards,

Hans

Comments

• Apr 17, 2023 - 12:23

just tried latest nightly. It does start where the stable version just quits, but the sound is played like 2x as fast in high pitch like MU4 is on steroids. If you use a output device that was already working with MU4.0.2 sound is played normally. I don't know if it has anything to do with Samping Rate or so (48khz vs 44.1khz)

Reply

• Dec 23, 2022 - 13:58

Thx, but did not help. The Splashscreen doesn't disappear here, but process hangs with 17MB memory and 0% Activity.

Reply

• Dec 27, 2022 - 16:04

Hi, tried it all including uninstalling and reinstalling with an and without Muse Hub (and @Horst: switching the printer on and off). Same result. Unfortunately I can't get musescore 4 work. Perhaps I'd try again in a couple f weeks when this is fixed. I guess there are more users confronted with this issue.

Regards,

Hans

Reply

• Dec 27, 2022 - 16:13

Update: I just found an approach in another chat: changing my computers audio output from my Bose USB-system to my AirPods made musescore 4 start. Good to have a reason for the behavior now, bad, cause my Bose system is the standard audio output for me. - Is there a chance that this will be fixed?

Reply

• Feb 7, 2023 - 04:13

Same here. When I run MuseScore 4, the splashscreen appears and then disappears without the app starting. My Windows Sound output is set to Bose USB Audio. When I change it to something else and restart MuseScore 4, it starts. If I then go into MuseScore's Preferences / IO and change the Audio device to Bose USD Audio, MuseScore briefly freezes and then crashes, so @bobjp's suggestion doesn't seem to help here.

Reply

• Feb 7, 2023 - 17:54

Hmmm. Do you have the latest driver? I have two completely different interfaces that work well. One is a Focusrite Scarlett. The other is a cheap discontinued Diamond Sound Tube.
This may sound funny, but what if, after you have MS4 open, you change Windows sound back to your Bose before you change it in MS4?
What are your Computer specs?

Reply

• Jan 1, 2023 - 22:38

Hi, I have the same problem. I cannot start Musescore 4 and get a message after installation:

'Kan toegangspunt van procedure MFPutWaitingWorkItem niet vinden in DLL-bestand MFPlat.DLL'

Ik heb geen Windows 10, maar werk nog met Windows 7 omdat mijn pc geen W10 aankan.

Reply

• Mar 12, 2023 - 21:40

Hello. I tried reinstalling Muse Hub but there is no way to send the previously installed version to the trash, since I get the message " "The item 'Muse Hub 2.app' cannot be moved to the Trash because it is open", although it is NOT open. The system I am using is a macOS 13.2.1

Reply

• Jan 3, 2023 - 12:39

Same issue here, though by reading through the comments on this post, I found out what works for me: if I change the speaker settings from my Focusrite soudcard to the internal PC speakers (system default) then Musescore will start up and work.
It is absolutely disturbing though to have to notice that no error message whatsoever is displayed when the program bails out and the splash startup screen is removed ... leaving us with a blank screen. Definitely someone would expect to be caught by software developers (I'm sorry, even in an open source context.
Pretty sure it will be looked into ;°)

Reply

• Feb 20, 2023 - 18:27

No, still not working. I tried the latest stable version today since it's been some time that I tried. I've switched to musescore3 again cause I don't want to wait and I noticed that ms4 files won't work if you try and open them in ms3. Too much work lost...

Reply

• Apr 17, 2023 - 11:37

Same here it's not working with most sound outputs like Nvidia HDMI, VoiceMeter or Soundblaster X4. It works with Jabra 370 Headset and Virtual Audio Cable. I wonder if it has something to do with output type 7.1 or 5.1 drivers... I wonder when they get this sorted. It's open since 4 Months now at least

Reply

• Apr 17, 2023 - 13:44

Since I get notifications from this thread almost every day, I'll give you a quick update, hoping to cool it down a little bit:

  • It is clear that the crash is indeed caused by audio devices with more than two output channels (or sometimes other configurations also cause it)
  • The crash was fixed, but for some miraculous reason it still happens in "installed" builds of MuseScore. It's really weird: if you download a nightly build, it works perfectly. But if we would give you a build from exactly the same code but with an installer, and you install that build, then it will crash. This mystery is what makes this issue so difficult to solve.
  • So, the workarounds are:
    1. Use a different audio device / configuration
    2. Use a "nightly build" (with the added benefit that it includes dozens of bug fixes that have not yet been part of an official release, but with the caveat that it might contain some new bugs too.)
  • When you use a nightly build, it will launch correctly, but playback will still sound high-pitched and too fast if you use an audio configuration with more than two channels. This issue is also quite difficult to fix; we do understand what goes wrong, but it is not quite easy to come up with a good solution that will not negatively affect the performance.

Reply

• Apr 19, 2023 - 00:54

I am also having similar issues opening Musescore 4.0.2, where the loading screen comes up, and then goes away.

I did have a version of Musescore 4 on my computer previously; it worked and I used it. My hard drive was recently replaced and my OS ported over, but I now need to reinstall my programs. I downloaded and installed the latest version of Musescore 4. When opening, it only goes to the loading screen and disappears after about 2 seconds or so.

The build/version of MuseScore 4 I previously had installed and successfully used was downloaded and installed on Feb. 9, 2023, and used it successfully after that. Based on the Announcements page, it looks like I had been using release 4.0.1.

I have uninstalled and reinstalled the 4.0.2 release a few times now, both without MuseHub and with MuseHub.

I note in the previous threads that there has been issue with a sound system driver. I am just using the laptop’s built in system, so there is nothing I can disconnect. The driver is nothing special – just a standard Microsoft driver. No enhancements are turned on.

My laptop is an older one, but functions well. The specs are:

• Acer E 15
• Processor: Intel(R) Pentium(R) CPU N3S30 @ 2.16GHz 2.16 GHz
• Installed RAM: 8.00 GB (7.89 GB usable)
• System type: 64-bit operating system, x64-based processor
• Windows Edition: Windows 10 Home, 22H2 Version (my computer is not compatible with windows 11)
• OS build: 19045.2846
• Windows Feature Experience Pack 120.2212.4190.0

My questions:

• Is there a troubleshoot that should get 4.0.2 working?
• Was there a specific change from 4.0.1 to 4.0.2 that would allow the former to work on my machine but not the latter?
• Is 4.0.1 available somewhere for download? I see that the "old versions" page has various Musescore 3 builds, but not the MuseScore 4 builds before 4.0.2.

I still have the version of MuseHub I downloaded on Feb 9th. Does that file include the Musescore 4.0.1 build in it,or does it automatically point to the latest version? Here are the MuseHub particulars:

• File description: Muse Hub Installer
• File / product version: 1.0.1.693
• Size: 37.3 MB

Thanks,

Jean-Louis

(also posted on a few days ago on https://musescore.org/en/node/347098)

Reply

• Apr 19, 2023 - 15:44

You can download MuseScore 4.0.1 from https://github.com/musescore/MuseScore/releases/tag/v4.0.1.

It might also be interesting to try how "nightly builds" behave: https://musescore.org/en/nightly-builds

Regarding the changes in 4.0.2: it's difficult to say what may have been the culprit. There were some changes related to the audio driver, but in all those months I haven't heard of any cases where this has caused new problems. It rather fixed the problems for some people.

It might be useful if you could upload the log files. In Windows Explorer, go to %localappdata%\MuseScore\MuseScore4 (paste that in the address bar in Explorer), locate the logs folder and compress this folder into a ZIP file. Then, upload that ZIP file here. (After that, you can delete the ZIP file, in order to not waste disk space on it.)

Reply

• Apr 19, 2023 - 18:57

Great thanks.

So, I uninstalled 4.0.2 and was able to install 4.0.1.

But when I went to open it, I had the same issue. That tells me then that the issue is not the change between 4.0.1 and 4.0.2, but rather an issue with version 4 in general and my system.

Unfortunately, I can't say specially what about my systems ops is different (other than I had my screen replaced and a new SSD put in).

I have attached the new version of the logs that would include the crash of 4.0.1, if it helps.

Also - if I can find the old logs on my old hard drive (which I have), where 4.0.1 did work - would they help?

JL

JL

Attachment Size
JLG_MS_402_logs2.zip 10.27 KB

Reply

• Apr 21, 2023 - 01:57

Breakthrough!

It suddenely occured to me that one thing not the same with my laptop setup was that I had not yet hooked it up to my extra display monitor. Typically, when I do that, the sound comes out the display monitor (via hdmi cable) and not my laptop.

I plugged the display monitor in, and I noted that the output device was now listed as my display monitor (VG245 Intel Display Audio) and not the built-in laptop speakers.

I ran the MuseScore 4 nightly exe file, and it worked.

I then downloaded and installed MuseScore via the MuseHub off the website, and it also worked.

So it looks like the issue was use of the built-in laptop speakers. FYI, the display monitor is an Asus VG245.

If the logs are helpful to you, I can provide.

Cheers!

JL

Reply

• Apr 21, 2023 - 08:30

Well, I wouldn't call switching to another sound device a solution or workaround. What if you only have 1 sound device or the only sound device that works is not near your computer where you run musescore? This issue is a Major issue for a lot of people and is still not beeing solved after months! Instead I see a lot of minor bugfixes on the 4.0.2-dev and also the nightlies do not work. I tested them and they have another nasty error. When you switch to a previously non working sound device MuseScore no longer closes, It just plays the arrangement in 2-3 times speed with very high pitch. As soon as you switch back to a sound device that's also working with current 4.0.2 it plays in normal speed. So whatever you tried to fix it improved things a bit in the sense that MuseScore does not crash but 2-3 times speed increase with high pitched notes makes the sound device as unusable as it was before.

Reply

• Jan 4, 2024 - 14:43

Hi everbody,

after a long time I gave musescore 4 another chance today to see if I can use it now.

  1. The app starts now even though my standard audio output (bose usb audio) is active. That's fine!
  2. Playing any score still leads to some "Mickey Mouse sound" - far too high and far too fast.

Any idea how this can be solved? - Other Audio output devices (e.g. my AirPods via bluetooth) work fine.

Regards,

Hans

Reply

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