Low latency monitoring (in Studio One)

Hello and welcome to this week's article!

This time we're going to talk about a theme that is often overlooked, but that is of paramount importance: the low latency monitoring, and in ordering to do it, we're going to use the interface of Studio One, but the same rules applies to every DAW.

There are 2 types of low latency monitoring: hardware and software.

Hardware low latency monitoring is the ASIO protocol (also known as Hardware Direct Monitoring), a protocol created by Steinberg, which basically lets the drivers of the audio interface to dialogue with the DAW and work together to allow the lowest latency possible for the configuration.

A particular type of low latency monitoring is called Blue Z, or "low latency monitoring for instruments", which is a bit more advanced than the classic ASIO one and it's a function supported only from certain audio interfaces (such as Presonus, RME etc), which allows you to monitor with almost zero latency without stressing too much the CPU, but will not let you hear the sound processed by regular plugins, just for some which are made for that (for example in Studio One you can add a delay or a reverb to the real time signal, those plugins are called DSP plugins).

The "software" low latency mode instead (which still anyway involves hardware as well) is the one called Green Z, or "Native Low Latency Monitoring". This mode is more advanced, and it's supported only by few, more recent interfaces and computers, and allows the signal to pass through the whole chain of effects and come out as fast as with the regular hardware low latency monitoring, but it requires also a comparatively faster computer.
Studio One, unlike other DAW, allows you to choose different settings for the buffer size, which is the protection from jitters when doing playback, and the so called "device block size", which is the buffer size for recording: the lower it is, the faster.
This way you can set "dropout protection" medium or high, to make sure there are no jitters, and then just set the device block size as low as possible to minimize the latency, and finally enable the "green z" in the mixer on the tracks you are recording in real time to use this function that minimizes the latency and also lets you hear all the plugins in real time.

The more the cpu is struggling by making many tracks passing through real time processing, the more we will need to balance, for example by increasing the buffer size (and therefore the latency), or the dropout protection (to avoid hearing weird noises during the playback, which is anyway a function tied to the buffer size), so anyway monitoring is a balance game: we need to be aware of how much we need low latency (if we are recording we do, if we're mixing we don't) and change the settings according to the phase we're in.

Become fan of this blog on Facebook! Share it and contact us to collaborate!!