musescore / musescore/MuseScore

Issues with microtonal playback using custom key signatures

Open
#28,773 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Jul 15, 2025.

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

Description

Issue type

Other type of issue

Description with steps to reproduce
  1. Shif+f9 to create a key signature and drag Koron for B on the middle line.
  2. Press N to write B and Play the note. it doesn't work correctly (it didn't decrease -50cents)
  3. Try to put Koron next to the note (not key signature) , you may see it decreases -50cents without adjusting in tuning.
  4. If this problem will be solved, it will be great
Supporting files, videos and screenshots

When I use quarter intervals (koron and sori) in measure, it works correctly in the last update of muse score.
It means I don't have to go to properties to adjust tuning ±50 cents 👐
That's a good news when I put Sori or Koron next to the notes , it effects .
but when I put Sori and Koron on the key signature it doesn't work like sharp or flat.

I hope it will be solved because I don't want to put Koron and Sori in each measure.

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

Op

Regression

Choose option...

Operating system

Windows 10

Additional context

When I use quarter intervals (koron and sori) in measure, it works correctly in the last update of muse score.
It means I don't have to go to properties to adjust tuning ±50 cents 👐
That's a good news when I put Sori or Koron next to the notes , it effects .
but when I put Sori and Koron on the key signature it doesn't work like sharp or flat.

I hope it will be solved because I don't want to put Koron and Sori in each measure.

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.