Add "standard" representation of key, tuning and capo information to tab

• Sep 24, 2014 - 14:53
Type
Functional
Severity
S5 - Suggestion
Status
closed
Regression
No
Workaround
No
Project

Regular music notation uses a clef and key signature and there is no way anyone would remove them and require the user to add text to the top of the score providing the same info. In tablature, the same function is performed by tuning and capo information which is missing from the score in Musescore 2.0 beta 1.

There is no standard in tablature to provide tuning and capo info. The most common method is to type in some random text somewhere at the top like: "Key of A, Standard G tuning( gDGBD), capo 2". However, every tab needs this info so it should be standardized.

I would recommend putting this info just before the first measure for each part. You should be able to select it somehow (double click) and be taken directly to the tuning dialog (which already exists). At a minimum, the string tunings should appear on the main score, first measure. Recommended keys (i.e. capo positions) can be added as random text.


Comments

Is it MuseScore's job to standardize this, though? As you say, every score does it differently, and one way or another, MuseScore supports most of the ways someone might come up with. Seems maybe we should wait for a standard to actually develop and then implement that, rather than invent our own.

Here's a thread where different ideas for this have been discussed:

http://musescore.org/en/node/23144

Again, leaving it out is like leaving out the clef/key signature from regular notation. The tuning defines the meaning of the staff lines. It affects every note in the part.

Perhaps it's too late to fix the slur/chord issue, the hammeron/pulloff/slide markings and tuning info in version 2.0. Please consider them for the next release.

I plan on adding a lot of banjo tunes to your archive once 2.0 is released -- that's why I'm pushing for these changes. To me they are not options -- they have to be there or us banjo players are going to revolt and declare a jihad against your tab implementation :-)

Just kidding -- I love what you're doing with Musescore. It's a great product.

:-) Well, again, there is a universal, centuries-old standard for how clef and key info is represented on a standard staff. So of course MsueScore supports the universal standard there. The problem is there is no such standard for tab - not for key (which is entirely superfluous info for tab anyhow), not for string tuning, not for capo (which MuseScore doesn't actually support well - a bigger issue, i think). So I think it would be presumptuous of MuseScore to force people to have their scores represented with any particular non-standard representation. Even if we made it optional, there should be more discussion over the "right: way to do it - or maybe we offer options. But again, since you can create appropriate markings manually now, that seems more than fine until standards start to emerge.

Status active closed
Regression No
Workaround No

I might be wrong but just reading the discussion, I feel like this issue should already be closed.