musescore / musescore/MuseScore

Parenthesized notes cannot be made to play normally

Open
#34,112 1 comment 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

P2 playback
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. Write a series of identical notes
  2. Place parentheses around one of them
  3. Play

Result: the parenthesized note plays softer and/or shorter than the others (specifics depend on the instrument/sound). In some cases, this is expected - the parentheses might be intended to indicate a muted or ghost note. But in other cases the parentheses might be editorial in nature. So while it is argukmably OK to default to using ghost playback, it should be possible to disable this by unchecking Play from the parantheses. This has no effect, however.

Supporting files, videos and screenshots

This is using MS Basic, where the effect is present but a bit subtle:

https://github.com/user-attachments/assets/89cdaf76-8552-4f3b-9a92-577be6067d8c

It's much more obvius with MuseSounds - for example Muse Keys / Grand Piano.

In which versions of MuseScore Studio is this issue present?

4.7.4

Regression

I was unable to check

Operating system

Debian 12

Additional context

I think MuseSounds may have only started doing this automatic mute playback for instruments other than guitar recently, but I can't be sure. I don't think MS Basic did in the past, but it does now - just not as strongly as MuseSounds. But I'm less concerned with the default than I am with the inability to disable the effect.

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.