Preamp control and recall, headphone routing, mono/dim.

More imprortantly 3.5 added duel buffering and native low latency monitoring of any plugin under 3 ms so you can apply your plugins to the input for example your favorite soft amp and record tracks with a complex song near completion.

I have track through S-gear at 2.5 ms latency on a test song with 140 tracks and 100 plugins.

Thanks for the info, much appreciated!

jpettit wroteMore imprortantly 3.5 added duel buffering and native low latency monitoring of any plugin under 3 ms so you can apply your plugins to the input for example your favorite soft amp and record tracks with a complex song near completion.

That's not unique to the Quantum, though, is that right?

No any ASIO interface can use LLNM.

There is bit more to the story.

Interfaces such as the 192 or very soon the Series III mixers have mirrored plugins with S1 so there is more integration.

The Quantum series are focused on extreme fast audio and do not have DSP.


S1 3.5 was released the same time to enable plugins to be in the recording path without the need for DSP.

jpettit wroteS1 3.5 was released the same time to enable plugins to be in the recording path without the need for DSP.

Yes, that's why I'm very interested in the Quantum. I've been using an Apollo Firewire using their console software to track with UAD plugins, but more and more I really like the idea of doing everything from within the DAW.

I've tried it using my 11Rack as an audio interface: I've put some plugins on the input channels (even some UAD ones!), and even with that interface it was doable, with about 30ms of latency. It was a great user experience to set up all the levels, plugins, and cue mixes from within the DAW.

If the Quantum brings even more of that experience (with super low latency) that's all I would ever need.

I can track with a Soft Amp at 1.5ms

Hi Guys, I have just hooked up my Quantum to my Mac Pro late 2013 model, 6 core 3.7ghz,16 gig of ram.

I don’t get zero latency , or close to it.

I have fiddled between all the audio processor settings but to no aveil. Tried different buffer sizes , that brings it down but with a hit to my CPU .

I have been trying to find videos or articles that can help me optimise the Quantum and Studio One 3.5

Pls advise if you can. Thank you so much👍

Start by telling us your buffer size and dropout protection settings along with are you using NLLM ( green Z).

Sow a picture of the DP page wiht all four latencies.

Hi jpettit
Thank you for all your help. it is hugely appreciated.attached is the screen shot.. i am getting pretty low latency now but the whole sustem feels clunky and not smooth. Also the CPU is much higher in general with the Quantums than the 192 used to be.

Your settings have in essence disable both benefits of the dual buffer system.

If you have a Quantum, start with typically 32 or 64 buffers on the device size.

The drop out you want high so start with HIgh and even play with the maximum.
You have turned off the ability for Low Z monitors by turning drop out to the minimum.

Try my settings.
Also please put your specs in your signature.

When i use the lowest dropout protection it is fine to work like that , but when i want to go back to using vsti's, i have to switch back to the maximum dropout ....but whike using the lowest dropout protection, the cpu is obviously running higher.

i see the "Use native low latency monitoring instead of hardware monitoring " is greyed out, is this suppose to be like that?

Thank you

Here is the screen shot of my screen shot at the moment, pls note the greyed out area

Here is another screen shot

The playback device is the The Quantum Aggregate, i dont know why it didnt show u on the screen shot

Those option are based on th settings of DOP vs. hardware buffers.
I believe It is called out on my monitoring hand book in FAQ

Please put you specs in we don’t know what system your on.

Aggregated devices introduces latency depending on what it is aggregated with.

Why don’t you use the non-aggregated quantum?

markbeling wroteThe playback device is the The Quantum Aggregate, i dont know why it didnt show u on the screen shot

Hi Roblof
The only way to use more than one quantum in a system is by creating an aggregate device otherwise it sees the two daisychained Quantums as seperate soundcards....Personally i dont see why they did it this way.

I also bought the 2 quantums to have more IO, otherwise i would be using the Quantum in the conventional way.

So they are linked via TB cables?
Also suggest a support ticket to confirm that assumption as aggregation is not possible on the Windows side.

Ok, but verify with a single quantum to determine if aggregation (is that a word?) is the culprit or not so that you don't chase ghosts.