Able to tie fret marks on different strings of the same note
1. Open attached score (produced in 2.0 beta).
2. Click on the first fret mark.
3. 'Tie'.
Expected result: Tie isn't applied.
Actual result: Tie is applied.
Using MuseScore 2.0 Nightly Build 2a67602 - Mac 10.7.5.
Attachment | Size |
---|---|
Able to tie fret marks on different strings of the same note.mscz | 1.73 KB |
Able to tie fret marks on different strings of the same note.png | 11.29 KB |
Comments
Sounds like a feature to me. Changing positions / fingering while a note sounds is not that uncommon a musical device. Is there an actual reason to deprive people of this useful ability?
I forgot about this and filed another: #165851: Fret value extends to different string
Could be wrong, but I don't recall seeing this in published material.
It seems odd to tie to something that hasn't been 'plucked'. In any case, it's a nuisance for me when inputting.
I have several at time contradictory thoughts on this
1. I would tend to agree with chen lung that this "feature" is meaningless ink on the paper. It tells the musician to move his finger to another string with no sound being made, if anything it will kill the sound already ringing.
2. A guitar player seeing this would interpret it as a slur rather than a tie and pluck the unison note on the other string. In this case, MS is playing this back improperly.
3. I don't see how this would affect the entry of the score. If you enter the 2 notes tied and move a note to the other string, both notes move. If you enter the 2 notes on the appropriates strings as in your example and don't want them tied, why did you enter a tie in the first place? How does this affect your note entry unless you are making a mistake that you would have had to fix if the "feature" didn't exist.
I'm just trying to figure out if this is a feature or a bug.
To me it's a feature that you *can* tie notes together on different frets, much as you *can* tie notes of different voices or of different enharmonic spellings together. It's a bug that this happens automatically if you lengthen a note across the barline. That is, the steps presented in this thread are not a bug. The steps in #165851: Fret value extends to different string are a bug; this one is not.