asked Jan 10 at 11:57 by phuitema (31)

edited Jan 10 at 12:36


Using Windows 10 (intel 9900k)– Bitwig 3.1.1, Latest UAD drivers

As a new UAD user I had a rough startup with UAD/Bitwig. My experience:

Set windows to always use high performance mode. Initially, core parking was controlled entirely by the operating system. The aggressive core parking of Windows led to a great deal of inefficiency during bursting CPU loads. Intel moved core parking control onto the chip in the Skylake generation, and AMD followed, but still the parameters of the Windows power plans are set to aggressively park CPU cores. Even the default ‘High Performance’ power plan is not immune. Any CPU throttling (below 50%) cause strange DSP spike within Bitwig. Consider

Screenshot of bitwig with defalut windows setting. These spike scale with the dsp load, a higer DSP load will increase the spikes. With 2048 asio buffers size i was not able to play (smooth) more then 16 track with just a audio sample or bitwig fm synth.

alt text

Set windows to optimize background services. This seems to provide more CPU headroom of the (Asio) audio drivers & plugin services of bitwig.

Remove the extra buffering in the UAD driver (toggle this in your UAD software). Kudos for bitwig .. this saves 64 samples. Set your audio buffer to the lowest possible amount. Every UAD plugin “duplicates” your DAW buffer, so the lower the buffer .. the lower the latency on each UAD plugin.

You can use UAD plugins into a live track mode (the microphone icon on every plugin windows) but taxes your system. LiveTrack Mode reduces latency on an active UAD-2 plug-in to the lowest possible amount. This feature is highly useful for monitoring processed audio when recording live performances. In LiveTrack Mode, UAD-2 signal data is transferred and processed "immediately" instead of being buffered, resulting in reduced latency (and higher cpu tax)

From UA:

Some UAD plug-ins introduce additional latency within the plug-in itself (in addition to hardware I/O buffering latency) to achieve sonic design goals. When these plug-ins are used in a DAW and/or Apollo’s Console, the additional latency is induced in the signal path. Therefore, they require more compensation to remain perfectly synchronized with other tracks, versus UAD plug-ins that do not have additional latency.

Note: Compensating for the additional latency from these UAD plug-ins is performed automatically by Bitwig when the latency delay compensation function is enabled in the host.Although the latency added by these UAD plug-ins is negligible (typically between 0 – 100 samples, depending on the plug-in and session sample rate), if this extra latency is not compensated, it can affect phase coherency in a session.The additional latency values, in samples, of UAD plug-ins with additional latency are listed in this chapter for the benefit of users with plug-in host DAWs that do not perform automatic delay compensation.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Jan 10 at 11:57

Seen: 44 times

Last updated: Jan 10 at 12:36

Related questions