musescore / musescore/MuseScore

Arpeggio line delays notes by almost half a beat on pitched percussion tied notes (Not Musesounds)

Open
#29,273 1 comment 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Aug 15, 2025.

P2 playback regression MS4
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

General playback bug

Description with steps to reproduce
  1. Make a score with a pitched percussion instrument
  2. write a tied chord with an arpeggio symbol on it
  3. playback, see that the start of the arpeggio notes don't happen until a bit less than an eighth note after they are supposed to
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/bcffbcfd-0909-47b8-a5fc-15ecbd7174b1

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Reported on Windows 11

Additional context

This doesn't happen when using muse sounds, I've only heard it with soundfonts, haven't tried VST
The more ties on the chord, the longer it delays the start of the arpeggio, the first tie has the most impact

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.