Unusable latency Nektar GX61 and Clarett 4PRE ASIO

[Murray Webster]

Hi all,

Getting unusable latency with this combo even down as far as 16 samples.

Works perfectly with Band-In-A-Box.

Any ideas?

Thanks!

M

[Sock Monkey]

ook

Edited 6 hours ago by Sock Monkey

[Wookiee]

@Murray Webster as Latency both Audio and MIDI are a correlation between Computer power and MIDI/Audio hardware, without knowing what your computer is we cannot help.

Personally I use a Focusrite Clarett Pre 8 USB and Arturia Keylab 88 Mk 1 without any latency issues. Running at 96 samples and capable of real-time recording with FX.

[reginaldStjohn]

The dreaded Realtek Asio driver and the Stienberg genericd ASIO drive have been known to cause these problems as well. Make sure there are no other audio drivers showing up. If there are, uninstall them.

[Sock Monkey]

Ook!

Edited 6 hours ago by Sock Monkey
Ook

[Wookiee]

@Sock Monkey whatever, you try running an underpowered cpu, say a two core 1,5 ghz at 96 samples.

Your CPU dictates how fast it can process data, it really is that simple.

But I have noted how much of an expert you are.

[Murray Webster]

Sorry guys, yes...more info...

AMD Ryzen 7 7700 8-Core Processor  3.80 GHz 64Gb RAM

Trying to play NI Session Horns Pro or Dimension Pro through ASIO 4PRE from the Nektar USB midi and there's like an 8th note audio delay when set to 16 samples.

BIAB using ASIO playing TTS-1 is fine.

M

[Wookiee]

@Murray Webster, subject to being corrected by the "expert" when recording ideally you are looking to achieve something called the Total Round Trip time. Ideally that is around 10 to 12 ms as that is the average latency that is undetected by the human ear. Apparently some Sonar radar operators can detect better.

A guitarist standing 10 feet from his amp experiences approximately ms of latency. 

My question is why are you using such a low sample level. Many people achieve good results at 96, 128, 256, I suggest increasing your samples to a significantly higher figure. 

If you still have issues try downloading the free Resplendent LatencyMon which might help with identifying where the latency is being introduced.