Hot cue lag with VCI-100 (firmware 1.3) and Traktor 1.1.2.004

[Donald Groins]

When I use the cue/play button there's a bit of a lag. Is this a normal latency issue? Is there anything that can be done about it? I tried setting the "audio latency" in the audio set up window between 1ms and 5ms and it seems to lag either way. When I use the mouse pad on my laptop the cueing is instant. I'd love to be able to get that functionality with my VCI. Thanks!

[tokenasianguy]

It might be the way it's set up in the preferences.

I had that issue as well, and noticed that there was an option in the preferences section for that button to either start playing when you release the button, or to start playing when you press the button.

It might be that the lag time isn't actually lag time, but the time it takes for the track to start playing after you release the button, when you're expecting it to play once you press the button.

[DvlsAdvct]

On 1.1.2 you can't change that setting, it was rolled out in v1.2

Instead of using Cue/Play use Jump to Active Cue.

[Donald Groins]

Thanks for your help. I'm downloading Traktor 1.2 as we speak. Did you say that there is a setting in 1.2 that changes or fixes this "cue/play" button lag? Where do I find the setting and what should I set it to? Thanks again!

[DvlsAdvct]

It's in the preferences, just look for Cue/Play interaction (or something like that) and set it to instant

[Donald Groins]

Thanks again! Can't wait to try it. One more dumb question for the meantime-- Where is the "jump to active cue" button, on the VCI-100 or in Traktor? Is it labelled something else?

[sm00sh]

You might have sync engaged in which case Traktor quantizes when the cue.

[DvlsAdvct]

Yeah, that's an option too. If you have Quantize lit up in the volume section it will only work every beat, so there could be a lag.

Jump to Active Cue is an assignment in your MIDI mapping window. With the new Cue/Play setting it isn't necessary, though.