Playback stutter in keylock function

Hello,
I've encountered a problem with manual cueing a track. If the keylock is activated, during maually cueing the track, there is a stutter on the track that plays. If the keylock is disabled, problem is gone.

I already send a mail to tech support of NI, I am curious about the reaction.

I am a house DJ, so the manually cueing on a specific point is a neccesity for me. Until now I have worked around the problem by disabeling the keylock, manually cue, and then enabeling keylock again.

Anyone with the same experience?

My system is fast enough ( Pentium D 3 Ghz/4GB RAM/Win 7), only Traktor pro 2 installed (and yes, the latest update to). Also no other applications installed, only Traktor, and I have a script to disable all the unneccesary background services of Windows, wich are not vital for Traktor.

 

Maybe not, the problem you describe points towards an underpowered system (at least at current latency settings). The glitches you are experiencing are likely caused by a buffer containing audio data running empty.

What audio interface are you using? Have you tried to increase buffer sizes/latencies?

 

I use the Traktor S4 audio interface directly. I Just returned from a weekend away with the family, so tomorrowmornin I will do some extra tweaking
Below the reaction from NI support:

We are aware of some load issues with Keylock in Traktor Pro 2.1.1 but we have not mapped them directly to the use of CUE. I suspect this is not the core of the issue; the stutter is caused by use of keylock and might be triggered by different events.

Nonetheless, if you could reproduce the scenario that leads to this particular
stutter-- also,does it happen almost everytime you perform this particular action?

Finally, please go to Preferences>>Audio Setup and in your device settings, choose a sample rate of 44100 Hz (please select it from the list even if it is already
set) and a latency of 512.

Finally, if you are not using an i5/i7 processor, please disable "Enable Multicore Support"

Let us know if this lead to a better performance.

 

I have never been able to use the high quality keylock preference
I have it set to the eco in preferences in the transport section.
A good way to test this is to leave the prefs open and scratch a deck.
With keylock on high quality the cpu load jumps very high and if scratching for a long time with a couple of effects enabled it almost always will cause a glitch.
If you scratch with eco keylock the cpu load indicator stays almost still.

I have also heard some other complaints of problems in high quality keylock mode.

Check out the scratch test and see if that helps.

In the windows tuning tips it says to use only multiples of 64 for latency.
64,128,256,512
My usb buffer is set at 3ms

 

It's not the scratch that makews the music glitch, it's the manual cuing with the platter that gives a problem. Iif you carefully cue up to let's say a beat, the slower you move the platter, the more the problem occurs. I hope to be able to make a short video of it tonight, so that you can see what happens. On the other way, I think that if NI system requirements are dualcore 2 Ghz and 2 GB RAM, a Dualcore 3 Ghz with 4 GB RAM should be more than sufficient to work flawlessly with the S4.
Anyway: to be conitinued...

 

have you done all the tweaking, (not only) NI recommends for audio applications?
knowledge base > tuning tips

 

The scratching test was not to say that scratching was the problem. What I am seeing is that when high quality keylock is on. the cpu load meter goes red very easily. It is very apparent when scratching. But it seems to stay still in eco keylock setting. Maybe this is just my system. Someone else should test this and post.

 

I can imagine the cpu load as the processor tries vainly to retain the same key while scratching is occurring.. the cpu equivalent of "wtf!" )

 

Yep

I agree mystic.

Maybe cue with the jogs has the same result via the s4.?