Hi,
I knew something had changed.
I play in a duo with backtracks and use pro files to play either keyboard or guitar to accompany.
All songs were setup a year or two ago with the key set to match the backtracks.
When the dancing season restarted in September after being off during summer,
many or maybe most of my songs appeared in the wrong key.
This is very embarrassing when you start a song and start to play in the wrong key.
Sometimes you notice and go right to the new key transposing the song in MS on the fly if you can,
or just do it in your head. But sometimes you have to stop to transpose and restart;
NOT GOOD!!! I am playing live...
For a year or two now, I have been gradually transforming from pdf to pro files,
following directives to the letter, even including all {eov}, {eop} and {Capo:#} as well.
It's a lot of work, but that is the main reason for going to pro files, isn't it?
However, the {Key:#} directive was worth it for me in the long run if transposing
on guitar is eventually needed when playing in other ensembles, even if I haven't ever used it.
In the past, there was no need for me to use capo as the key was already set from the beginning.
Now, I still haven't figured out how to turn this off, but a lot of damage has been done,
in the sense that the songs that I have since transposed will again be in a wrong key
if the capo setting is changed to the way it was before, i.e. not using the capo setting at all.
I knew it was necessary for me to check here to see what had changed,
but life got in the way until now.
Even reading your posts, I still can't figure out how to get MS to ignore the capo directive
until I need it. So please,
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?
Sincerely,
Dan
I knew something had changed.
I play in a duo with backtracks and use pro files to play either keyboard or guitar to accompany.
All songs were setup a year or two ago with the key set to match the backtracks.
When the dancing season restarted in September after being off during summer,
many or maybe most of my songs appeared in the wrong key.
This is very embarrassing when you start a song and start to play in the wrong key.
Sometimes you notice and go right to the new key transposing the song in MS on the fly if you can,
or just do it in your head. But sometimes you have to stop to transpose and restart;
NOT GOOD!!! I am playing live...
For a year or two now, I have been gradually transforming from pdf to pro files,
following directives to the letter, even including all {eov}, {eop} and {Capo:#} as well.
It's a lot of work, but that is the main reason for going to pro files, isn't it?
However, the {Key:#} directive was worth it for me in the long run if transposing
on guitar is eventually needed when playing in other ensembles, even if I haven't ever used it.
In the past, there was no need for me to use capo as the key was already set from the beginning.
Now, I still haven't figured out how to turn this off, but a lot of damage has been done,
in the sense that the songs that I have since transposed will again be in a wrong key
if the capo setting is changed to the way it was before, i.e. not using the capo setting at all.
I knew it was necessary for me to check here to see what had changed,
but life got in the way until now.
Even reading your posts, I still can't figure out how to get MS to ignore the capo directive
until I need it. So please,
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?
Sincerely,
Dan