Of (Hot)Cues Loops and Jumps

Hi, I'm having problems in TSP 1.2.2 using the standard Faderfox DX2 setup where the cue/loop move buttons only move the cue point. How do I set it to move the loop instead? Is it something to do with the modifiers? That part of the mapping system isn't very friendly.

 

+1 on this unless anyone has come up with a way around this (which, if that's the case, please let me know). I can also confirm that johnnycoombes' solution activates a loop when that may not be the desired result (i.e. when triggering a cue as opposed to a loop).

 

quick question,

can't figure out how to store cue points without
mapping them on quick acces buttons (1, 2, 3...8)

thanks
---
quick question

how to store cue points without mapping them on quick access
buttons (1 2 3 ..8) in TPRO?

thanks

 

Cue/Loops | Cue Set + Store

MIDI Command Finder:
www.traktorbible.com/en/midifinder.aspx
see section "Advanced Deck Panel, Cue View"

 

chronological order?

this has been driving me a bit crazy.. but is there really no way to re-order the number sequence of cues?

when beat gridding, i go in and find the first downbeat to set my grid. This spot now occupies hot cue #1

but then if i add points PRIOR to that, rather than traktor renaming them sequentially, it does it in the order you set them.

is it just me or does this seem assbackwards?

if im looking at my midi trigger pad, my mind wants to navigate from left to right.. but as it is, i have to remember that my 4th pad might be cue #1 in fact

am i missing something?

thanks

 

You're not missing anything. It's a PITA. You can remap the cues (use the Map button) but it's far from automatic or easy. People have been asking for a way to at least chronologically order the cues automatically, but there's no indication that we'll see that any time soon.

 

man. with how complex timecode software can be, you'd think something as basic as this would be cake. probably just an oversight. but a HUGGGGGE one

 

what i do is add a cue on the first beat, then go back to the first "beat"at the start of the track, when the cue is at that point, delete all cues and create cue 1 where you are pointing, then it should be easy to add cue 2 at the first kick. doesnt take that long.

 

No one is saying there isn't a workaround. It's just that this seems like there should be a pretty straightforward way to address this and make it a whole lot more efficient.

 

I honestly cant see a problem with the way it works at the moment. You just manage your cue points better

 

I have scanned the whole 9 pages thread, sorry if this has been answered. I have searched in the forum, searched in the manual, and asked other forums about this.

So far it seems this is not possible in traktor, which is really a shame.

I want to set a loop and then jump to a hot cue and move that loop to that hot cue.

Example:

I set a 4 bar loop. Then I'd like to have a 4 bar loop in a hot cue in different position where my actual loop is.

Logically, at least to me, I would simply jump to that hot cue and still have a 4 bar loop but starting where the hot cue is. Because in my way of thinking I don't want a certain portion of audio looped, I want whatever I'm playing looped.

When I:

1) set a loop
2) jump to a hot cue (not a loop)

The loop stays where it was set. As I see it that is useles. Why? because:

1) I can't go to a hot cue and loop it on the fly unless is a stored loop
2) I can't go back to where the loop was set unless the song eventually reaches that point.

Why would I want to do that? Well for example to set a loop at certain part of a song (a hot cue) of a certain size that I have decided in the fly in the midst of a live performance.

Torq does it that way, and I think serato too. It's the most logial way in terms of dj thinking. Each crowd and session is different, and ideas flow...

I have seen the loop move, to move the loop x beats forward/backward, but that is not what I want.

I want to be able to set a loop and that loop size will follow the play head in my jumps between hot cues until I deactivate the loop.

Is this possible?

 

Well it took till the last sentence before I understood what you were asking for but in short no it is not possible in Traktor. You need the notion of an unlocked / locked loop
and Traktor does not support those semmantics, for better or for worse.

Phil

 

I know that this slightly fiddly, but could you not press the 'loop-in' button immediately after pressing the hotcue button? And then just follow that up with the 'loop-out' button at the desired point?

Its not ideal but would still achieve what you're after.

 

Hm, you could do the following:
When pressing the midi-button for a hotcue, combine it simultaneously (spelling ok? *g*) with a 4-Bar Loop. Maybe only in conjunction with a Modifier.
That way you always should have a 4-Bar Loop at your current hotcue-position.

Hope I didn't make a logical mistake, can't test it right away @ the office ;-)

 

Hmmm that's not a bad idea at all!

A modifier, so that when I press the hot cue it set also a loop of the desired size. Why not?

Will try it in the next days!

 

Yep, that would be my approach. I just configured my midi device that way and it works quite nice.

 

Hello! I'm having problems in Traktor Pro with deck B getting hotcue commands. Deck A is working as it should, i.e. with the track stopped, pressing a hot cue button will only play the track from that point for as long as I hold down the button.

On deck B, when the track is stopped, pressing a hotcue button will start the track playing from that cue point (if I let go, it is still playing.) and also it won't let me select the same hotcue over and over. example: if I have just pressed hot cue 1, and it's playing from that point, pressing hot cue 1 again does nothing. pressing hotcue 2 will jump to cue point 2. So I can do 1-2-1-2 but not 1-1 or 2-2.

I've rechecked my controller mapping over and over and over. The Mapping for deck A is EXACTLY identical to deck B. yet deck B is doing all this weird stuff.

Anyone have ideas?

 

Well. I deleted everyother Deck B mapping, in hopes to solve whatever was interfereing with my hotcue on deck b. It still didn't work! Select/set + store Hotcue 1 and 2 were the only mapping data for deck B, and the hotcue was still being screwed up.

So I created a new generic midi device, with my xponents in and out port setup.

I make the same commends.. "select/set + store hotcue" 1 and 2. Now it works perfectly. wtf? oh well, it works!

I checked my xponent with midi monitor and the buttons on deck a side and b side both put out the exact same output, one in and one out, when i quickly tap the buttons. So this was not a weird hardware problem.

I'm using an xponent, traktor pro 1.2.1, macbook, osx 10.5.8, 4gb ram.

 

There was for sure some settings-sideeffect active. maybe some old modifier setting interferring.

 

Yeah it has to be. but I deleted all modifiers to be sure, and my mapping is pretty simple for now, only deck a and b. I deleted or reset everything related to cues/loops on deck B, inputs and even outputs.

Some other weird things started happing after i loaded HolyCT's Tsi file (2.1a I believe.) I think it's possible that Tsi was for 1.2.2 and not 1.2.1 and changed something that I can't see in 1.2.1. I would upgrade to check but I am using my boy's computer and contoller.

Oh well, If someone else has this problem we can figure out what it was.

One last note on this problem before I shut down discussion: when pressing a hotcue trigger on deck B, the "CUE" button stayed lit up even after releasing the button, so I think Traktor thought I was holding the button when I was not. I checked that mapping was set to "hold" and not toggle or direct. Hold was actually the only option anyway for a hotcue trigger. And like I said, midi monitor reports that the button was physically fine.