Linked tablature staff fail / Wrong pitch in bass

• Feb 6, 2024 - 04:34

Don't know what happened to this score, but the linked tablature is not operative in bars 3 and 4. Also there's a pitch issue in Bar 4 with the bass on beats 1 and 3.

Here's the score for anyone who wants to help out by taking a look and reporting back.

       Linked TAB fail and wrong pitch_Partial Capo issue?.mscz

      Update: The reason for the blank tablature staff is that it is not linked to the treble staff.
      Which is odd, because I started with a score with linked tablature, noticed some odd behaviors
      and then simply deleted some measures to bring focus on the peculiarities.
    It seems that produced the result of an unlinked stave ...

Thanks in advance!



Is there some reason you are only doing a partial capo? When I capo all 6 strings everything seems fine. I can copy the notation into the tab. Although I copied the notation into a new score. But still had your issue until I did a full capo. The player would have to finger the 6th string, otherwise.

In reply to by bobjp

Regarding the Partial Capo

> Is there some reason you are only doing a partial capo?

Yes. I notated for partial capo because I arranged the piece for partial capo: 022222

Going forward in this post, when I refer to a chord or key, it is relative to the capo at the 2nd fret—for instance, a D chord or D bass note sounds E. Same goes for the key of D.


Due to partial capoing (022222) the guitar behaves as if tuned to Drop-D except for the fretted behavior of the 6th string. One benefit is that the root of G chords are fingered at fret 3 of string 6, ... as if the guitar is in standard tuning. Whereas, in Drop D tuning the G bass note is awkwardly located at the 5th fret, two frets higher than normal.

Net result of partial capo 022222:

    • the low G is easily accessible for the root of G chords and the 5th of C chords
    • the open 6th string provides a resounding deep root note for "D" chords
    • A consequence of the aforementioned is that the open 6th string is not longer the root of "E" chords.
      But ... that's not a problem for tunes with no Em chords.

So capo 022222 is great for the key of D and the key of G. (As mentioned, the most significant problems in the key of G are the Em or E chords.)

Regarding the linked tablature

When you said, "... everything seems fine" were you saying that you see tablature on line 2? That's my concern. Something happened at measure 3 causing the tablature staff to become empty from that point on. I've never seen that before, but I haven't done much tablature work in MuseScore 4.

Here's what I see:

Linked TAB fail.png

In reply to by scorster

Did you retune string 6? I see you lowered the usable range to D2. But you didn't edit the string data to retune string six. Regardless, the partial capo should take care of that without retuning anything.
As far as the first two notes of your tab go, call me crazy, I'm not sure that MU4 should call an open string 6, a D.
Or the next note. String 4, capo 2, should be called an E. At least it plays back as such.
This why I don't write tab. It gives me a headache.

In reply to by bobjp

I know these matters are challenging to grasp, but they are the nature and bounty of partial capo techniques. As we know, guitar is a transposing instrument ... and a guitar with a capo or partial capo even more so.

No headache here. And no need that you engage in discussions that provoke any for you.

My main concerns the issues thatt appear to be MuseScore glitches:

    • The linked staff conking out. (You've never stated if you see that. I'd appreciate knowing.) Anyone?

    • The difference in pitch of bass notes written on the same staff line, as described above

I only need to know if anyone can confirm the these two points. All else is good—other than the frets written only relative to the nut, which is an open P2 Github issue.


In reply to by scorster

When I copy your notation into a new score, all four measures are copyable into a tab staff. In your score the tab bass notes don't play the correct pitch. Same with the whole tab staff in the attached.
We can't have much idea as to why the last two bass notes are incorrect in your score. We don't know how you created it.
It seems to me that if you suspected a procedural problem, redoing the entire section would be the way to go. Rather than building on potential problem.
Given all the problems you call out about being possible capo instigated, Is it really worth it. Yes you've gone into detail about it. But still. I don't believe guitar being a transposing instrument has anything to do with it.
You are looking for specific things, but I think there is more goin on.

Attachment Size
tab s.mscz 30.93 KB

In reply to by bobjp

Sorry, I can't fully parse your post ...

But it sounds like you've confirmed that the bass notes on beats 1 and 3 of measure 4 produce a different pitch from notes residing on the same staff line in other measures. Correct?

I don't need advice on recreating or copying measures out of the score. I've already done so. My questions are about the appearance and behavior existing score I attached to the original post. I'm not looking for advice on repairing it. I hope we can stay on topic with that.

To see if the issue is specific to my system/configuration I merely want to know:

• if in the attached score anyone hears the pitch discrepancy (cited above, cited here in previous posts, and cited with red tesxt in the score itself. (Sounds like you did hear that.)

• if anyone sees an empty tablature staff on line two. That would be quite odd as the staves are linked. But I'm seeing a number of link/sync issues with linked tablature. Update: The staff issue turns out to be an unlinked staff, which is surprising—as expressed in the updated opening post. Sorry for the bum steer!


Do you still have an unanswered question? Please log in first to post your question.