MarkGuitar
I think the idea is very good! I do also have a FR in mind very similar.
### Personal capo position
Current Limitation / Use Case:

Guitarists often use a capo to play with open strings, which tends to favor the keys of E or A. Keyboard players, on the other hand, often prefer to avoid the black keys and favor the keys of C or G. Because of this, a bassist, a guitarist, and a keyboardist may end up with different transpositions for the same song. Keeping separate local copies of songs just for transposition purposes makes song management much more complicated.


Proposed Feature:

The capo function introduce the ability to have a personal/local transpose saved with the song. Guitarist can't use negative values, while keyboardists can.


Benefit / Impact:

Now we don't need to handle local/personal copies of songs any more and can easily stick to the network session song. That would ease the song management dramatically.


Implementation Idea (optional):

This is a personal "capo position" transpose.
 Add this value to the overall transpose/pitch when showing chords.
 
Create a map in the song with the connected client as key and the capo position as value.
When a connected client change the capo position it need to tell the host to save the capo position for that client.