[jlgtx]

1- How do I get MS to ignore the capo setting in pro files?
2- Any suggestions to get me out of this predicament would be appreciated.
3- Should I delete all {Key:#} directives in all pro files?

It is all a bit confusing, between the transpose, capo, modulate down, etc.

Here's the simple skinny:

-- When creating a ChordPro file, the only time you should add a {capo} directive is if the {key} in the file, as typed, is the capo key, not the original key -- and, in any case, the {key} directive should always match the chords that are typed. IOW if the song is in E but you type up the CP file using D chords, then you should add {key: D} and {capo: 2} directives, but if you type up the CP file using E chords, use {key: E} and no capo directive. This is how it should be done, according to the ChordPro documentation (linked earlier in this thread).

-- My understanding is that MobileSheets only looks at the {capo} directive when importing the ChordPro. For songs already in the database, you shouldn't have seen any effect. (Mike can correct me if I'm wrong here!)

-- Once the song is in MobileSheets, display the song, and then open the Text Display Settings pane (touch the "A" at the top right corner). Configure your capo there. Notice the "eye" to the right of the capo setting slider. That "eye" tells MobileSheets whether to display the original chords in the CP file (eye un-checked, or white), or to transpose the chords down by the capo interval (eye checked, or orange). As of 3.8.19, the default behavior, when MS imports a CP file with a capo directive, is to set the MS capo interval to match the directive (so you'll see "Capo: 2" displayed on the sheet**), and un-check the eye -- because the actual chords in the CP file should be in the capo key, not the original key, so they should be displayed as-typed.

-- If you imported a CP with a non-standard combination of {key} and {capo} directives (e.g. the {key} is original, and you added a {capo} directive because you planned on using a capo), you can fix the display to your liking using the capo config settings above, by simply checking the eye (make it orange). If you typed it up with mismatched {key} directive and chords, I'm actually not sure how MS processes that. I would probably bow to my OCD muse by standardizing the original CP and re-importing it, to save myself confusion down the road.


** assuming "Show capo on score" is enabled in the Capo display settings