Mappable Traktor LFO (beatsynced)

You can easily apply a square, sawtooth, our triangular LFO to any mappable parameter in Traktor.

To do this with only modifiers requires a virtual midi cable like midi yoke be installed.


Set up a global modifier and map it to an unused button.

Have the button toggle the modifier between two values.

Map a beat phase monitor output.

Have the virtual midi cable bring the midi-output back into traktor and map it to the same button so that the beat toggles the modifier between two values.

Adjust the speed with the beat phase output settings (you can use multiple bpo to perform complex automation)

Map any on/off parameter to this button and it will cycle with the beat.

Map any variable parameter to this button with the control types fader/knob or encoder to produce smooth beatsynced automation of that parameter

For more control use the toggling modifier to restrict actions, or have another modifier count the beat cycles... Be imaginative.

Remember that Traktor can send a midi output for any modifier state, and each one of those outputs can be brought back in to cycle other modifiers/controls.

Note: with this you can make the FX change with the beat or automate the sample player to work like a step sequencer, or create a live mpc style beat slicer, and much more.



---
The beat slicer works like this...

Have Traktor play the track muted.

Set up beat phase output to cycle a modifier from 0-7 and then back to 0 so that the modifier counts out eight beats.

Set up a button to "load sample from track" into eight sample slots.

Use the LFO method to have traktor do eight beatjumps and loads. (very quickly)

Use the LFO to mute all the sample slots except the one "on beat" using the beat-counting modifier.

have all eight samples play on every beat.

Map a row of eight buttons to switch the mute on/off for each beat and correlate this to mute the normally unmuted sample that is playing "on beat"

While beat eight is ending on the sampler, use the LFO to do the beatjumps/loading of the next eight samples from the muted track deck to continuously "slice" through the entire track.

 

You're the weird midi guru guy around town I reckon

 

I'm digging this but think my bcd isn't

It simply change modifier values twice as fast as beat phase monitor kick's in. Can't seem to get it in time.

 

Try reading my "how to" create gears on djworx.com forums.

Using the engine I walk you through step-by-step should solve your problem.

 

I did read your post, I've read it at DJTT also, it's very cool stuff there, but I don't manage to bring the beat phase midi-output back into traktor by using "loopMIDI" virtual cable. If you can explain it a bit more how you get it to work then I could find this more useful.

I'm more about mappings, this MIDI protocols isn't really my field but I'm always happy to learn something new because I love it

I got two more clear modes in my last mapping (nine generic) that I'm hopefully finishing till autumn and will definitive name one mod by your name if I find the use of your gear engine in some creative ways like supercombos or some new stuff that come my mind if I start this cycle.

 

Make sure that under "Device Setup" the in-port is "all ports" and the out-port is the virtual midi cable. That gets the midi back into Traktor.

Have the output of the beat phase mapped to a button, and map a command to the same button.

Is it working now?

 

Same problem is present. I did setup for MIDI in/out ports like you said and M3 value just slap from 0 to 1 and back without any beat phase order (no sync though). I guess that M3 need to toggle the value every time beat grid come over needle position and both of the virtual gears need to scroll 0>7 it two beats till it cycles again, right? Could it be my controller is too slow for dealing with this stuff? I'm using bcd3000.

Here is what I did:
View attachment traktor LFO sync.zip

 

I can't open your file right now, but no, there won't be a full cycle. You dont even need the gears for this unless you are doing really complex automation. Delete M1 and M2, and just map an fx knob to the M3 button. is the button blinking in beat? Try different output settings and see what happens.

The beat phase monitor will always trigger M3 on beat unless the track isn't gridded properly.

 

I got it, finally. Instead of Controller range -0.5 and 0.5 I change it to 0 and 0. Problem was so simple but who would know that beat monitor treated same output behavior in different range options when routing back to traktor. When I normally set this range /0 > 0/, traktor can't send any information to LED so it's always off so I didn't expected LED to act properly in this range and never actually tried it.

I've mapped FX button as M3=0/value 0 and M3=1/value 1 and it blink on the beat. Even tried to mess with loop in/out ultrafine settings just to see how fast can make it toggle in traktor. Think that result is about 1/8 (four toggles in one beat count).

Gears are fully operational now. I'm all about testing new opportunities.

+1

 

Next put it on a knob and set the interaction to increase, and then decrease to get a triangle LFO, or use "dir" (direct value) and combine it with an inc/dec to get a sawtooth LFO. Use multiple beatphase output with random timing to get random "noise" LFO.

This works on any parameter.

Use a "fine" beat jump to get keylocked timestretching, compression, and reverse play .

Use multiple beatphase output on opposite duty cycles (one on the "up" beat and one on the "down" beat) to get "hyperspeed"

*note in "hyperspeed" the modifier will toggle so quickly that you might not actually see it change.

 

When give beat to any fader/knob:

Knob button inc/dec auto DJ
Knob direct switch 0-100%
Knob encoder direct switch 0-50-100%
Knob encoder relative automatic crossfades with sensitivity

I'll try to make 4 beat position first and do some more exploring.

Did you ever try to create some cartoon on lounchped this way?

 

I forgot to mention that you're going to need a relative interaction mode setting for the faders and encoders.

Next I would set up another toggling modifier on a usable button and condition M3 with that so that you have an On/Off switch for the LFO

Then I would set up all of the four of the different LFO types on four conditions of a modifier and set a row of buttons to button "dir" that modifier to the four different LFO type values, OR use modifier on a fader with the controller type fader/knob so that you can select the LFO type that you want applied.

 

When setting relative interaction mode to knob nothing at all happens and when I turn it to direct I got direct switch from 0 to 127 synced to beat.

LFO on/off switch is done.

This LFO automation remind me to DJM T1 feature for controlling FX amount.

http://www.youtube.com/watch?feature=endscreen&v=daxqxfpb2sc&NR=1 (9:14)

 

Did you change the sensitivity?

This is a virtual knob (like FX wet/dry) not a physical one, right?

 

You were right, my bad. It slightly increase or decrease parameter depend on invert option. Sensitivity work too.
---
First one is to see how many LED feedback can I get from MIDI out - all ports if I wanna keep LED's working in that mode of existing mapping.

I'm looking the way to start modifier loop as four values that provide the drive by beat monitor. This could be very useful feature in traktor. For controlerist and digital dj.

Thanks for sharing this.

 

I got modifier loop running.

Mapped beat monitor to toggle modifier 3.

Modifier loop:
Button 1) M1 button-inc/Mod Con M3=1 LED: 1-1
Button 2) M1 button-inc/Mod Con M3=0 LED 2-2
Button 3) M1 button-inc/Mod Con M3=1 LED 3-3
Button 4) M1 button-hold/Mod Con M3=0 LED 4-4

Mapped two more modifier 1 commands to M3 button:
M1 button-inc (loop starter)
M1 button-dir 1/ModCon M1=4 (reloop)

Beat position is working as four beat counter.

 

Everything is set. I created some simple FX automation and beat position using beat engine, it's cool.

Would be nice if you can post this four LFO types when you got some time.

 

Is this at all possible without using external software like loop MIDI or LoopBe?