Sweetwater
1-800-222-4700
View Cart
SEARCH
SHOP BY BRAND Free Shipping!
Tech Support:
Over 15,000 product support articles and factory-authorized service. Click Here »


Expert Center Sweetcare

«Back to Tech Tip Menu

Tech Tip of the Day Archives
1997 | 1998 | 1999 | 2000 | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 | 2007 | 2008

Using the UAD-1 in Pro Tools HD and Automatic Delay Compensation
03/02/2005

First introduced in version 6.4 of Pro Tools, Automatic Delay Compensation (ADC) makes life easier for people using plug-ins that cause some latency, like some look-ahead gates and limiters, up-sampling EQs, as well as the Universal Audio UAD-1 card. The UAD-1 card, as you may know, can be used in Pro Tools TDM and LE on OS X and Windows XP. The key to using the UAD-1 in Pro Tools is the VST to RTAS Adapter software made by FXpansion.

The UAD-1 has been used in Pro Tools LE for some time now. One thing that LE users have had to do manually is compensate for latency. Latency occurs on a UAD-1 plug-in because the audio travels from the application to the UAD-1 card and back. But since Pro Tools HD has ADC, latency caused by UAD-1 RTAS plug-ins are not as much of a concern. But that doesn't mean we don't need to be concerned at all, there are a couple things to be aware of

Setting Up the VST-RTAS Adapter

In the VstRtas Configure application, users can set a Block buffer size at which the UAD-1 plug-ins will run (see figure1). The higher the number, the more latency you will get. The lower the number, the less latency, but the trade-off is higher host CPU load. This buffer is different than the hardware buffer size in the Pro Tools Hardware setup dialog.

While it defaults to 1024, setting the block buffer size down around 128 gives less latency. While it's harder on the computer's CPU, the CPU is not working hard at all, since all the other plug-ins are running on either the TDM bus or the UAD-1; and both options leave the host CPU for other operations.

The way to determine how much latency per plug-in is multiply the block buffer size in the VST-RTAS Configure application by three (one buffer for the trip to the card, one buffer for the trip back to Pro Tools, and one buffer for the adapter). In Pro Tools, the 128 sample buffer size translates into 384 samples of delay for each plug-in. It is important to know how much latency you get per plug-in, as you will see later.

Enabling ADC in Pro Tools

After converting the plug-ins, they will show up in the Pro Tools mixer as RTAS plug-ins, under the "Other" heading.

Pro Tools Playback Engine:

In order to start using ADC, the type of delay compensation needs to be chosen; selecting the Delay Compensation Engine type in the Playback Engine window, under the Setup menu, does this. For our purposes we'll choose "Long (4095 Samples per channel)". This means we have 4095 samples per track for delay compensation. This is valuable information, as we might need it later. Also, while you're in this window, bring the CPU usage limit to at least 85%.

Once that is set, you'll need to turn delay compensation on, which can be done in the Operations window. It is important to see how much delay is being compensated for; so that you know how much delay compensation you have left on each track. So, it is best to be able to view the Delay Compensation as it adjusts the tracks. To do this, go to Display/Mix Window Shows/Delay Compensation View.

Understanding the Delay Values

For an example, lets assume we have four mono audio tracks, and two of them have UAD-1 RTAS plug-ins on them. At the bottom of the channel strip in the mix window you can see the Delay Compensation values.

The two items to look at are "dly" and "cmp". The first value, "dly" is the delay that the plug-ins are causing on the track. "Cmp" is the amount of delay compensation that Pro Tools is applying to the track. As we said earlier, there are two UAD-1 RTAS plug-ins on two tracks, which we'll call Kick and Snare, and the other two tracks, Overhead-L and Overhead-R, have no plug-ins. The plug-ins on the Kick and Snare tracks are causing 384 samples of delay, so Pro Tools' ADC is delaying, or "compensating", the two overhead tracks by 384 samples. Basically, Pro Tools looks at the tracks that have the most plug-in-induced delay, and then delays the rest of the tracks by the same amount.

