Community Tip - What Should Go Into A Pro Tools Template Session
08-08-2013 10:00 AM
With the support of iLok, here is another community tip. This tip from Owen Swanson-Low is a very timely tip with me recently posting a tutorial video on how to create template sessions for both music and post. Owen says….
My tip is to spend a bit of time creating a session template. I start a session by opening one of my default templates. I think of it like a ‘virtual modular studio’. Things that I do:If you would like the chance to win a stormtrooper iLok courtesy of iLok then please submit it to us using the Contact Us page. Also do check the content on the site before you do it to make sure that the idea isn’t already covered.
- Set window layouts for your system- if your screen layout gets messed up, you can quickly switch back to normal;
- Have sets of tracks/busses already created, named, hidden and inactive;
- Keep track naming short and simple; use track comments to add extra detail;
- Set multiple dithering/mastering, busses/audio tracks for realtime ITB bouncing; set up a few cool send busses for reverbs and delays, with source tracks pre-populated with sends;
- If doing post-work, pre-define your usual frame rate; keep your edit window viewing options simple with as much space assigned to viewing session content, I make an exception to the groups/hide/inactive left-hand-bar, that I use frequently;
- Turn on marker colours; label markers with the marker ID number at the beginning of the text field - so you can use the .NUM#. command to jump around quickly;
- Set master bus outputs with preferred metering options - I have enough window space to keep spectrum analysis open all the time - so build it into my default window layout. In fact, I use a Shadow Hills Equinox to sum OTB to 2 tracks;
- I loop back into protools - so I set my metering inserts on an aux-in.
There are currently 1 users browsing this thread. (0 members and 1 guests)