Forums > MaxMSP

MIDI issues


electronicmess
May 17 2010 | 1:09 pm

I’m creating a patch for live performance which uses the matrix on my KP3 to control, 7 separate sliders which in turn control 3 different parameters and can also be armed to record live input. I’m using Gates linked to the other buttons on my KP3 to switch between these. Everything runs perfectly until I tap my Kaoss Pad matrix and the MIDI data of my new finger position is also sent through the gate (which is supposed to filter this out) to the last position of my finger. This is a big flaw, since my patch is supposed to record 7 different slices of audio, but every time I record a new slice, the previous slice is also recorded over due to the MIDI data being sent to both record buttons. I’ve experimented with delay to try and solve this, but have not yet fixed it. Any help is appreciated!

This is the MIDI section of the patch:

— Pasted Max Patch, click to expand. —

brendan mccloskey
May 17 2010 | 1:54 pm

I didn’t spend too long with your patch, but i had a slightly similar problem with the KP2, in that the pad would send a note-off message whenever finger-release was detected; i used [stripnote] to overcome this, in the following patch. I hope it helps. Could you perhaps strip your patch down to something a little less dense, showing only those elements which are causing the issue?

-- Pasted Max  Patch, click to expand. --

electronicmess
May 17 2010 | 2:22 pm

Thanks for the reply! I tried stripnote, but could still not overcome the problem.
Here’s a condensed version of the patch, with more explanation of the problem.

— Pasted Max Patch, click to expand. —

Thanks again!


Timo Rozendal
May 17 2010 | 3:27 pm

I don’t have my kp2 here, but it seems that you need to make sure that you always receive ctrl 12 first, you can use ctrl 92 for this which will tell you when the pad is touched

this might work for you:

— Pasted Max Patch, click to expand. —

Chris Muir
May 17 2010 | 4:33 pm

Without having a KP3 to test with I don’t know that this will work, but I made the patch a little more efficient, as far as the column select stuff goes: 



-- Pasted Max  Patch, click to expand. --

electronicmess
May 17 2010 | 6:03 pm

Thanks Chris, that is perfect!

My only problem now is that the number boxes are still sending bangs and causing anything I record to be overwritten, is there anyway of transferring your more efficient column select method to prevent the re-recording?
Here’s what I mean:

— Pasted Max Patch, click to expand. —

I promise this is the last problem with my patch! Thanks to everyone for the feedback.


brendan mccloskey
May 17 2010 | 6:29 pm

[onebang]?

— Pasted Max Patch, click to expand. —

Chris Muir
May 17 2010 | 6:31 pm

The problem is that the pictslider outlets were firing in the opposite order than you wanted. A trigger and an int swapped the order.



-- Pasted Max  Patch, click to expand. --

electronicmess
May 17 2010 | 6:35 pm

Thanks so much! Everything is now perfect. You have literally saved my life!

Viewing 9 posts - 1 through 9 (of 9 total)
Forums > MaxMSP