musescore / musescore/MuseScore

MIDI Trigger Regions

Open
#34,892 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

MIDI Trigger Regions would be useful when midi mapping can't make certain articulations (loops, repetition, note patterns) on midi mapping, i.e attributing these to a specific articulation in MuseScore like staccato, spiccato, tremolo, trills and much more.

This concept was done in Dorico and I think something similar should be in MuseScore 5.x.

Problem to be solved

Allow MIDI Trigger Regions, to be used with keyswitch and velocity.

Input a region where you can drag in your score and you can select a keyswitch area and velocity.

This is mainly for VST library samples with repetitions, loops and note patterns in mind.

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

The request names no files, tests, or entry points. Start by locating existing MIDI mapping, articulation, keyswitch, and velocity handling in MuseScore; define the region-editing and playback behavior, then verify the requested trigger cases.

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
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.