Overlapping noteheads in two voices - a TAB issue
Please refer to the attached file, a guitar arrangement in staff/Tab.
There is an issue with overlapping noteheads in two voices in treble/Tab notation. When the overlapping notes are translated into Tab they appear, incorrectly, as notes on separate strings and there appears to be no way to correct this.
e.g. Go to the tab staff, bar 6, third note along, an A shared notehead. This has been translated incorrectly onto two strings but there seems to be no way to move the note on the 6th string to its correct position on the open 5th string. This problem is also apparent on the first note in the bar which is shaded red: the reason for this, I think, is because the note in voice 2 still exists but cannot be placed on any of the displayed strings.
MuseScore needs to allow the user to merge both notes on one string. And prevent notes in voice 2 disappearing below the lowest string!
| Attachment | Size |
|---|---|
| Golliwog's Cakewalk.mscz | 33.46 KB |
Comments
Unless I'm mistaken, this had been fixed very recently.
Hmm, wrong, but close, see #60651: Fret conflict shouldn't be exported to PDF or printed
In reply to Unless I'm mistaken, this had by Jojo-Schmitz
1) "Go to the tab staff, bar 6, third note along, an A shared notehead. This has been translated ) incorrectly onto two strings but there seems to be no way to move the note on the 6th string to its correct position on the open 5th string."
It seems that you discover MuseScore. A learning curve is necessary and understandable ;-)
Why do you write" translated incorrectly" ?
In this situation, the open 5th string, indeed, is necessary.
But this would not be the case in another situation if, for example, the writing imposed was by starting in fret VII.
This means you have the choice. Nothing is imposed. Good, right?
In this case, simply hide the number 7 (for the A), eg via the "V" key. If several notes are involved, you have simply to select them with the Ctrl key and then press the V key .
Finally, if you don't want see the grayed numbers on the score, just uncheck in View -> "Show Invisible".
2) For this: " also apparent on the first note in the bar which is shaded red"
please read this thread: https://musescore.org/en/node/60411
Try this:
1. Create an additional TAB staff, but *unlinked*.
2. Copy/paste the linked TAB staff into it.
3. Select and delete all the unnecessary notes on the *unlinked* TAB staff. This action won't be propagated onto the treble staff (unlike the linked TAB).
4. When finished, use menu item: Edit / Instruments, where you can remove the linked TAB staff.
See the bottom staff in the attachment. It's an *unlinked* TAB staff.
Regards.
Hiding the extraneous tab note is the obvious solution but it does leave a greyed-out remnant. And since shared noteheads are extremely common in all fingerstyle music there would be a lot of hidden notes to deal with – and a lot of extra visual clutter. And then there is that problem (if it is a problem) where one of the notes has "disappeared" off the bottom edge of the TAB.
I wonder if another possibility is for the user to be able to move one of the notes onto the same string as the other so that it overlaps and reads the same. If I remember correctly, this is the approach adopted by Finale and it has the merit of retaining both notes on the TAB without adding unecessary clutter to the score.
I haven't looked at jm6stringer's new score, but I tried copying and pasting from staff to Tab before (with unlinked staff and Tab) and it gave some very strange results. Is cutting and pasting from staff to Tab an official design feature?
In reply to Hiding the extraneous tab by geetar
"Hiding the extraneous tab note is the obvious solution but it does leave a greyed-out remnant." Please, read entirely the replies :)
For eliminate, as you said, the "greyed-out remnant": View ->Untick "Show invisible"
In reply to "Hiding the extraneous tab by cadiz1
And they won't print, nor export to PDF anyway.
In reply to And they won't print, nor by Jojo-Schmitz
" And since shared noteheads are extremely common in all fingerstyle music there would be a lot of hidden notes to deal with – and a lot of extra visual clutter. "
The shared noteheads are common, true. But your sentence is marked by a preconceived idea. You tend to raise this question because you're used to something else ...
I am a professional guitarist, I use tabs with MuseScore for a year, I input a few hundred scores with tabs (so, I made the operations that you described x times), and I can tell you that after a time of learning, you will quickly understand the benefits of using MuseScore instead Finale! I take the bets...
" And then there is that problem (if it is a problem) where one of the notes has "disappeared" off the bottom edge of the TAB." Don't understand? Could you develop this, and give an example in a score.
"but I tried copying and pasting from staff to Tab before (with unlinked staff and Tab) and it gave some very strange results. Is cutting and pasting from staff to Tab an official design feature?"
Yes, copy-past from staff to Tab it's a official feature! :) If you enconter difficulties, attach please the score to show where is the issue.
In reply to " And since shared noteheads by cadiz1
For this: "but I tried copying and pasting from staff to Tab before (with unlinked staff and Tab) and it gave some very strange results".
After thinking, I suspect that you have forgotten, for the added Tab staff, to go - before copying-pasting - in Staff Properties -> String Data -> and edit the pitch of some strings, since you have chosen an atypic, or custom tuning for this piece (D2/A2/D3/G3/A3/D4), right?
The bottom D string in Tab is marked red. This indicates, as far as I know, that a note is "out of range", but since I have set the note range to accomodate the lowest note this shouldn't be happening. Two voices cannot share the same string in MuseScore so it seems that voice 2 has been omitted.
However, am I right in assuming that this fret colouration issue has been fixed and won't appear in future versions of MuseScore? Or should this issue be reported?
In reply to The bottom D string in Tab is by geetar
The red marking marks a fret conflict, not a note out of range
Does this mean the red-mark issue will definately be fixed in the next update?
In reply to Does this mean the red-mark by geetar
It won't get exported into PDF