musescore / musescore/MuseScore

Glissando not exporting at all in MIDI MS4 and onward (not matching playback whatsoever)

Open
#34,680 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Functional glissandos, that match the MS4 playback, when exporting to MIDI.

Worked in MS 3.7 (Evolution) and before that; once MS4 (and continuing) hit, it has not worked like it used to.

Problem to be solved

From MS4 over to now, this has been an issue; where when you have any glissando on any instrument, it will export the MIDI data correctly (correctly being what the export for a MIDI File would result in; a clean study run, that would copy what was playing back in the MS sound engine.) MS3.7 (Evolution) and before that version, there was no issue with missing glissandos when export to MIDI.

This has been issue for years, and I hope this gets to the right people so this is fixed.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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.

Research direction

Start by reproducing the issue in MuseScore with a glissando, then compare playback with the exported MIDI file and check the behavior against MuseScore 3.7 and current MS4 or later versions. Done means MIDI export includes glissando data that matches the playback result.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.