Addition of a small section of TAB clef
I'm finishing up my first real Musescore Project, sketching out some parts of an old MoTown song. I'd like to show the guitar player how I want an A flat cord riff played up on fret 12 and 13, just the top two strings. I could show the fingering and rhythm easily in Tab clef, but I currently have parts for sax, bass, and guitar with guitar on a standard clef with just chord names and slash heads. So what's possible? Can I add a short piece of TAB clef on just a four bar line? Or can I insert a short piece of Tab somewhere outside the main body of the song, like at the top of the page, designate it as guitar fig. 1, then add some text in the appropriate measures in the song calling for guitar fig. 1?
Comments
add a TAB staff, fill it where required
and use menu
Style>Global style>Score>Hide empty staves
(not sure of the exact terms, since I use french ones)
In reply to add a TAB staff, fill it by robert leleu
Like the idea. I added a new Instrument staff for guitar, replaced the treble clef symbol with the tab, edited the staff properties to make a 6 line staff, but the note entry isn't working for me. I just get notes, not little numbers. I'm trying to follow the handbook at http://musescore.org/en/node/7845 but something isn't working. Under the handbook heading "By changing staff type" I'm not seeing step three "In the "Type:" drop list, select "Tab"' in my staff properties window. I'm using Musescore 1.2.
The Create Instruments window shows the second guitar under the first guitar and the clef is set to tablature.
In reply to LIke it, but by MajorGeek
So is all this Tablature stuff only available in Nightlies? I haven't been able to get it to work at all.
In reply to So is all this Tablature by MajorGeek
Yes, proper tablature is only available in the forthcoming version :).
What do you have problems with?
In reply to Yes, proper tablature is only by chen lung
Thanks, got a Nightly and got it to work. However, now my chord names that were Ab7 are now A little box 7. But I'm making progress.
In reply to Thanks, got a Nightly and got by MajorGeek
Great!
I think I noticed the problem with the chord names too, but hadn't filed anything in the Issue Tracker - will do that soon if no-one else does.
Just remember that it's only intended for testers and advanced users, so be cautious ;).
In reply to Thanks, got a Nightly and got by MajorGeek
I kmow the fonts used by MuseScore are in transition between 1.x and 2.0 - the flat and sharp signs are moving from their old locations in the character set to the Unicode stamdard locations. I think there is supposed to be some sort of code that converts older files to use the new Unicode symbols, but that might not be hooked up yet. Do a search for "unicode" on these forums or the issue tracker and you'll probably find more info on the status of this.
In reply to I kmow the fonts used by by Marc Sabatella
My only remaining problem with my project is the missing flat signs on the chords. I searched on unicode, but couldn't find anything that would help me fix this.
In reply to My only remaining problem by MajorGeek
Oh, I didn't say anything about letting you fix it. I said it should turn up more information about the issue itself. For instance, see:
http://musescore.org/en/node/17748
But I don't you can do anything ablut it - you have to wait for the developers to finish implementing all this (unless you are a programmer and help implement it yourself). You have to realize, 2.0 is not released yet. It's still under development,.. So while you can try out experimental nightly builds for fun, or to provide feedback, you shouldn't be expecting them to actually work. If you are trying to actually do real work, you should stick to 1.2.
In reply to Oh, I didn't say anything by Marc Sabatella
OK, but I went to nightlies just so I could write one line of tablature to more clearly show the guitar player how a rhythm figure goes. Now I don't know if I can roll back.
In reply to OK, but I went to nightlies by MajorGeek
Probably not on that score. You can try exporting to MusicXML and then importing into 1.2, but I suspect the tab would not convert very well. so you'll probably have to finish this in 2.0 From the information in the Unicode thread I mentioned, I'd guess that if you deleted the chord symbols and re-entered them, the font issue would correct itself, and you could complete this chart. But for future pieces, you'd probably be better off sticking to 1.2 until 2.0 is more stable.