musescore / musescore/MuseScore

Normal guitar bends play back as a linear sloped pitch bend, when the visual graph in Properties is exponential

Open
#33,396 5 comments 0 reactions 3 assignees View on GitHub

@abariska is already working on this.

Since May 15, 2026.

needs review 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. Input a bend, the longer in duration and larger in range, the more obvious the issue becomes
  2. Play back the bend
  3. Observe the linear playback, when the properties graph shows exponential
    Ideally, the playback should match the graph shape
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/2128ef24-c30b-4d9b-a8e2-908bcaa8785a

In which versions of MuseScore Studio is this issue present?

OS: Windows 11 Version 25H2 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.7.0-260513133, revision: github-musescore-musescore-9989a50

Regression

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

Operating system

Reported on Windows 11

Additional context

Because the "Dive" item from the guitar palette has a linear graph, and the normal pitch bends have an exponential graph, these two items should reflect their own graphs, rather than both being played as linear.
Additionally, with regular pitch bends having switched to linear from exponential, it is no longer possible to get an exponential playback, and older scores with bends relying on the exponential shape will all need to be reworked.

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.