You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I have been studying guitar for more than 30 years. I've never encountered a publication that uses slashes on stems for tablature. I've raised this issue in MS3 but it still persists in MS4. Slashes on stems indicate tremolo. While there is no single standard for indicating half notes, dotted half notes, etc in tablature, there's generally something that echos what the rhythm looks like in standard notation. For example, if it's a half note, there's some sort of oval or round shape around the number to indicate this. I've attached screenshots showing my workflow to workaround this. My graphics certainly aren't perfect, but they're better than having tremolo slashes on the stems.
Here's the line after I elongated the stems in the tablature:
After converting the half notes to quarter notes and making the rests invisible, I added the graphic I made to the tablature:
With the eventual hope to have it look something like this, without the standard notation (this makes it universal to all ukuleles).
But now with the parenthesis around the notes in the last measure, my graphic would look silly on top of that to indicate a dotted half note.
I don't know if it's ok to post pictures from copyrighted publications I have but I can provide examples from Hal Leonard and Mel Bay books if you'd like. Virtually any guitar book that Hal Leonard has with tablature will use something like what I've created. Again, I've never seen the slashes on the stems like MuseScore implements. The closest thing would be lute tablature, but that's covered in a separate section of MS of course. And you wouldn't have slashes to indicate longer notes.
Let me know how I can be of assistance. Thank you.
The text was updated successfully, but these errors were encountered:
@GrayCatMusic I agree that slashes is not a good approach for whole and half notes, but there's a question how it should be implemented.
We briefly discussed this point a year ago but it definitely needs a new design and implementation. It will fit to guitar release.
FYI @bkunda Probable, it's time to create separate project for guitar release
Hello,
I have been studying guitar for more than 30 years. I've never encountered a publication that uses slashes on stems for tablature. I've raised this issue in MS3 but it still persists in MS4. Slashes on stems indicate tremolo. While there is no single standard for indicating half notes, dotted half notes, etc in tablature, there's generally something that echos what the rhythm looks like in standard notation. For example, if it's a half note, there's some sort of oval or round shape around the number to indicate this. I've attached screenshots showing my workflow to workaround this. My graphics certainly aren't perfect, but they're better than having tremolo slashes on the stems.
Here's the line after I elongated the stems in the tablature:
After converting the half notes to quarter notes and making the rests invisible, I added the graphic I made to the tablature:
With the eventual hope to have it look something like this, without the standard notation (this makes it universal to all ukuleles).
But now with the parenthesis around the notes in the last measure, my graphic would look silly on top of that to indicate a dotted half note.
I don't know if it's ok to post pictures from copyrighted publications I have but I can provide examples from Hal Leonard and Mel Bay books if you'd like. Virtually any guitar book that Hal Leonard has with tablature will use something like what I've created. Again, I've never seen the slashes on the stems like MuseScore implements. The closest thing would be lute tablature, but that's covered in a separate section of MS of course. And you wouldn't have slashes to indicate longer notes.
Let me know how I can be of assistance. Thank you.
The text was updated successfully, but these errors were encountered: