How to: Autoloop Hotcue-loops when selecting via MIDI

For each hotcue button add the command:

In > Loop Active > Assigment x (x being the deck) > Button > Hold > Is in Loop = 0

What this means is that Traktor engages 'ACTIVE' when you hit the button.

If this causes a loop, when you release the button, 'ACTIVE' stays on and the loop remains engaged.

If this doesn't cause a loop, when you release the button 'ACTIVE' is disengaged, and Traktor carries on as before. Traktor seems to exhibit the same behaviour as if the mapping were not there.

Works well for me with Maschine - give it a try...

l_p

 

can't do this with my s4?

 

Dunno about the S4 mate - haven't got one

 

it works but it works on every hotcue regardless of whether its a loop or not.

so active gets swtiched on any time you hit a hot cue

i guess i rather have it like this than not at all, but its still flawed
---
it works but now any hotcue regardless of whether its a loop or not activates looping

its probably going to lead to less mistakes than no loop at all, but its still flawed

i only want loop activated when its actually a loop... too much to ask for i guess "-)

 

Hmmm... works on my Maschine, maybe because the pads are set to 'Gate' ie. 127 on note on and 0 on note off?

 

if you map it like lethal_pizzle said it will work!

loop active | button | hold | assignment:deck > modifier condition: is in loop (deck) value: 0

 

I've given this a go and it does in fact work exactly how Lethal Pizzle said it does - 'loop active' will only come on if the hotcue you are jumping to is actually a hotloop; if it's a normal hotcue it won't come on. Well done Lethal Pizzle!

However, there are 2 slight snags to bear in mind with this customization... the first is that if you try to set a normal hotcue within the region of an existing hotloop during playback, regardless of whether that hotloop is active or not, the new hotcue you're trying to set automatically becomes an identical hotloop to the existing one.

The second is that if you try to resolve this by setting hotcues within the region of a hotloop whilst the song isn't playing, you will still find that jumping to this hotcue during playback will result in the hotloop this hotcue is within still becoming active. This will put you in a situation where, instead of being frustrated that you have to manually activate a hotloop, you'll become frustrated at having to manually turn it off...

Obviously whether or not either of these snags will affect you is entirely dependant on how complex you like to get with your hotcueing / beatjuggling etc, but it's something to just bear in mind.

 

yes, it seems to work now, i did exactly the same setup first time around and it wasn't working.... put it down to user error...

i must say though that it does show a certain amount of contempt for the customer not having this in by default and not having it on the onscreen buttons.

sure live you want to use an interface, but learning the software, just on the PC at home, the first thing anyone would tend to do, as i did 6 months ago is just try out all the feaures with the mouse.... and just as myself and apparently many other people on the forums did, assume that gives you a good impression of all the features.

i think the marketing dept. needs to talk to the development dept. and visa versa. bad marketing not showing sailent features like this in the default install, not to mention leaving the customer plugging in 8 x 4 hotcues to "in loop" = 0

Traktor should enjoy its monopoly while it lasts, because if they don't pull their socks up, someone is going to come along and put out something sharper and traktor will be introuble. Cubase enjoyed a virtual monopoly until Logic practically put them out of business overnight.... It was the same with the Apple Newton staff all leaving to form Palm, although Apple ultimately won.....but for 5-6 years Palm dominated......all it needs is a couple of guys from NI to make their own company and woof.... traktor is struggling.....

 

The reason Traktor is ahead of the game is because it can be set up so many different ways. I'm a bit of a geek though so I like fiddling.

Chuffed at the minute because I've worked out how to make my modifier buttons latchable...