User manual

UAD Powered Plug-Ins Manual - 62 - Using UAD Powered Plug-Ins
UAD Track Advance
Overview The previous discussions on delay compensation (see “Delay Compensation”
on page 50) apply mainly when using only audio tracks. When MIDI tracks
are played simultaneously alongside audio tracks, a different (but related)
synchronization issue can arise.
Let’s say you have a MIDI track and an audio track with a UAD plugin on the
audio track insert. In this scenario, the host application will automatically
compensate for latency and no use of the UAD DelayComp or UAD Track Ad-
vance is required.
However, if the audio track is sent to a send/group/bus and that
send/group/bus has a UAD plugin on it, the audio track will be delayed in
relation to the MIDI track because the host does not compensate for latency
automatically on groups/buses (unless full-path latency compensation is im-
plemented in the host). If the MIDI track was an audio track, you would use the
UAD DelayComp on it to compensate for the latency. But you can’t put a UAD
DelayComp on a MIDI track, so what to do?
Enter the UAD Track Advance plugin (TrackAdv for short). It operates just like
the DelayComp plugin, but backwards. Instead of delaying unprocessed
tracks, it shifts them forward. It does this by reporting to the host application
that a track has a UAD plugin on it, so the host compensates for the latency.
However, the track audio is not actually processed by the UAD so the net re-
sult is that the audio plays early.
Note: The Track Advance plugin only works in hosts that support partial
(track inserts only) automatic delay compensation.
When to use
TrackAdv
UAD TrackAdv should be used whenever MIDI tracks are played alongside
audio tracks that are assigned to a send/group/bus that is using UAD plu-
gin(s).
Figure 14. The UAD Track Advance plugin window