11-07-2016, 07:04 AM
There are more issues with keys and transposition, so I would advice to not make changes until there is time to rethink it.
For example, consider this (test) file:
When imported, MSPro only considers one key, the last one seen. So this piece will be registered as having the key of F.
When viewed, the chords read G A# F // G Bb F. Correct.
When transposed up one step and down one step, the chords read G Bb F // G Bb F.
I still haven't found a way to get the original chords again, except for song delete / re-import.
For example, consider this (test) file:
Code:
{title: Keys}
{key: G}
[G]This part [A#]is in the [F]key of G
{key: F}
[G]This part [Bb]is in the [F]key of F
When imported, MSPro only considers one key, the last one seen. So this piece will be registered as having the key of F.
When viewed, the chords read G A# F // G Bb F. Correct.
When transposed up one step and down one step, the chords read G Bb F // G Bb F.
I still haven't found a way to get the original chords again, except for song delete / re-import.
Johan
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).