musescore / musescore/MuseScore

Ties should be easy to enter in "input by duration mode"

Open
#27,235 8 comments 12 reactions 1 assignee View on GitHub

@bkunda is already working on this.

Since Mar 25, 2025.

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

Description

Your idea

Currently ties are very easy to enter in the standard input by pitch mode: select duration, press "T" (or click toolbar button). If there is an equally easy way to do it in input by duration mode, I haven't found it, and the (new) Handbook doesn't discuss this.

The basic issue, of course, is that selecting the duration enters the note already, so it seems too late for the "T" command to do that. One "obvious" solution would be for the tie command to act retroactively while in input by duration mode - apply a tie backwards from the just-entered note. But that's actually pretty awkward if you think through the different cases, like what happens if the note you just entered isn't the same pitch as the note before, or what happens when pressing "T" after navigating backwards. Maybe a better answer is that the tie command should work more like the rest command: setting input state for the next note. So the sequence to tie to an eighth note would be T 4.

Other solutions are possible as well, of course.

Also, note that the same applies to the old "rhythm only" mode - see https://github.com/musescore/MuseScore/issues/14777.

Problem to be solved

Entering a tie in "input by duration" mode is inordinately difficult.

Prior art

Since the idea behind this mode is borrowed from Finale, we should consider borrowing their tie behavior too, assuming they have a good solution.

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.