musescore / musescore/MuseScore

Musescore won't export audio file

Open
#30,342 15 comments 0 reactions 3 assignees View on GitHub

@zacjansheski is already working on this.

Since Oct 6, 2025.

crash needs review VST
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Description with steps to reproduce

I had to replace the hard drive on my computer. After reinstalling MuseScore and MuseHub, I had one particular file which would cause the program to shut down when I tried to save to cloud or export as an audio file. After updating to version 4.6 the save to cloud seems to be working, but exporting an audio file still causes a crash, sometimes almost right away, other times part way through the export.
I don't know how to do screen recordings, crash logs or diagnostic files. I will attach the score causing the problem.

Supporting files, videos and screenshots

Here is the score/ file causing the problem. I tried to save it as a zip file, but the file (folder?) wouldn't upload, so here are the contents?

audiosettings.json

viewsettings.json

container.xml

Image
In which versions of MuseScore Studio is this issue present?

4.6

Regression

Choose option...

Operating system

Windows 10 Pro

Additional context

I'm sorry, but I don't have time t o look through 136 pages of reported issues, and since this is a new issue with and existing file that didn't change since the new hard drive install, I don't see a reason too. Besides, I was advised to report this by someone on the forum - mercuree

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.