Request to Include Chord Names (XF Chord Meta Events) in Exported MIDI Files
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the MIDI export entry point and the existing handling for chord data, lyrics, and musical notes. Compare the exported events with the attached Midikit example, then consider the work complete when chord names are embedded as XF Chord meta events and the export behavior is covered by tests.
Written by the indexing model from the issue text.
Description
Your idea
Hello Development Team,
I would like to submit a feature request regarding your software.
I kindly ask that the software be developed in a way that, in addition to song lyrics, musical notes, and chord sounds, the chord names (symbols) are also embedded in the exported MIDI file.
For reference, I am attaching a sample song that I created using MuseScore, provided as a PDF file, a MIDI file, and the original project file.
If you open the MIDI file generated by your software, you will notice that it contains the musical notes, song lyrics, and chord sounds; however, the chord names themselves are not included.
To achieve this, I used another software called Midikit to add the chord names to the MIDI file and then exported it. I am also sending you this modified MIDI file. This was done by adding Meta Events in the XF Chord format.
Thank you very much for your time and consideration. I hope this feature can be considered for future updates, as it would greatly benefit many users.
Best regards,
Problem to be solved
I would like to briefly explain why adding chord names (as MIDI Meta Events, such as XF Chord) to exported MIDI files would solve several real-world problems and be highly beneficial for users.
Currently, although the exported MIDI files include musical notes, lyrics, and chord sounds, they do not contain the chord symbols themselves. This creates a significant limitation for users who rely on songbook applications and arranger keyboards.
Many professional songbook applications and arranger keyboards (such as Korg PA series, Yamaha, and similar systems) depend on MIDI Meta Events to display chord names, synchronize measures, and provide accurate live-performance guidance. Without embedded chord symbols, these systems cannot fully utilize the MIDI file, making the workflow incomplete for live musicians.
As a result, users are forced to rely on third-party tools (for example, Midikit) to manually add chord names after export. This process is time-consuming, repetitive, and error-prone—especially when managing large song libraries. It also adds unnecessary complexity to an otherwise streamlined composition workflow.
By embedding chord names directly into the MIDI file during export, the software would:
Eliminate the need for external MIDI editing tools
Save significant time for users
Improve compatibility with songbook applications and arranger keyboards
Enable accurate chord display, bar tracking, and synchronization during live performances
Provide a more professional and complete MIDI export standard
From a development perspective, this feature builds upon information that already exists within the software (the chord data) and simply makes it available in a widely supported MIDI Meta Event format. This represents a high-value improvement with relatively low implementation complexity.
Adding this capability would greatly enhance the software’s usability for professional musicians, live performers, and arranger keyboard users, while also making the application more competitive and aligned with real-world performance workflows.
In addition, I am attaching several images to demonstrate how chord names are displayed in arranger keyboard songbook applications when they are embedded in the MIDI file. The software shown in these examples is Songbook+, which allows accurate tracking and synchronization of song measures using MIDI files.
Thank you very much for considering this request. I truly believe this feature would add significant value for many users.
Prior art
To resolve this issue, as I mentioned, I am forced to open the MIDI file exported from the MuseScore in Midikit and manually add the chord names there.
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
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·