musescore / musescore/MuseScore

Ability to modify "gate time" and default velocity for all articulations within UI

Open
#22,446 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Currently you can save using the "uncompressed MuseScore folder (experimental)" format and edit the mscx file to specify how articulations should be played by default, but this is quite painful and not reasonable to expect for the average user (who is likely to introduce syntax errors into the xml etc.).
A screen that allows editing these values would be well justified.
The default gateTimes are not appropriate in many cases, even for unarticulated notes.

Problem to be solved

Having to save using the "experimental" format then edit xml files:

        <Articulation name="staccatissimo">
          <velocity>100</velocity>
          <gateTime>33</gateTime>
          </Articulation>

Which is especially painful as it has to be done per instrument (to be clear, it's good that level of control is available, but painful when you want to apply it to all 30 or so!)

Prior art

No response

Additional context

In fact I have a far bigger concern, which is that from the testing I just did, MS4 seems to be ignoring this completely. Indeed the only code that seems to look at these gateTimes etc. is in the MIDI export code (compatmidirender.cpp).

It appears the plan is to replace this with "articulations profiles" that can be edited etc. Which is fine provided a) the articulation profile info can be stored with the .mscz file itself and b) is used for both MIDI export and playback (and c), where possible, that it work for Muse Sounds as well as regular sound fonts such as MS Basic). If there's already an issue that captures the intention behind that feature then this can be closed (and if community assistance would be useful for working on it, I'm happy to put up my hand).

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 reviewing compatmidirender.cpp and the mscx Articulation fields shown in the issue, then trace the proposed articulation-profiles work. Done means defining a UI for changing gate times and default velocities across articulations, with the values stored in .mscz and applied consistently to MIDI export, playback, Muse Sounds, and sound fonts.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.