Hello,
is there a way to transpose a chord progression into another key? I didn't get it. And: Is there a way to find out in what key the predefined chord progressions are intended to be used? It is obvious for progressions with names like "Rock in D minor". But what about the progression called "Jazz Blues" for example?
Thank you.
Transposing chord progressions
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- 6014 posts since 9 Jan, 2010
Hello,
no, it is not possible to transpose the chords on the master track. This is badly missing. In version 2, you will be able to assign chords and progressions with roman numeral chord notation, so everything will be much easier.
Regards,
Attila
no, it is not possible to transpose the chords on the master track. This is badly missing. In version 2, you will be able to assign chords and progressions with roman numeral chord notation, so everything will be much easier.
Regards,
Attila
-
- KVRist
- Topic Starter
- 70 posts since 24 Nov, 2011
Thank you for the answer.
Just some additional thoughts from my side:
While it will certainly be a good option to have the possibility to enter chords and progressions in roman numeral chord notation (because it will introduce relative chord notation just like it is already there for the phrases), I'm not sure that this solution will meet the needs of all.
For example: If I want to enter the chord progression of an existing song and transpose it into another key with the help of Rapid Composer, then I usually don't have a notation in roman numerals. What I find in songbooks are probably chords in direct notation (such as "Dbsus2"). Of course I could translate that into the roman numeral notation (if I know the key of the song), but I feel that such kind of mental arithmetics an intelligent composing software should do for me.
I think the problem at the current concept of RC (you may correct me, if I'm wrong), is that the progressions are not internally connected to a key. And because RC does not know the original key of an progression, it can not transpose it into a different key. Therefore, a solid solution of the problem would require to introduce the relation between keys and chord progressions into the software.
Meanwhile, the software at least could offer a feature to transpose chord progressions in semitones up and down (for example: C-Dminor-F >> 2 semitones up >> D-Eminor-G). Should be relatively easy to implement. Then the user can do the desired transposition at least if he knows the original key (and of course has some basic musical knowledge).
Anyway, I'm looking forward to V2 with impatience
Just some additional thoughts from my side:
While it will certainly be a good option to have the possibility to enter chords and progressions in roman numeral chord notation (because it will introduce relative chord notation just like it is already there for the phrases), I'm not sure that this solution will meet the needs of all.
For example: If I want to enter the chord progression of an existing song and transpose it into another key with the help of Rapid Composer, then I usually don't have a notation in roman numerals. What I find in songbooks are probably chords in direct notation (such as "Dbsus2"). Of course I could translate that into the roman numeral notation (if I know the key of the song), but I feel that such kind of mental arithmetics an intelligent composing software should do for me.
I think the problem at the current concept of RC (you may correct me, if I'm wrong), is that the progressions are not internally connected to a key. And because RC does not know the original key of an progression, it can not transpose it into a different key. Therefore, a solid solution of the problem would require to introduce the relation between keys and chord progressions into the software.
Meanwhile, the software at least could offer a feature to transpose chord progressions in semitones up and down (for example: C-Dminor-F >> 2 semitones up >> D-Eminor-G). Should be relatively easy to implement. Then the user can do the desired transposition at least if he knows the original key (and of course has some basic musical knowledge).
Anyway, I'm looking forward to V2 with impatience
