musescore / musescore/MuseScore

Introduce more options for styling tremolos between notes

Open
#33,793 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Currently the appearance of tremolos between notes (two-note tremolos) may only be changed for half-note tremolos. This is by design, to avoid potential rhythmic ambiguity (e.g. a beamed quarter-note tremolo looks exactly like an eighth-note tremolo - although durations are often made clear by context).

There are, however, situations where you might want to allow changing appearance of tremolos of any duration, e.g. if you need to accurately reproduce a source. We should provide options that allow this.

Also we should provide options for setting tremolo beam style globally, rather than only allowing overrides for individual tremolos beams.

Problem to be solved

Add a new section to Style > Beams: Tremolo beams - see mockup (@avvvvve, this needs copy and design).

Image
  • Add Auto to tremolos Style property. (Should be Auto by default)
    • Half-note tremolos:
      • Auto is wired up to the Half-note tremolos option in the Style dialog
      • Overrides to individual tremolo beams are always allowed
    • Tremolos of shorter than half-note duration:
      • Auto is wired up to the Style (between notes) of shorter duration option in the Style dialog
      • When Allow beams for tremolos of any duration is unchecked (default), the Style properties should be grayed out. They are active only when Allow beams for tremolos of any duration is checked.
        • Note however that any overrides set for individual tremolo beams should not be lost when toggling Allow beams for tremolos of any duration.
    • Tremolos with duration whole-note and above:
      • Overrides to individual tremolo beams are never allowed. The Style properties should always be disabled.
Image

(In the properties panel, add Auto before the first of these options)

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.