musescore / musescore/MuseScore

Exporting Midi options

Open
#33,283 0 comments 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

When exporting midi. Allow us to include or exclude midi cc information to the new midi file. Ie. Do not include text events, ect per user selection.

Problem to be solved

Currently when exporting midi to other programs. Musescore may generate information thats not needed or may potentially conflict with the intended use. This would allow the user to select what information is actually saved so those issues don't arise. Skipping the steps of needing to clear midi cc lanes manually a daw.

Prior art

No response

Additional context

My suggestion would be to have a drop down list with all of the midi cc lanes and there corresponding title. An indicator of any information present and a box to toggle saving said information on export. This wouldn't change any info musescore has, just what is exported in the exporting menu. Last but not least, let Musescore save these settings so they persist via other sessions and updates either as a global setting or per session. Maybe also add the ability to save and load user made presets. Information regarding midi cc lanes can be found easily on google.

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 at the MIDI exporting entry point and review how export options are presented. Define the scope of selectable MIDI information, including CC lanes and text events, along with whether settings are global, per session, or preset-based. Done means users can choose which information is exported and the selected settings persist as specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.