Notes tied over other measures

• Feb 7, 2016 - 08:36
Type
Functional
Severity
S4 - Minor
Status
by design
Project

Tieing notes causes other notes played later with the same pitch to be tied, which in turn causes these notes to be inaudible. For example: C in measure 1, C in measure 2, D in measure 3, C in measure 4. Tieing the C's in measures 1 and 2 causes the C in measure 4 to also be tied to these two notes, leaving the C in measure 4 basically inaudible.

GIT commit: f51dc11

Attachment Size
Untitled.pdf 27.76 KB

Comments

You PDF shows clearly that you've also tied the notes from measure 2 and measure 4. Doing that is explicitly asking that the C from measure 4 won't be played.

This specific way of notation is one I haven't seen before. I know tying across other notes exists from broken build-up chords in romantic music, but this is new to me.
Do you have a real use-case for this notation in which measure 2 and 4 need to be tied? If it comes from a printed score, are you sure those notes aren't slurred instead?

I am guressing maybe you made the mistake of selecting both the C's in measures 1 & 2 before hitting the tie button. That's not the proper way to tie two notes. Instead, you are suppsoed to just select the *first* note, and MuseScore automatically figures out what to tie it to. That is, the button says, "start a tie here". If you select two notes before hitting the tie button, MuseScore will try to start a tie at all of the selected notes. So MuseScore did exactly what it was designed to do.

That's very interesting indeed. I have wondered for a while why everytime I added an editorial tie to a score the program extended the tie to the next note on the same pitch. It never occurred to me that I should only select the FIRST note of the pair to be tied. You've made MuseScore 'smarter' than I expected it to be.