delay when using cue points need help :)

delay when using cue points need help :slight_smile:

basically im using traktor and have a omni control and korg nanopad, the omni control is setup for typical mixing and the pad is for jumping between cue points, inspired by ean’s stuff, when i use his tracks from the we will rock you mix it plays them flawlessly so i can pretty much drum with them but when i use them on my own songs with custom cue points there is a slight delay between them. by the way i am using traktor pro on a netbook but i dont think the netbook should be affecting it since its only running traktor and nothing else and is upgraded to 2gb ram and overclocked as much as can be with powercable constantly in, using the sound card on the omni control which is perfect with eans tracks, so i dunno if its the type of mp3 im using, there all 320 format so i dunno, would appriciate any help at all thanks :slight_smile:.

cheers

thanks for the fast reply will try that then

what is your latency setting?

Is quantize checked? Sometimes you can get a delay because Traktor is playing everything in sync. If Sync is on both decks try turning it off and see if you still get the same delay.

…

in traktor its, 44100hz 2.5ms and then in the settings for the soundcard its clock rate is 44.1khz latency 128samples - 3.9ms / 25.6ms dunno what most of this means but its a lot better compared to using my laptop sound card cause there used to be a big lag with that

quantize

no quantize isnt on and i very rarely use sync cause it used to mess it up, i think it might be a problem with loading to the point in the track fast enough if that makes sence??

If your not scratching you can bump the latency in traktor up to around 10ms and everything seems to work fine.

…

tried the latency setting and its still the same its a bit more stuttery though

If Ean’s cue points work great but yours don’t I don’t think it’s a latency issue. Your cue points are probably not exactly lined up with the downbeat. Try zooming in on the waveform and moving the cue point a bit forward until you find EXACTLY where the downbeat is.

…

i know what you mean but it like only the first time i hit the cue point theres a delay then as long as i dont change cue point it will respond instantly but when i change the first time i hit the cue point theres a delay making cue juggling impossible on some songs

i have this (i believe) same type of problem.

if i am actively playing the track and try to make quick cuts to a cue point, i can really only get it to play on an 1/8th note, nothing quicker.
if i am not actively playing the track, i can get down to 1/16th, 1/32nd, something very very fast. only problem is, if i cue juggle then want to go into a loop or play, i have to hold the hotkeyed button down, then toggle play / loop.

i did use sync / quantize in the center area of traktor toggle settings, but with the track sync turned off.

i also notice with my cdj400s, quick cue shots are “less accurate” than with my apc40.

+1 on placement of cues and ‘sync’ related issues. if eans work and yours don’t it isn’t the laptop or traktor.

are the beatgrids accurate? and are the cues placed on or off the grid lines?

…

the cues seem fine, like its really unusual the first time i hit that cue theres a delay then when i hit it again i can do it as fast as my finger allows, then when i change cue theres a delay the first time i hit it again so i think its just the loading between cues so i dunno what that would be down to!

on the nanopad yeah?

fiddle with the velocity settings maybe with the korg editor software?

Could it be a cache setting? If you’re jumping around to areas of the track that aren’t cached anymore there could be a delay.

In the preferences try using a bigger cache.

…

ill give that a try but its only with certain songs so is there a way to compress songs for use in traktor??

what format are the ones that mess up?

…

cache is set to 256mb for decks a and b and i dont use c and d and the format is 320 mp3

where do you find that in pro? i can’t seem to spot… :confused:

..

its under loading in the settings and its the bottom section