Traktor Hot Cues Help

Home :: General Discussion :: Traktor Hot Cues HelpReply
Traktor Hot Cues Help
Posted on: 30.11.2013 by Trey Efraimson
Easy guys just a quick question about hot cues in Traktor,

The problem im having is when i set a hot cue on a beat in a track its not all ways hitting it on the beat,

So for instance ive got a 2 step drum loop - Kick Snare Kick Kick Snare and im setting the hot cue on the first kick but when im pressing the hot cue its missing the kick and the snare is the first beat i hear,

Hope that makes sense guys, and thanks for any advice given...........
Judi Sissel
02.12.2013
Originally Posted by makar1
Did you turn off Snap, Quantize, and Sync?
Try doing ^^^ That GetCarter. Haven't had those unticked in a while, but I remember it working pretty well.

I was digging around in the blog section, but for the life of me can't find an article posted by Dan White (I believe) that really helped with this. Pretty sure it was pretty involved, but non-the-less, addressed the problem and enabled you to keep S/Q/ and sync on... I believe... lol.
Trey Efraimson
02.12.2013
Originally Posted by DarioJ
I've noticed there is a latency lag (or compensation) if you're constantly mashing the same point. If you mash on the button too fast the cue point has the tendency to Jump before the original set point.
Yeah this is exactly what im talking about, So is there a way to stop this from happening?

Thanks for the help guys...........
Judi Sissel
30.11.2013
Originally Posted by makar1
That's usually due to Quantize or Sync
I figured as much but thought I'd mention for OPs sake
Alphonso Deitchman
30.11.2013
Originally Posted by DarioJ
I've noticed there is a latency lag (or compensation) if you're constantly mashing the same point. If you mash on the button too fast the cue point has the tendency to Jump before the original set point.
That's usually due to Quantize or Sync
Kellie Myrum
01.12.2013
Originally Posted by makar1
Snap is what locks your cuepoints to the grid, not Quantize.
Correct. Quantize is used for triggering cue point on grid markers.
Meg Reinoehl
30.11.2013
Originally Posted by happydan
Is quantisation turned on? Are your beatgrids set correctly?
If you're using beatgrids, make sure that you have them lined up on beat and that quantize enabled at the top of the screen.

If you're not using beatgrids, then make sure that quantize is disabled. This should allow you to enter your hot cues exactly where you want them to go.
Trey Efraimson
30.11.2013		Easy guys just a quick question about hot cues in Traktor,

The problem im having is when i set a hot cue on a beat in a track its not all ways hitting it on the beat,

So for instance ive got a 2 step drum loop - Kick Snare Kick Kick Snare and im setting the hot cue on the first kick but when im pressing the hot cue its missing the kick and the snare is the first beat i hear,

Hope that makes sense guys, and thanks for any advice given...........
Judi Sissel
02.12.2013
Originally Posted by makar1
Did you turn off Snap, Quantize, and Sync?
Try doing ^^^ That GetCarter. Haven't had those unticked in a while, but I remember it working pretty well.

I was digging around in the blog section, but for the life of me can't find an article posted by Dan White (I believe) that really helped with this. Pretty sure it was pretty involved, but non-the-less, addressed the problem and enabled you to keep S/Q/ and sync on... I believe... lol.
Alphonso Deitchman
02.12.2013		Did you turn off Snap, Quantize, and Sync?
Trey Efraimson
02.12.2013
Originally Posted by DarioJ
I've noticed there is a latency lag (or compensation) if you're constantly mashing the same point. If you mash on the button too fast the cue point has the tendency to Jump before the original set point.
Yeah this is exactly what im talking about, So is there a way to stop this from happening?

Thanks for the help guys...........
Judi Sissel
30.11.2013
Originally Posted by makar1
That's usually due to Quantize or Sync
I figured as much but thought I'd mention for OPs sake
Alphonso Deitchman
30.11.2013
Originally Posted by DarioJ
I've noticed there is a latency lag (or compensation) if you're constantly mashing the same point. If you mash on the button too fast the cue point has the tendency to Jump before the original set point.
That's usually due to Quantize or Sync
Judi Sissel
30.11.2013		I've noticed there is a latency lag (or compensation) if you're constantly mashing the same point. If you mash on the button too fast the cue point has the tendency to Jump before the original set point.
Kellie Myrum
01.12.2013
Originally Posted by makar1
Snap is what locks your cuepoints to the grid, not Quantize.
Correct. Quantize is used for triggering cue point on grid markers.
Alphonso Deitchman
01.12.2013		Snap is what locks your cuepoints to the grid, not Quantize.
Meg Reinoehl
30.11.2013
Originally Posted by happydan
Is quantisation turned on? Are your beatgrids set correctly?
If you're using beatgrids, make sure that you have them lined up on beat and that quantize enabled at the top of the screen.

If you're not using beatgrids, then make sure that quantize is disabled. This should allow you to enter your hot cues exactly where you want them to go.
Evalyn Voges
30.11.2013		Is quantisation turned on? Are your beatgrids set correctly?

<< Back to General DiscussionReply

Copyright 2012-2023
DJRANKINGS.ORG n.g.o.
Chuo-ku, Osaka, Japan

Created by Ajaxel CMS

Terms & Privacy