musescore / musescore/MuseScore
Playback skipping notes
@sampleeditor is already working on this.
Since May 29, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Choose option...
Description with steps to reproduce
I submitted a playback issue to Muse Sounds team, they reviewed it and said it seems to be a problem in Muse Score Studio playback. So I'm submitting it here.
I am having issues playing back scores using Musescore Studio 4.7.0 using Muse Strings. The issues were already present in previous versions. My Muse Sounds Manager is up-to-date and all my Muse Sounds are up-to-date. My system is Fedora Linux 44 and my Musescore Studio is the appimage downloaded from the official site. Here are some attachments demonstrating the issue. The playback skips notes in violin 2, viola, cello and cellos section. The attachments demonstrate some examples, except in viola where they occur but I forgot to catch it in an example. The issues become very worse when adding classic phrasing staff text, but also occur without it. The issues occur in notes without any articulation and in most cases but not all, adding some articulation to the skipped note or to the note before it restores playback. But that's only a workaround because sometimes we want a note without articulation and using classical phrasing exactly to get phrasing precision and then when the note is skipped we have to add louré, tie or any other unplanned articulation just to make those notes be played.
Supporting files, videos and screenshots
I'm sending some attachments.
In which versions of MuseScore Studio is this issue present?
Musescore Studio 4.X (all versions)
Regression
No.
Operating system
Fedora Linux 44 KDE
Additional context
I'm trying to figure out the right place to post it, so I ended up posting it in forums and then here again. Sorry.
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.