F double sharp?
Notice the difference in the first note of each measure.
The pitch is the same (and correct) in each but the notation difference
4th string/5th fret gives F double sharp
3rd string open gives G natural
Why is Musescore doing this?
Is the how notation from guitar is done?
| Attachment | Size |
|---|---|
| xF.mscz | 5.11 KB |
Comments
Is there something wrong with that?
In reply to Is there something wrong… by Jm6stringer
Not necessarily. Though I would prefer that 4th string/5th fret just be G.
Unless there's a reason with respect to music theory that it should be F##
In reply to Not necessarily. Though I… by allelopath
You wrote:
Though I would prefer that 4th string/5th fret just be G.
OK...So click on the '5' in the TAB staff and press Ctrl + up arrow.
You wrote:
Unless there's a reason with respect to music theory that it should be F##
No more reason than why the treble clef staff shows an F## in measure 1 and then a G in measure 2.
Yes, there are reasons why it can be more correct to notate a given pitch as Fx instead of G. Most obviously, when writing in G# minor, the leading tone absolutely should be spelled Fx. Another more subjective case could be, when writing an ascending chromatic line between F# and G# in any key that includes both F# and G# in the key signature.
As for why it is spelled that way in this instance, it must be that whoever created this score - apparently some years ago, or at least with a years-old version of MuseScore - must have used the "J" command, or perhaps the "respell pitches" command to change the enharmonic spelling. If you simply delete the "5" from the tab on the first beat then re-add it, you get G as expected. At least you do in the current version of MuseScore.
When looking at your attachment...
Theoretically, I see a sequence of note pairs (dyads) each spaced an interval of a 10th except for that very first F double sharp - which I, too, wonder why it should (deliberately) need to be Fx. Especially since this short example exhibits no overall tonality (e.g., key of G# minor).
"TABithetically", I see the sequence of dyads played strictly on the 1st and 4th strings except for beat one in measure 2. The question then arises: Why the open G string here and not the 5th fret of the 4th string?
Regardless, apparently you want the Fx in measure 1 -- "to just be G" .
Logically, though, your response: Though I would prefer that 4th string/5th fret just be G
![TAB_Fx.png]( "TAB_Fx.png")
...mixes TAB lingo ("4th string 5th fret") with musical notation terminology ("G").
Have a look:
However you choose to notate it, MuseScore can handle it.