Chord track is affected by fixupMIDI() when same pitch appear on the main track

Open
#27,827 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
audio-video-rtc

Research direction

Reproduce the problem using example.zip by exporting the score as an SMF, then trace the fixupMIDI() path involved in handling simultaneous notes on the main and chord tracks. Compare the exported notes and verify that chord-track notes are no longer discarded or shortened when the tracks use different MIDI channels.

Written by the indexing model from the issue text.

Description

MIDI
Issue type

Import/export issue

Description with steps to reproduce
  1. Write a chord symbol.
  2. Write a note contained in the chord symbols simultaneously in different voices.
  3. Export as a SMF.

Actual behaviour: In the exported SMF, there is a discarded or shortened note in the chord track.
Excepted behaviour: Notes on the chord track should not be discarded because the main track and chord track are not on the same MIDI channel.

Supporting files, videos and screenshots

example.zip

Image

Image

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

MuseScore Studio version (64-bit): 4.5.1-250800846, revision: github-musescore-musescore-603eca8

Regression

Choose option...

Operating system

Windows 11 x86-64

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
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.