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.
Bookmarks