MIDI Kinetics Forum

Hi, I have a bunch of posts on here but no answers yet so I keep trying alternative methods to solve my issues. In the process of trying to figure out a workaround I stumbled across what I think is strange behaviour. I use OSCulator with my iPad running Lemur and I have been using Multi-pads for several different reasons. I also use a Midi Monitor app to monitor all MIDI I/O events.

What I noticed is, after creating a Multi-pad, engaging it so OSCulator sees it, and then assigning each pad to a MIDI CC, every MIDI CC from each Pad in the Multi-pad sends data, even though I am only triggering one pad at a time. Is this normal? I feel like it renders the Multi-pad useless as the individual use of each pad is not an option. In OSCulator, when the Multi-Pad shows up, there is a single line that represents the whole Multi-pad and, if you unscroll it, there is a line for each individual pad. I have tried all different sorts of combinations including assigning each pad a MIDI CC in it's individual line while un-enabling the Main Multi-pad line. Despite that, any pad triggered will send it's data and every other pads data too.

Is there anyway to prevent this from happening? I am using the Multi-pad to change tabs in a container. I am trying to setup Ableton so it can send midi data to OSCulator, which can then send that data to my iPad (Lemur) to remotely change the Container tabs.

Any Ideas?

Prokat99 wrote:Hi, I have a bunch of posts on here but no answers yet so I keep trying alternative methods to solve my issues. In the process of trying to figure out a workaround I stumbled across what I think is strange behaviour. I use OSCulator with my iPad running Lemur and I have been using Multi-pads for several different reasons. I also use a Midi Monitor app to monitor all MIDI I/O events.

What I noticed is, after creating a Multi-pad, engaging it so OSCulator sees it, and then assigning each pad to a MIDI CC, every MIDI CC from each Pad in the Multi-pad sends data, even though I am only triggering one pad at a time. Is this normal? I feel like it renders the Multi-pad useless as the individual use of each pad is not an option. In OSCulator, when the Multi-Pad shows up, there is a single line that represents the whole Multi-pad and, if you unscroll it, there is a line for each individual pad. I have tried all different sorts of combinations including assigning each pad a MIDI CC in it's individual line while un-enabling the Main Multi-pad line. Despite that, any pad triggered will send it's data and every other pads data too.

Is there anyway to prevent this from happening? I am using the Multi-pad to change tabs in a container. I am trying to setup Ableton so it can send midi data to OSCulator, which can then send that data to my iPad (Lemur) to remotely change the Container tabs.

Any Ideas?

There is no object called Multi-pad. Do you mean the Pads object? The messaging system in Lemur is based on arrays, the x variable is an array which contains the state of every single cell in the Pad object. If you want to extract or monitor a single value, there are many ways around this with custom expressions, Custom MIDI or even scripting. Have a look at the following example for the User Library, it might be exactly what you're looking for: http://liine.net/en/community/user-library/view/152/

Kind regards,
Nicolas