Is 5.9MS a respectable amount of latency?

DJ Life & Community General Discussion
1

Is 5.9MS a respectable amount of latency?

After upgrading to Traktor Pro 2, I’ve spent countless hours trying to optimize my PC.

With TP, my latency was LOW. The load meter would bounce just above the zero mark. The second I installed TP2, I was fighting to keep it below halfway.

Currently I have it at:

44.1K Sampling Rate
1MS USB Latency

The load is hovering just above the halfway mark, and it’s at 5.9MS latency.

2

They say anything below 10ms is good. So YES!

3

yes

4

Keep in mind traktor 2 measures latency differently so it will always be “higher”. 5,9 is a totally reasonable value.

5

i would kill for those settings :wink: i run at around 11-15ms

6

9.5ms here on my desktop and laptop
Might let it go a tad higher on my laptop due to issues with cpu usage meter and apc40

7

i can go to about 3.5 with tp1 but that’s not an option with the new lemon update

8

I feel ya bro. Same boat here.

9

Sorry if i’m hijacking this thread - But what exactly influences the latency? Is it just the CPU speed?

10

Hey Sparkbro,bra,

Have a look there. Its a good start.

11

A little above half way isn’t that bad but there is more to it than just latency. TP2 uses more CPU power because of the new ability to be able to route more than 1 deck to the same output. That takes up a lot of CPU power. I use a Xone DX and have the system performance set at “normal” which gives me the output latency at 1016 samples/23ms and the input latency at 307 samples/6 ms. This translates in Traktor as latency at 256, processing 5.8, output 17.2, overal 23ms. My meter is about 1/4 way. The other thing that pushes CPU power big time is keylock. Go to the transport setup and change the keylock settings to Eco and scratch and you will see a drop in CPU power. I have no issues at all.

12

I run with 6.8 on my desktop, and it’s fine. CPU meter around half.

13

I run around 11 just fine.

14

When using timecode, I find anything more than 8 ms gives me serious delay on the feedback.

15

First of all, the latency number reported in Traktor isn’t your ACTUAL latency. At best, it’s just the latency introduced by Traktor. So looking at that number as a rule is kind of a red herring. It’s one small part of a much larger picture.

Second, the WAY you use your software makes a big difference. If you’re using Traktor as a DVS, latency will be much more important to you than if you’re using the software with a MIDI controller.

In the DJ world, the latency we’re really concerned with is the time between a physical action (like pressing a cue button) and the resulting sound. But a lot of things can effect this. Are you listening to your mixing on speakers? Every meter they are away from you adds 3ms of delay. Using a hardware mixer instead of the internal software mixer? That can add more than 20ms of latency depending on the quality of the mixer and it’s configuration. The length of your audio cables can also add delay (it’s called propagation delay). Even the GUI process for your given app might introduce quite a bit of latency.

Guys, that latency measurement is a tool you can use to help tweak your own system for better performance. Don’t get bent out of shape about your number. Tweak your system until YOU are happy with the performance of your particular setup. You will know immediately if latency is a problem for you.