musescore / musescore/MuseScore

MuseScore 4 - Chords are played in MIDI export even when turned off and muted

Open
#17,371 3 comments 7 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

General playback bug

Bug description

This bug was originally created by user room34. @MarcSabatella asked me to report it on GitHub.

When I export a MIDI file of the main score, which contains chord symbols, the exported MIDI file includes the realized chord notes, played with a piano sound, in addition to the actual part notes. This, even though the chords channel is muted and "chord symbols playback" is disabled.

room34 and myself tried:

  1. In the Mixer, setting the volume of the "chords" channel to the minimum value, and also muting the channel with the "mute" button.
  2. In "Playback Controls" toolbar, unchecking "Play chord symbols".
  3. Selecting a chord symbol in the score, choosing "Select… Similar on this staff" and unchecking "Play" in the Properties toolbar.

Still, in the exported MIDI, the chords are played.

Examples:

Thanks!

Steps to reproduce
  1. Open the attached mscz file, or have a score with some chord symbols in it
  2. In the Mixer, click the "mute" button on the "chords" channel. Also, lower its volume to minimum
  3. In the playback controls toolbar, disable "Play chord symbols"
  4. Export the main score into a MIDI file
  5. Play the exported MIDI file, and hear the chords being played on top of the other parts.
Screenshots/Screen recordings

test chords disabled playback

MuseScore Version

(64-bit) 4.0.2-230651553, revision: github-musescore-musescore-dbe7c6d

Regression

I don't know

Operating system

Windows 10 Version 2009, Arch.: x86_64

Additional context

No response

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.