musescore / musescore/MuseScore
opening .mscx file and editing syllabification/hyphens causes MS Studio 4 to crash
@ajuncosa is already working on this.
Since Sep 15, 2026.
- 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
- Open a file saved as .mscx in Musescore 3.6.
- There are more hyphens than the program normally would use; you can right-click and select them as a separate kind of object.
- Click through with the keyboard from one note on the same syllable to the next. The lyrics are in the wrong line, and there is no hyphenation.
- Go to the last note on the syllable before the new one; enter lyrics. This causes the program to crash.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/b2fb0f08-903d-41dc-9874-a5a839c37fbf
In which versions of MuseScore Studio is this issue present?
4.7.4
Regression
I was unable to check
Operating system
macOS 15.7.9
Additional context
The lyrics problem doesn't present in Musescore 3, but of course, that doesn't help me if I need to work in MS Studio. Saving a compressed file, then opening it in MS Studio did not fix the problem. Exporting a music XML file from Musescore 3, then opening that in MS Studio did seem to work; fixing syllabification works as I expect.
I reviewed #34096, and while it is not a strict duplicate, the issues appear related. For those who aren't early-music specialists, Nancho Alvaro, the developer of the lilypond lyrics plugin, created, edits, and maintains a website dedicated 16th-century Spanish sacred polyphony; Victoria website On this page, clicking any title will allow you to access the Musescore-compatible files that would, hopefully, allow for users to do the least amount of work possible.
I don't know if he's on GitHub, but his project is on Gitlab, so I'll let him know about the issues opened here.
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.