Hi Frank, There's no better place to find the shortcuts than in the documents. forget the DVD—go to Applications>Digidesign>Documentation>Pro Tools and there you'll find the Pro Tools Shortcuts pdf. Actually, You can find it right in the help menu in Pro Tools.
A word about learning shortcuts… It certainly is nice to keep the pdf opened in the background while trying stuff in Pro Tools. I've never been in that position. When I learned Pro Tools, pdfs weren't at all accessible, neither in Windows nor the Mac. I exported pdfs to text files and kept my place easily. The other thing is that, when reading the "Getting Started" guide (which is now called something like "Intro to Pro Tools" or something like that), the keyboard shortcuts are always spelled out and, frankly, that's a better way, in my opinion, to learn the shortcuts… one at a time, slowly. My two cents. Slau On Nov 24, 2010, at 10:54 PM, Frank Carmickle wrote: > Hi list > > > On Nov 24, 2010, at 5:57 PM, Slau Halatyn wrote: > >> Hi Chris, >> >> Welcome to the list. Pro Tools is, in many ways, totally accessible but >> there are still areas that need improvement, some more urgent than others. >> I'll try to give an overview. >> Virtually all areas of audio recording and editing are accessible. Creating >> tracks, routing input & output, soloing, muting, etc., all of the things one >> needs to record multi-channel audio is very straight-forward and rock solid. >> There is no better platform on the planet to edit audio and it can all be >> done with keyboard shortcuts. In fact, Pro Tools has an plethora of key >> commands for all kinds of things. >> > Is there a better document of keyboard commands then is currently on the dvd > of pro tools 9? I wish we had a nice table that we could interact with that > one could easily find what they are looking for. I hate the preview always > goes back to the top when reading a pdf after switching to another app. I > need to be able to read and try the key strokes right away. My brain can't > just hold on to them all at once. > > Thanks > --FC >
