KP3 Loop start cc# from DT

Hi there guys!

So as you guys may already know KP3 sync is a pain in the ass…

So I thought maybe sending a CC# message from DT to start the looper, with KP3 bpm fixed to same Bpm as DT may solve this problem.

Is this even possible? Have someone tried it?
How are you working around this?

Thanks!

1 Like

I did it a long time ago with another sequencer, I don’t have a Kp3 anymore. You have to use notes corresponding to pads.

I don’t remember what where the issues…

2 Likes

If you have it slaved to a clock it doesn’t really keep up as it should do.
Also is quiet hard to start recording exactly when beat hits… so programming it is much easier

Dont slave, just give the same bpm, then loop with kp3, on kp3. Doesn’t matter when you start your loop, as long as it is 4/8/16/32 beats long

1 Like

It works like a charm! The loops of the KP3 can be started by the DT. As said above, select note on #36-#39 on the first trigger to start the loops. I use one midi track of my DT and set the first trigger to start all 4 loops and set the last step to stop them. If you don´t use the last step to stop the loops, the next first trigger would stop them (you would start the loops every second time). Otherwise you could set the first trigger condition to 1st. When the clock of the KP3 is synced to the DT, the loop has the perfect length!

2 Likes

My Idea is to have that channel muted with a trigger in the first step and unmute it whenever I meed it to loop.

Is it necessary to stop the loop from recording?

This is how I do it. It´s not necessary to stop the loop from recording. Every trigger of the DT changes the state of the KP3 loop (if the loops plays - the note message stops the loop; if it is stopped, the note message starts the loop).

I use a channel with a trigger on the the first and the last step (otherwise, the loop would one play every second run, if I don´t mute the channel).