musescore / musescore/MuseScore

'Play chord when editing' preference changes

Open
#26,219 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Jan 24, 2025.

P2 playback UI
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

Follow-up from #24352.
Related follow-up task: #26224

Background
In Preferences > Note input, 'Play chord when editing' does not work entirely as described. When it is turned on, adding any note to a chord will play back the whole chord. When it is turned off, adding a note to the chord will not play the chord (as expected), but it also won't play any individual note added.

The copy also does not accurately describe the behavior.

Solution

Change 'Play chord when editing' from a checkbox to a dropdown.
Label: 'When adding notes to chords'
Dropdown options: 'Play the entire chord' and 'Play only the added note'

Playback changes

  • When set to 'Play the entire chord', it should act the same as when 'Play chord when editing' is checked on now.
  • When set to 'Play only the added note', when adding a note to a chord, ONLY that note should be played back, not the entire chord.

Image

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/06ece272-4394-4470-8b68-22d516d69d7b

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

Nightly

Regression

No.

Operating system

macOS 15

Additional context

No response

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.