Midi clock from traktor to control pad sustain

Discuss Lemur and share techniques.
Post Reply
tput73
Newbie
Posts: 25
Joined: 11 Mar 2013 13:11

Midi clock from traktor to control pad sustain

Post by tput73 »

Hi erybody!
how does one go about getting
Traktors midi clock signal to control the
length of sustain on a pad(controlling fx on)
thereby having fx on for x amount of bars
of a track and shut off in time?
Thanks for the continuing wisdom
Put
hakonandersson
Newbie
Posts: 5
Joined: 15 May 2013 12:04

Re: Midi clock from traktor to control pad sustain

Post by hakonandersson »

Hi Put,

Am very interested in knowing this also - did you ever get anywhere with your attempts? I'm just integrating the traktor midi > lemur side of things in my project, and would like to enable X (whatever it may be) for 4, 8 or 16 bars..

I've got the midi_clock sending his ticks in successfully.. now just need to interpret those to break them into beats and bars..

Cheers.
Softcore
Regular
Posts: 1613
Joined: 04 Nov 2012 08:34

Re: Midi clock from traktor to control pad sustain

Post by Softcore »

Midi clock ticks are 24 per quarter note. With that in mind set up a script that will execute every 24 ticks for quarter notes (beat), 2*24=48 ticks for half notes, 4*24=96 (bar) etc, etc.
tput73
Newbie
Posts: 25
Joined: 11 Mar 2013 13:11

Re: Midi clock from traktor to control pad sustain

Post by tput73 »

Still in the dark over here.
I can receive midi clock ticks
And show them in monitor object
however the value just increases, I can't
Figure out how to cycle as in a bar or measure.
Then applying this time as a condition
of a pads release, I'm perplexed.

T
Softcore
Regular
Posts: 1613
Joined: 04 Nov 2012 08:34

Re: Midi clock from traktor to control pad sustain

Post by Softcore »

example 1:
create a global expression - name it q (quarters)

Code: Select all

q = midi_clocks[2]%24
Every time a quarter note passes by, q will be zero.

So for example if you want a script excecuted after a quarter note you would make the script "on expression q, dropping to zero (dwon arrow)".

example 2:
create a global expression - name it b (bars)

Code: Select all

b = midi_clocks[2]%96
Every time a bar (loop) passes by, b will be zero.

So for example if you want a script excecuted after a bar you would make the script "on expression b, dropping to zero (down arrow)".

The above provide a way to script an action to turn "off" or "on" a pad. In order to calculate its decay value, you'd have to calculate the time between two subsequent 0s of q or b with an on frame script and then apply that claculated value to your pad's decay.
Softcore
Regular
Posts: 1613
Joined: 04 Nov 2012 08:34

Re: Midi clock from traktor to control pad sustain

Post by Softcore »

To say the truth, I havent been busy at all with these midi clock stuff - LFO studio in the factory templates appears to be very advanced and also "looks" the exact song position and whatnot. I think it will take some time to "de-code" what is actually going on but it appears to be very elegant and accurate.
tput73
Newbie
Posts: 25
Joined: 11 Mar 2013 13:11

Re: Midi clock from traktor to control pad sustain

Post by tput73 »

Oi!
I'm almost there I can feel it.
I got the global bar expression
In and it's a perfect bar judging by
my monitor object.
And the pad or custom button loops on and
Off in time, but its continuous.
How would one execute the on/off loop
just once? Or once pressed go through loop
and stay off until pressed again.
T

Ps thanks again for the wisdom, you really
should teach a course!
Softcore
Regular
Posts: 1613
Joined: 04 Nov 2012 08:34

Re: Midi clock from traktor to control pad sustain

Post by Softcore »

lol naaah, I dont think so really! There are other guys in here WAY more advanced in this scripting thing,. Probably Im just dedicating more time in the forums than others, thats all! ;)

As for your question, Im really starting to lose "touch" with what you are after. Send an example template over so I can see where you are at, and possibly help finish it! ;)
Post Reply