Benjamin Cleek

I'm using Max For Live to add features to my midi controllers which do not already exist. I want my Max For Live object to be my MIDI controller instead of the actual controller. This way, I can use logic I've programmed to get my controller to behave differently instead of being limited to what the controller itself offers.

Live needs the controller to be active as Remote in order for Max For Live to receive the commanding CC's which will go through the switching logic in my patch and send new CC's which I would map in Live. Because of the conditions apparently needed for my M4L object to work, when I try to map the controller (my M4L patch, not the actual controller), the CC's from the hardware controller map instead of the CC's from my patch.

I'm trying to get my Nektar Pacer MIDI foot controller to behave like 3 loop stations mapped to 3 different looper objects.

My patch works fine as a standalone patch but I would love for it to work in my set. Anybody trying to do this or have any ideas?

If this works, I would love help on getting colors to work via sysex. I have the specs from Nektar.

The problem:
Live needs the controller to be active as Remote in order for Max For Live to receive the commanding CC's which will go through the switching logic in my patch and send new CC's which I would map in Live. Because of the conditions apparently needed for my M4L object to work, when I try to map the controller (my M4L patch, not the actual controller), the CC's from the hardware controller map instead of the CC's from my patch. 

Specifically:
I'm trying to get my Nektar Pacer MIDI foot controller to behave like 3 loop stations mapped to 3 different looper objects.

I'm using Max For Live to add features to my midi controllers which do not already exist. I want my Max For Live object to be my MIDI contro

Using M4L for deep MIDI controller logic