This is an excerpt from my column “The Pro Tools Corner” at audioMIDI.com

Metering with DigiRack PhaseScope

SignalTools provides a set of useful metering utilities in both TDM and RTAS formats, and come automatically installed as part of the free DigiRack plug-ins that ship with all Pro Tools systems. Consisting of SurroundScope and PhaseScope, these tools provide access to critical information regarding a signal’s level and phase coherency, both paramount in any mix workflow. This week I will walk you through the PhaseScope plug-in and hopefully shed some light on the frequently misunderstood concept of metering in Pro Tools.

Why meters matter

A nasty side effect of the ease and accessibility of DAW recording, I often find that many aspiring engineers and producers know very little about topics such as metering, headroom, gain-stages, and other basic audio engineering concepts. As modern, virtually unclip-able mixers and plug-ins become the norm in the native DAW world, many simply ignore metering all together. The truth is, meters can actually be an engineers best friend, providing vital information about a signal’s level and phase as it relates to a specific system’s output capabilities. For example, meters allow us to make sure that our signals don’t exceed the maximum level allowed by a given system or likewise, dip below the noise floor. In a digital system like Pro Tools this is extremely important, as these systems have no headroom beyond the maximum quantization level of 0dBFS, often referred to as “full scale” or “full code.” Metering is also very important in post-production and broadcast, as specific program requirements are often defined for peak and average levels. If you think about it, mixing in a system without meters would be a bit like playing a sport without the boundaries of the field marked off.

Pro Tools metering basics

The track metering in Pro Tools can be a bit convoluted depending on whether you are recording or playing back audio, and whether or not you have enabled “pre-fader metering” from the options menu. As a general rule, whenever a track is record enabled, the track’s meters display pre-fader and pre-insert input levels in dBFS, regardless of the meter option selected. This means you can rely on the track’s meters when determining the optimum recording level of a signal, regardless of the volume fader’s position and any other gain-stages added by inserts. When a track is not record enabled, the metering is governed by the option “Pre-Fader Metering” found under the Options menu.  When pre-fader metering is enabled, a track’s meters display the signal level after any plug-in inserts but before the track’s volume fader is able to add or subtract any gain (hence the term “pre-fader”). With pre-fader metering enabled, a signal that came in peaking at -5dBFS with no inserts, would read the same no matter how much you push or pull the fader.

Hint: in Pro Tools HD, when a track is input enabled (but not record enabled), a track’s meter will follow the same rules as any other non-record enabled track, taking into account any plug-in inserts regardless of pre-fader metering mode.

Using the PhaseScope plug-in

The DigiRack PhaseScope plug-in is found under the multi-channel “sound field” category and can be inserted on any stereo track. The PhaseScope provides level metering with 8 different meter types (Peak, RMS, Peak+RMS, VU, BBC, Nordic, DIN, and Venue), a Lissajous meter display, and a combo phase/Leq(A) display. The combo phase/Leq(A) can be selected under the options section in the lower left hand corner of the plug-in. I generally place the PhaseScope on my master fader, as master fader inserts are the only track inserts in Pro Tools that are post-fader. In this case, by placing the PhaseScope as the last insert in the chain you are able to meter right before the signal hits the D/A at the interface, this can be useful for checking the difference in peak and/or average level a buss compressor or brick wall limiter is adding to your mix or for checking final output levels when complying with post/broadcast standards.

Setting up the level meter:

The level meter defaults to “peak” metering in dBFS, where 0 dBFS represents full scale, or the loudest signal Pro Tools can send out to the D/A converters without clipping. See the DigiRack plug-ins guide for more information on the different metering types and reference calibrations. You can set the reference mark wherever you’d like, all it does is change the color of the meter when the signal exceeds the marker (which can be very useful in post production applications where peak and average values are more scrutinized, beyond just the defacto “clipping/not clipping”). Remember, how the dBFS scale relates to the analog world is far from standardized and entirely dependent on your converter’s calibration. For example, the 192IO is factory calibrated for 18dBs of headroom at +4dBu, therefore a sinewave playing out at -18dBFS in Pro Tools would read 0 VU on an analog meter attached to the 192s +4 dBu outputs. While the complex nuances of the dB scale and all of its variations are way outside the scope of this article, if you feel up to it and want to learn more, there are some great articles just a google search away.

How to read the Lissajous and phase meters:

The goal of a phase meter is to determine how similar the left and right hand sides of a stereo signal are in relation to each other. The way the two signals relate can greatly affect the mono compatibility of a mix (as is the case where the left and right hand sides are summed into a single mono channel). While it is becoming less common for people to digest music and film on mono playback systems, phase coherency is still an important consideration in finalizing a mix. In a worse case scenario, the left and right sides of a stereo signal would be identical but have opposite polarities, resulting in a complete cancellation when summed into mono. While this rarely occurs, the phase meter can easily identify even subtle phase issues by comparing the relationship between two signals. Generally, positive values above 0 indicate acceptable mono compatibility (a value of +1 would indicate a duplicate signal in the left and right channels completely in phase), whereas values from 0 to -1 indicate potential problems.

