What about Capo fret position?
If I understood reading this thread, #20512: Add capo support to tablature staff, the Capo function is not implemented.
Yet it is displayed in Style -> General -> Symbols Chords, Fretboard ... -> Capo.
To summarize: it is displayed but doesn't work at all.
For any other function, it would be a bug, right?
And so, the thread mentioned above, should move from a feature request status to be classified as " Bug report."
Or have I misunderstood something? Thanks.
| Attachment | Size |
|---|---|
| capo fret position.jpg | 16.22 KB |
Comments
Style -> General -> Chord symbols, Fretboard ... -> Capo is about "Chord symbols and Fretboard" not about tablature staff. If I remember correctly, it's used to display chord symbols based on the capo position.
In reply to Style -> General -> Chord by [DELETED] 5
Well, I do not understand how it works.
For example, I select two fretboard diagrams on the score (e.g, an E, and a G with barré) -> I change the value of Capo Fret position. -> Apply or / and OK
Result: nothing happens
Ditto, if I begin to change the value of Capo Fret, and continue by adding the diagrams.
What I forget?
In reply to Well, I do not understand how by cadiz1
It's used to display chord symbols between parenthesis.
Create a score, add a couple of chord symbols, go to style, general, etc... change the value of the capo.
In reply to It's used to display chord by [DELETED] 5
Yes, and to be clear - it has nothing to do with fret diagrams as far as I know. Only chord symbols.
In reply to Yes, and to be clear - it has by Marc Sabatella
Ok, I understand.
![chords.jpg]( "chords.jpg")
![Capo.jpg]( "Capo.jpg")
Enter chords and change the capo fret value (eg capo 2, the equivalent of a tone for guitar) adds a new chord between parenthesis: a chord thus a lower tone.
I'm curious (well, it's not very important) to know of that emanated this feature request. Personally, I will not use because I see any interest whatsoever if not useless. Oh well.
Thank you both for the explanations.
In reply to Ok, I understand. Enter by cadiz1
I think the idea is, wanting chords to display both as "sounding" and "written" is pretty common, and if MuseScore can calculate things for you so you only have to enter one set, why not?
In reply to I think the idea is, wanting by Marc Sabatella
Absolutely. As it is in v1.3, if you need to write a second set of chords to be used with a capo, your guitar chords write over your concert pitch chords and you have to move them yourself — very tricky, horrendously time-consuming. I would think parens above the concert pitch chords would be preferable to parens beside concert pitch; but at least some function appears to be implemented in v2. One decent step forward. Kudos.
In reply to Absolutely. As it is in v1.3, by km2002
If you want your capo chords written above, then I think the best way in 2.0 will be to enter them normally (or use copy/paste & transpose to generate them automatically - see below), then select them all and assign them a different text style. 2.0 allows you to define and apply text styles easily, so you could put them in a different font, italics say, and higher above the staff.
To get MuseScore to help you generate the chords, you could copy to a new staff, then use Notes / Tranpose to transpose that staff - hmm, even F2 / Shift+F2 would work well, and would be kind of cool because you'd just press it as many times as you want the capo position. Then apply the text style there, then copy them back to the original staff. Wouldn't take but half a minute to do the whole score.
In reply to If you want your capo chords by Marc Sabatella
Glad to see that this function is helpful to some.
For my part, after rereading the thread, I realize that I definitely do not understand a point.
If I play a D chord with Capo 2 of my instrument, I hear the chord a tone highest, ie a E chord, right?
So: when I write a D chord on the score, and then I change capo fret value (ie, 2) via Style -> General -> Chord symbols...,
I expect the result D(E): the written D chord + the E chord as it will be heard with a capo 2.
![D chord.jpg]( "D chord.jpg")
Currently, the calculation is reversed: the result is D(C)
![Chord D C.jpg]( "Chord D C.jpg")
In reply to Glad to see that this by cadiz1
That is the calculation I would expect: Input the concert pitch chord (without parentheses), get back the capoed chord (inside parentheses). As a guitarist, I expect the chord in parentheses to be what I play with a capo on the guitar, not the concert pitch of the chord I play with the capo. So for someone who isn't playing with a capo, they would, given your example, play a D chord; if you're playing with a capo at the second fret, you would play a C chord, because the capo, at the second fret, raises the pitch of the guitar a major second. It's the same thing as transposing for, say, a B♭ trumpet: You have to write a full step higher than concert because the instrument is pitched a full step lower than concert. If you put a capo on a guitar, you are raising its concert pitch; therefore, your chord symbol has to be lowered by the inverse interval.
In reply to That is the calculation I by km2002
Apparently we did not have the same understanding of this function (which I never use actually, or very little)
But I totally understand your point of view, and I understand now better your desire to see the guitar chords (in parentheses) write above the concert pitch chords: it is indeed a rather disturbing gymnastic to play a chord that is in the second position.
The misunderstanding on my part comes mainly from the fact that this function has exactly the same name (fret capo position) than Guitar Pro.
But it is quite different. With GP, it allows you to hear the playback of a score, for example written in C, so to hear it in D (with Capo 2) or in E (Capo 4). So it is the sound effect that is achieved with GP. It was the reason why my understanding was different from yours.
In reply to Apparently we did not have by cadiz1
Ah. And now I get your point of reference. I have to admit that at this point I haven't tried to run either of the V2 betas (I've had problems with all kinds of betas before; so I usually wait for the stable release); so I have no idea if there's even a playback of chords in MS 2. I know there isn't in MS1.3, which is what I'm using now. So if I stack up a D chord on a staff, it really doesn't matter what the guitar transposition is; MS will play a D chord.