Tying chords extends a couple of the ties far too long

• Jul 6, 2017 - 23:41
Reported version
2.1
Type
Functional
Severity
S5 - Suggestion
Status
by design
Project

When I try to tie chords together using the Shift+= shortcut, this happens:
http://i.imgur.com/27ZUA40.gifv

EDIT: I realise that, at least in my particular case, there is a workaround one can do simply by inputting each note as a dotted whole note. However, I reckon this shouldn't be another case of jumping through hoops to get somewhere.

EDIT 2: I isolated the issue: the chord ties correctly if you select only the first two sections of it. Changed priority to minor for this reason. Example:
http://i.imgur.com/e1lzbH9.gifv


Comments

That is not really a bug. You are telling MuseScore to tie the last chord to the next notes with the same pitch, so it dutifully complies. In your case you need to select only the first 2 chords and press + to make the proper ties. I would prefer MuseScore to do what you expect: look at the next beat and see if it can tie any of the notes to it, and if not, do not make a tie. If only some can be tied to the next beat, then tie only those. Perhaps this should be a feature request rather than a bug report.

As I've been messing with it more I see what you're on about and I do like the way it functions. However, if you look at my original gif, the ties that are looking for the next available note to tie to end up not finding their way across entire lines and instead only get about halfway through a line before just jumping to the next one. That doesn't seem right to me.

I see what you mean about the ties going part way through the line. It looks like on each line, the slur goes as far as it will on the destination line. Sine there Since there is no B natural in the rest of the song, there is no tie for that note.

I don't see any of the programmers posting anything now. They're probably all asleep in Europe right now. Wait for them to wake up and give there opinions on what to do with this.