INTRODUCTION
When working on projects with limited audio space, such as apps for mobile, browser-based games or packaged electronics/toys, it is often necessary to squeeze as much out of that space as possible in order to meet or exceed the expectations of the project. From the standpoint of the sound designer, this is likely achieved through compressing the sound files in various ways. However, when working with linear audio that contains gaps of silence or recalls repeated audio, precious space can be saved by editing within your Pro Tools session and exporting the resultant files and session data for programming. While the processes for identifying and editing these two elements are different, their functionality in implementation is essentially the same. In Part 1, I cover the process for getting started, staying organized, and identifying and removing silent gaps.
GETTING STARTED
What’s needed:
*Pro-Tools (This tutorial is conducted in Pro Tools 9)
*Linear audio (e.g Dialogue)
*Playlist Dividers and Mutes (Short, silent files that you can create yourself, or download this .zip file)
*Access to spreadsheet software (This tutorial uses Excel)
*An understanding programmer
The example in this tutorial refers to a project I worked on that was intended to help children learn to count in German through repetition. It consists of 28 different sound files, comprising both dialogue and sound effects. Of the files that consist of only dialogue, many follow this pattern:
Sound File Example 1: “Eins. / Zähl bis / eins. / Eins. / Wow!”
Sound File Example 2: “Zwei. / Zähl bis / zwei. / Eins. / Zwei. / Gut gemacht!”
Sound File Example 3: “Drei. / Zähl bis / drei. / Eins. / Zwei. / Drei. / Super!”
Translation:
Sound File Example 1: “One. / Count to / one. / One. / Wow!”
Sound File Example 2: “Two. / Count to / two. / One. / Two. / Well done!”
Sound File Example 3: “Three. / Count to / three. / One. / Two. / Three. / Great!”
Without regard for silent gaps or repetitious audio, the sum total of the audio for this project would have been over three and half minutes. See below:
Since there was not enough space to accommodate that amount of audio, it was imperative that I find a way to cut down.
STAYING ORGANIZED WITH THE “PLAYLIST DIVIDER”
When working on projects like this in which multiple sound files will be edited within a track, discerning where files begin and end can be difficult. Therefore, I use a newly-created file I call the “Playlist Divider.” This is a silent demarcation placed at the beginning of each separate sound file to keep the session and resulting documentation organized. See below:
(“Playlist Divider”)
The “+” sign is used to keep the Playlist Divider at the top of the REGIONS file list for easy access. Here is an example of its use within the Pro Tools session. See below:
(Implemented Playlist Dividers)
The middle series of files appear to be separate, but they are all part of the same line of text. With the help of the Playlist Dividers, the line “Drei. / Zähl bis / drei. / Eins. / Zwei. / Drei. / Super!” stands apart from the others that precede and succeed it. When it comes time to export the session, this organization will be key in formatting the information, which will be addressed later in this tutorial.
REPLACING SILENT GAPS
Side Note: While going through this editing process, I recommend staying in “SHUFFLE” mode to retain the integrity of the space when removing and replacing silent gaps.
Assuming the project’s audio has been approved for implementation, it’s time to start identifying and removing the gaps of silence. Because of the amount of space I needed to save for this project, I accounted for gaps of silence starting at 10 milliseconds and greater. These gaps are identified and replaced with newly-created files called “Mutes,” which are just dummy, silent files of nearly the exact same length as the removed gaps. See below:
Like the Playlist Divider, the “_” at the beginning of the filename is used to keep the Mutes at the top of the REGIONS file list for easy access.
Side Note: When in the process of removing the silence, you have a couple options:
- Use the “Strip Silence” edit tool. If unfamiliar with it, there is a great explanation of how that works here. In short, it’s a great way to remove silence en masse through automation. If you follow this route, you will need to take an additional step by highlighting the now empty space between files to determine what length of Mute to put in its place. See below:
(“Strip Silence” applied and gap length identified)
- If you want more control over editing individual sound files, select Pro Tools’ “Selector Tool.” You can then manually highlight and cut the silence and then replace it with Mutes.
Let’s take a look at an example of audio that was treated with this process. See below:
(Original audio with gaps of silence)
(Silence removed and replaced by Mutes)
For instances where more than 500 milliseconds of silence was removed, I stacked the Mutes contiguously to make up for the extra space (e.g. 500ms + 125ms). Accommodating for every instance of silence is time-consuming, so I find it easier to start with a basic palette of Mutes and build as needed.
This process is repeated until all files are complete, after which the edited files may look like this:
This concludes Part 1. In Part 2, I continue looking for opportunities to save space by reusing audio clips in multiple places. Should you have any questions, please contact me via the social media links below or feel free to email me directly, george@creatingsound.com. Thanks for reading!
Hey George,
Interesting post–I can’t wait to see the other 2 parts!
Because I am a workflow nut (and have done a lot of foreign language program editing), one thing did jump to mind. Instead of creating dummy mute files with specified times then slotting those into approximate gaps, why not just delete the audio, consolidate the blank space, then rename the ‘mute’ region with your _m naming convention? The whole process can be automated with Quickeys (mac) or AHK (pc).
Assuming you are manually selecting the gap you could: cut the region, shift+opt+3 to create new ‘mute’ region of silence, numpad = 3x to select region length, cmd+c to copy that value, then cmd+shift+r to rename the region using your naming convention and pasting in the region’s length. Now you have a mute region named with its respective length.
I know that looks like a lot of work, but the whole process after making the selection can be automated and executed with one keystroke. That way, you can quickly replace all silences with your mute regions. If you the strip silence method, you could do the same thing. Just find the empty spots in the playlist, select them, then execute the macro from there.
I realize taking the time to create the macro might only make sense if there is a lot of audio to get through, but it could save some of the boring busy work.
Hey Stephen,
Thanks for reading and for the positive reply! My colleagues use Quickeys (mac) for a lot of their renaming, especially before export, but we haven’t done it yet for Mutes. This might be an interesting approach for especially large projects, as you mentioned. The majority of my smaller projects have limited audio to begin with and I’m assuming that your approach will work on the back end when it comes time to export the session data. I’d love to hear your thoughts once parts 2 and 3 are posted regarding your suggestions and how this might be improved with additional automation.
Cheers!
George
[…] In Part 1 of this tutorial, I covered the process for getting started, staying organized, and identifying and removing silent gaps. For Part 2, I go through more space-saving tips by demonstrating how I look for opportunities to reuse the same audio clips in multiple places. Tweet […]
[…] Hufnagl over at CreatingSound.com recently wrapped up a super-duper 3 post series on Saving Space with Linear Audio in Pro Tools. In a nutshell: When working on projects with limited audio space, such as apps for mobile, […]
[…] Hufnagl over at CreatingSound.com recently wrapped up a super-duper 3 post series on Saving Space with Linear Audio in Pro Tools. In a nutshell: When working on projects with limited audio space, such as apps for mobile, […]
[…] taken the tutorial I wrote for Creating Sound and have edited down to a convenient, standalone PDF. You can download the document with the […]