Connect MIDI CC options to existing play engine controls
@RomanPudashkin is already working on this.
Since Jun 27, 2025.
Assessment
This issue has not been assessed yet.
Description
Your idea
Create a menu option to assign existing play engine data (like gain, velocity, and/or dynamics) as a translation to a cc controller (like cc1 - mod wheel / cc7 - master volume / cc11 - expression). This option would allow cross platform VST instruments and sfz libraries to use their layered sample functions in the performance of dynamic notation. A build example of this concept (without menu options) can be found here:
https://github.com/diedeno/MuseScore/actions/runs/15804170039
Problem to be solved
Virtual instruments (VSTi / VST3) cannot currently be mapped to streaming performance data from the play engine. This means that while VST instruments can be used, those instruments that have layered sample features may not derive proper cc control data from the play engine. As a result, such instruments and sfz libraries will only play one sample layer.
Prior art
No response
Additional context
Similar mapping was available with the Zerberus sfz synth in <MuseScore 3. While VST implementation is an enhancement, the loss of such mapping is a regression for these libraries and similar VSTi platforms.
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 ·