Now let's add a TDM UA Pultec Eq plug-in to one of the overhead tracks so you can see how the latency values change. UA's Pultec EQ has 16 samples of latency itself due to up-sampling. Now the track with the Pultec is being delayed by only 368 samples, because the Pultec's delay means that Pro Tools does not need to compensate that track as much, while the Overhead-R track is still delayed by 384 samples.

Now let's see what happens if we add a UAD-1 RTAS plug-in to the track with the Pultec. The new UAD-1 RTAS plug-in will add 384 samples of delay to that track; so now that Overhead-L's delay is 400 samples Since the Kick and Snare tracks now have less delay than the Overhead-L track, those two tracks must now be delayed by 16 samples to match the delay of Overhead-L.

Pro Tools LE users have been doing this delay compensation manually using Universal Audio's DelayComp plug-in. The ADC in Pro Tools HD makes using the UAD-1 very easy. The only thing you need to watch out for is making sure that you don't exceed the amount of delay compensation that is available per track. The way to do that is:

  1. In Pro Tools, use the Long Delay compensation option, and increase the CPU usage limit.

  2. Convert the UAD-1 VST plug-ins at a small buffer size, like 128 (remember, the actual delay will be three times that amount!).

  3. Make sure you can view the delay compensation in the Mix window.

  4. Start mixing!





Other Techtips from March 2005:
March 31 - The Links in Your Mastering Chain
March 30 - The Top Five Questions about Electronic Drum Mesh Heads
March 29 - Currently Unavailable
March 28 - How to use Oxygen 8 to control Guitar Rig
March 25 - Currently Unavailable
March 24 - RAM and your computer.
March 23 - Vocal removers revealed.
March 22 - Safety on the Job: Rigging is Serious Business!
March 21 - Universal Audio's UAD-1 and the Apple G5.
March 18 - Currently Unavailable
March 17 - Phantom Power and Your Mixer
March 16 - Cabling Basics: AC and A/V Don't Mix
March 15 - Currently Unavailable
March 14 - Acoustic Treatment for Surround Mixing
March 11 - Clearing the Air About Sound Waves
March 10 - Matching The Phase Of Mic & DI
March 09 - Pre-Fader, or Post-Fader?
March 08 - Currently Unavailable
March 07 - Currently Unavailable
March 04 - Currently Unavailable
March 03 - The Direct Route from Your Keyboard to the PA
March 02 - Using the UAD-1 in Pro Tools HD and Automatic Delay Compensation
March 01 - MIDI Merging


1997 | 1998 | 1999 | 2000 | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 | 2007 | 2008
     
Home | Gear Reviews | Videos | Buying Guides | Glossary | Tech Tips | Show Reports | Publications | Featured Articles



Sweetwater Deals! Sign up for weekly e-mail offers:
Unsubscribe | Learn More »
About Sweetwater
· Why Sweetwater
· Our History
· Customer Testimonials
· Tour Our New Headquarters!
Additional Services
· Publications
· Gift Certificates
· Special Financing
· Sell Your Used Gear
Benefits & Policies
· Free Shipping on Most Orders
· Safe Shopping Guarantee
· Shipping & Delivery Times
· We Protect Your Privacy
Customer Support
· Track Your Order
· Return Policy
· Sweetcare 24/7 Support
· More...
{SWEETWATER_FOOTER_BANNER_0} {SWEETWATER_FOOTER_BANNER_1}

Careers   |  Academy of Music   |  Events & Seminars   |   Recording Studio   |   Trading Post   |   Download   |   Links   |   Press Releases   


Sweetwater Sound, Inc.
5501 US Hwy 30 W
Fort Wayne, IN 46818
Get Directions
Toll-Free (800) 222-4700
Local (260) 432-8176
Fax (260) 432-1758
Contact Us
Telephone hours:
9-9 Mon-Thu, 9-8 Fri, 9-7 Sat EST
Retail Store hours:
9-8 Mon-Fri, 9-7 Sat EST
Current Sweetwater time is 1:45 PM
HACKER SAFE certified sites prevent over 99.9% of hacker crime.

© 2008 Sweetwater Sound Inc. All rights reserved. Please read our Terms of Use and Privacy Policy. Site Map


{GOOGLE_ANALYTICS}