• warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'nodereference_autocomplete_access' was given in /home1/chenetzn/public_html/max4live/includes/menu.inc on line 452.
  • warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_imagecache_menu_access_public_files' was given in /home1/chenetzn/public_html/max4live/includes/menu.inc on line 452.

Mapping Korg Kaoss Pad XY data to MIDI messages

4 replies [Last post]
monty_mcmont
Offline
Joined: 05/01/2010
Mapping Korg Kaoss Pad XY data to MIDI messages

Hey, this is my first post to the forum. I've been using Live for a number of years but I'm not very familiar with the finer details of how MIDI works, so please forgive any obvious ignorance on my part!
I'm trying to build a patch that takes converts touches on my Korg Kaoss Pad's XY area into MIDI messages. I'd then like to map these MIDI messages to control MIDI-assignable parameters on VST plugins and Live's built-in devices.
My Kaoss Pad is connected to my audio interface via a MIDI cable, and the patch ( http://ul.to/mzoo2v ) is loaded into a MIDI track that monitors incoming MIDI messages from the audio interface. (The patch works equally well with mouse clicks on the boxes of the jit.cellblock, so you don't need a Kaoss Pad to use it.)
My patch maps the XY information into an integer relating to each zone, labelled 1-4. When I select one of the zones, the patch outputs a corresponding MIDI message using ctlout. I want to map these messages to control parameters in other plugins.
The problem comes when, In MIDI map mode, I click on the parameter that I want to map but Live doesn't pick up the mapping - I don't understand why it doesn't! I'm probably doing something really obvious wrong, but I'd appreciate any help that you can give me!
Thanks in advance,
Monty

Anonymous

cant download the patch unfortunately

did you test that the messages are really being correctly send out of the patcher?
i read somewhere that audio effects rack are limited in that way that they cant send midi out, maybe thats the problem

imo, put the patch on a seperate midi channel, and use the midi out object that you have by default for sending the values, instead of the ctlout

negotiator
Offline
Joined: 04/16/2010

ah forget my last post, i was a bit confused lol

if i am right now, the midi that is send out is routed with lives track chain and isnt globally available

so your device would only have effect on the devices that follow it and on the devices that are located on a track you route the output of your midi track to (in the I/O section)

but this midi data will only be available inside these devices and will not be available for mapping things in live

the easiest workaround that comes onto my mind would be to route the output of the track to a midi port which isnt currently in use and then select the midi port you routed to as your REMOTE IN port in lives preferences

i hope that works and be sure to only receive data from your midi controller and not from all midi ins, as it will produce an infinte feedback of midi data (check I/O section of your midi track)

Anonymous

Thanks for the advice, negotiator... I think this patch needs to be a bit more complex than I thought!

I've decided to delve a bit deeper into the Live Object Model, and I'm going to do the mapping using the live.remote~ function. I'll upload it to maxforlive.com when it's finished...

recycledcity
Offline
Joined: 07/09/2010

How is progress coming on this? I'm not yet skilled enough in M4L to make a patch for this, but I have been thinking about it lately as it seems like it is plausible.

Has anyone looked at this patch? http://www.thecovertoperators.org/Max/MSP-Patches/pk-squared

I feel like some routing in it might be adaptable here.