To experiment, take two identical mono signals on two separate tracks. Pan one signal hard right and the other hard left and look at the PhaseScope plug-in on the master fader, it should read +1. Now apply the Audiosuite>Other>Invert plug-in to just one of the signals (effectively flipping its phase 180 degrees) and look at the PhaseScope again, it should now read -1. If your monitoring system allows you to sum the main output to mono, engage that now. Pretty crazy huh? Now while it is unlikely for your mix to exhibit perfect inverse phase correlation between the right and left hand sides, this extreme example can help you appreciate what is at stake.

As opposed to reading the phase meter, reading the vectorscope (or lissajous figure) in PhaseScope can take a little more practice. The goal of the graph is to visually represent the relationship between the amplitude and phase of a signal in real time. Sound complex? Well to simplify this, you can generally relate vertical lines (or lines living in the top and bottom quadrants) as in-phase, where as horizontal lines (left and right quadrants) represent out of phase material. With practice, one can even recognize different stereo recording techniques such as X/Y coincident, spaced mic, etc simply by looking at the graph.

Using the Leq(A) Meter Display

The Leq(A) display is designed to show a true weighted average of the power level in a stereo (or multichannel) signal. This meter displays a “floating” average for the level over the chosen interval (1s,2s,10s,etc). This can be very useful when trying to compare the average level vs peak level of a mix as it relates to other mixes. Experiment by comparing the average level of different mastered music in your collection (hint: try comparing something from the 70s to something from the 00s). I usually start with the default interval setting of 2 seconds. As always, remember to use your ears in addition to any metering tools, as perceived loudness can vary greatly even with two signals sharing the same average level.

Mixing on AIR part 4: BF76

While not technically part of the new AIR collection of plug-ins, the Bomb Factory BF76 compressor does come included with every Pro Tools installation and is the only ‘vintage’ style dynamics processor that ships with the standard configuration. Those in the know will quickly recognize the interface of BF76 as a virtual recreation of the famous Urei 1176 peak limiter, but because of its less than intuitive controls many new users forgo this little gem in favor of the more straightforward Digrack dynamics package. This week at the Pro Tools corner I will fill you in on some of the history behind the BF76 and show you how to integrate this great vintage modeled plug-in into your mixes.

Dynamics Review:

Before we can get into the specifics of BF76, it is useful to review the basics behind dynamic range and processing. The term “dynamic range” is widely used in audio engineering and is actually quite easy to understand. Simply put, a signal’s dynamic range is the difference between the softest and loudest parts of that signal’s amplitude. Dynamic range can be measured over a very short period of time, like the difference between the transient peak of a snare drum and its ringing decay, or over longer periods, like the difference between the soft and loud words of a vocal phrase. The job of a dynamics processor is to work within this realm of dynamic range by reacting to the variations in signal level that occur over time.

For example, a compressor or limiter (such as BF76) reacts to the louder portions of an audio signal by attenuating or turning the signal down by a specified amount (or ratio), with the goal of reducing the overall dynamic range of that signal over time. Think about a vocal with a wide dynamic range. Left unprocessed, many words will pop out over the rest of the mix, sounding awkward and disconnected, while others will be lost beneath the mix completely. Using a compressor or limiter the engineer is able to automatically turn down these louder words while simultaneously bringing up the softer ones, effectively reducing the overall dynamic range of the vocal. In this case, using a compressor to reduce the dynamic range allows the vocal to sit in the mix without poking out or getting lost, all without extensive volume automation.

Mixing with BF76

The bomb factory BF76 is designed as a plug-in model of the famous Urei 1176 peak limiter, developed in the late 60s by Bill Putnam and still being manufactured today by Universal Audio. The 1176 is a FET (field-effect transistor), solid state dynamics processor with a very unique sound, known for retaining the brightness and clarity of a signal that other compressors often take away. Because of its extremely fast attack and release times, the 1176 is a very versatile processor that works well on almost anything, from evening out a vocal or bass, to creating punchy snare drums, even master bus processing.

The Interface

The interface of BF76 is a near replica of its real world counterpart featuring a limited number of parameters. At first these parameters may seem counterintuitive to what you are use to seeing on other compressors, but once you learn what they do you may find that it is actually easier to use this processor.

Input: You may have noticed that the BF76 does not have a ‘threshold’ parameter like most compressors do. Many vintage compressors, including the 1176, feature a ‘fixed’ threshold that is driven by an input control, so think of the input parameter as the threshold parameter on the BF76. To increase the amount of gain reduction (or compression), turn the input counterclockwise towards 0 while watching the GR meter until the desired amount of compression is achieved. Remember, the threshold of a compressor defines the level at which the compressor begins to act on or ‘compress’ the incoming signal, in a sense it defines the “what is loud, what is not” line that the compressor uses to turn on and turn off, enabling it to control dynamic range.

Output: The output of the BF76 is used to return the signal to unity gain after compression. After achieving the desired amount of gain reduction (compression) use the output control to return the signal to its pre-processed level. It can be useful to use the plug-in’s bypass button to determine the correct output setting, as a general rule try to match the signal’s level to the bypassed state. This can help in evaluating the actual processing, avoiding the “it’s louder so it must be better” approach.

Attack: As with most compressors/limiters, ‘attack’ defines the amount of time the unit takes to grab onto the signal once a threshold breach is detected. Think of it this way, when you watch your favorite program on TV and an insanely loud commercial comes on, breaching your ears threshold of “too loud,” your “attack” would be the time it took for you to reach for your remote and turn the volume down.

The attack time on the BF76 is variable from .4 ms to 5.7 ms, which is quite fast even at its slowest setting. ‘7’ or 100% clockwise is the fastest attack while 1 or 100% counter-clockwise is the slowest attack. This is counter intuitive for most people, as one might assume that ‘7’ would be slower than ‘1’, but remember these numbers do not represent millisecond settings like most compressors, as a general rule just remember the BF76s attack/release controls are backwards. Slower attack times allow more of the signal’s transients through and can be great for putting a sharp ‘thwack’ on the head of a snare or kick drum while faster attack times can soften a signal’s attack. Because the range of attack time on the BF76 is so small, changes to this parameter can range from very subtle to inaudible, depending on the program material.

Release: Release defines the amount of time the unit takes to recover after the signal falls back below the threshold. Going back to our TV example, this would be how long it takes you to turn the television back up after the loud commercial break was over.

The release time on the BF76 is variable from 60 ms to 1.1 seconds. ‘7’ or 100% clockwise is the fastest release while ‘1’ or 100% counter-clockwise is the slowest release. Setting the release control close to ‘7’ can really help bring out the sustain of a signal for a super aggressive sound, but be careful as it can go from 0 to insane sustain and pumping with the tiniest tweak. Because the 1176 design has program dependent attack/release characteristics it is best to use your ears when setting these values rather then consuming yourself with millisecond values (notice how these values aren’t even labeled in milliseconds on the units controls). Be aware that the release control provides a much wider range than the attack and is much more sensitive to small changes, setting the attack and release times too fast can result in distortion.

Ratio: The ratio buttons define the amount of gain reduction in correlation with the threshold. For example, a ratio of 4:1 would attenuate a signal ¾ dB for every 1 dB over the threshold, so if a signal’s input is 4dB past the threshold only 1 dB will reach the output, 8dBs past the threshold at input would yield 2 dB at output. Ratios of 12:1 and 20:1 act more as limiters. Try shift clicking one of the ratio buttons to engage the famous “all buttons in” mode, dramatically changing the compressor knee and the character of the compression.

Metering: BF76 provides gain reduction (GR) and output metering modes (-18 and -24). In meter mode -18, the meter is calibrated so that -18dB FS equals 0 VU while in meter mode -24, -24 dB FS equals 0 VU. Because the less than ideal ballistics of this virtual meter don’t always help me personally, I often set it to ‘off’ and work just by ear.

Tips for using BF76

• A great starting point for most material is the default of 3 attack and 6 release, or “10 and 2 o’clock.” Set the ratio to 4:1 and adjust the input until the gain reduction (GR) starts diving a bit. Use the output control to balance out the signal, using the plug-in’s bypass as a guide. This method is great for sitting a vocal or acoustic guitar in the mix.
• Use BF76 as a parallel processor on snare or overhead tracks (duplicate the track and run one track dry and one track with BF76). Over compress the duplicate track using a very fast release (try 6 or 7) to really bring out the sustain of the processed track then blend the over compressed duplicate track with the original to taste.
• Try processing a mono room mic with the “all buttons in” mode.
• Try using it on the master bus with a ratio of 4:1 or 8:1, just kissing the tops of the transients (1-3 dBs of gain reduction). You will probably have to reduce the input from the default level to achieve this.

In closing

While some will argue that there are better third party plug-in recreations of the 1176 available for Pro Tools, and they might be correct, as a professional I like to be able to get the job done with just the stock plug-in set when I have to. Being familiar with all the stock Pro Tools plug-ins, including BF76, prepares you for any recording/mixing scenario, regardless of the plug-in availability on the machine.

Pro Tools Automation Part 2:

In the last installment of the Pro Tools corner, I walked you through some basic automation techniques in Pro Tools. Picking up where we left off, this week I will show you a few more ways you can manipulate automation in Pro Tools, including graphic editing and the automation of plug-in parameters. If you missed the first part of this article, you might want to check it out here before you proceed.

Graphic Manipulation of Automation

In the last article I showed you how to view your automation data directly against the track’s waveform and hinted at the fact that the automation points, called “breakpoint” can be manipulated with the edit tools. Some people like to call this “graphic automation” and it is a great alternative or supplement to the real-time automation we learned last week, especially if you don’t own a control surface.

Remember you can switch a track’s view to show any automation graph by simply clicking on a track’s view selector.

Editing Automation with the Grabber Tool:

• Use the grabber tool to create new breakpoints by simply clicking on the automation graph (the black line).

• You can move existing breakpoints with the grabber tool by clicking and dragging. Hold down Command (Mac) or Control (PC) to move the breakpoints in finer increments.

• Delete break points by Option-Clicking (Mac) or Alt-Clicking (PC) on an existing breakpoint.

Editing Automation with the Pencil Tool:

• Use the freehand pencil tool to click-drag and draw automation curves in a track’s automation graph.

• Click and hold on the pencil tool to show a list of pencil tool options. Use the line tool to easily create straight lines.

• The triangle, square, and random pencil tool options will create shapes based on your grid settings. These are great for tempo synced automation effects. Try setting your grid to a 1/32^nd note and use the square pencil tool to draw in mute automation data for a cool gate effect. Or try using the triangle pencil tool on the pan graph with a grid setting of a ½ note or 1 bar for a cool auto-pan effect, no fancy plug-in necessary.

• Unfortunately the parabolic and s-curve pencil tools do not work with automation breakpoints, only the tempo editor.

• Some graphs, like mute or many plug-in parameters, are stepped. In other words they are either one value or another, lacking the ability to glide smoothly between two states (like a volume or pan graph can). Therefore, trying to draw in sweeping curves with your pencil tool wont have much effect on these types of graphs.

• Just like the grabber, Option-Click (Mac) or Alt-Click (PC) to delete a breakpoint

Editing Automation with the Trim Tool:

The trim tool is used to scale existing breakpoints up or down, or make “delta” changes in an already existing automation graph. The trim tool works best by first selecting a range of breakpoint with the selector tool and then trimming them up or down. Notice the “tooltip” in the top left-hand corner of the graph that shows you the current parameter value as well as the “delta” amount or relative change. The trim tool is great for selecting a short passage, say a phrase or word of a vocal, and easily trimming it up or down by a few dBs. Like the grabber, you can hold down the Command key (Mac) or Control key (PC) while you trim for finer trim increments.

Other Editing Tips:

• You can cut/copy/paste/duplicate automation much like region data. To copy and paste from one automation type to another (say from volume to pan) use the special paste command under Edit > Paste Special > To Current Automation Type.

• You can delete multiple breakpoints by selecting them with the selector tool and pressing delete. To delete all automation (across all graphs in a track) in one pass, hold down Control (mac) or Start (pc) while you hit delete, or use the Edit > Clear Special menu.
• By default, automation breakpoints follow region edits. If you move a region that contains automation behind it, the automation will move too. You can disable this by un-checking Options > Automation Follows Edit.
• When you copy and send or a plug-in from one track to another (by option (mac) or alt (PC) dragging) all automation graphs pertaining to that send or plug-in are copied also.

Automating Plug-Ins

Automating plug-ins is pretty much identical to automating volume or pan in the mixer, but there is just one extra step before you start. Because complex plug-ins can have hundreds of automate-able parameters, it would be inefficient to have all these show up under a tracks automation view when most of the time you are only interested in automating a few specific parameters. Because of this, Pro Tools requires you to enable the specific plug-in parameter you wish to automate before adding automation.

To enable a Plug-ins parameter for automation:

1. Control+Option+Command-Click (mac) or Control+Start+Alt-Click (PC) directly on the plug-in parameter you wish to automate.
2. Choose “Enable Automation for ****.”
3. Once a control is enabled for automation it will show up as a graph in the track view list and can be automated by any of the methods covered in these articles.

Alternatively you can look at the plug-ins entire list of automate-able controls by clicking on the plug-ins automation button, located underneath bypass. This list contains a left hand side of potentially automate-able parameters and a right hand side of parameters currently enabled for automation. Double click a parameter to move it from the left list to the right list. Pro Tools can by default set all plug-in parameters to be enabled for automation as soon as the plug-in is inserted. The preference “Plug-In controls default to auto-enabled” can be found under the Mixing tab of Setup > Preferences.