Friday, August 19, 2011

Changing Music Score Key while Saving Your Music: MIDI ONLY

Have you ever created a studio project in Garageband setting the key and tempo along with the filename, then played a fantastic track.... and THEN realized that you set the project for the wrong key? Result: Your music score may have so many sharps or flats in it that only a college music major would want to try it. This hint shows -- it's NOT too late to fix your score!....

....even though the GarageBand program makes you think it is. After you've created a beautiful music track, if you look at the score (fancy GB wording: in the Notation View), you CANNOT simply change the GB key. Changing the tempo or signature there keeps all notes the same, but if you change the key, GarageBand transposes all your music to that key.

For projects with only MIDI tracks (hence ability to create score):
EASY FIX so that the score's signature shows the key you want but your recorded music won't change:
1. SAVE your project. Just in case you want to revert to the existing file :)
2. TIGHTEN your view (the slider under the top window) so you can see all or most of your track. (It also helps to do a Track > Hide Track Info for long tracks. If in the Loop Browser, first Track > Show Track Info.... another of those weird hints not in all instruction guides.)
3. Select the entire track (dark green... the track, NOT the notes in the track). and CUT.
Hey, now you understand that suggestion to first Save!
4. Select Control > Show Tempo (if you're not already there).
5. Change the Key to whatever you like.
6. Hit HOME to put the red marker at Measure 1 count 001.
7. Ensure that the correct track name is highlighted. Then do Edit > Paste.

Your original track will be pasted in exactly as it was.... NO transposition done after you changed the key. Now when you check the score, it most likely looks a lot easier to play!
Much joy to you in defeating those little quirks in GarageBand!
©2018, 2011 DianaDee Osborne
An updated version published 20 February 2011
Updated version published   16 February 2018

1 comment: