H BL

I'm very new to max for live and I can't figure out this :

I want to translate velocity to a CC value. so if I press a C3 pad with velocity 88, I want an output of CC60 value : 88 and so on for every note..

midi-velocity-to-cc

Thank you BROC for this quick reply ! It translate the midi messages but doesn't work as I expected. I thought I will be able to midi map the CC message to any parameter in Live but apparently doesn't work that way. You know why ?

(I'm trying to make sort of poly "aftertouch" on Push 2 using the repeat mode (at its fastest speed) which I want to use to control different parameters in Live according to the pressure on the pads)

Any help / infos on that topic is highly appreciated

(I'm trying to make sort of  poly "aftertouch" on Push 2 using the repeat mode (at its fastest speed) which I want to use to control different parameters in Live according to the pressure on the pads)

Any help / infos on that topic is highly appreciated


have a look at Packs > Max for Live Essentials > Max Mid Effect > Control Devices Midi > Expression Control

Yes I know this one. It does what I need (map velocity to anything in Live) but I need to have it 64 times (the number of pads on the Push). I tried to copy this device in a drum rack 64 times but the CPU is going crazy...

So what I would need to do is a single device that filter velocity according to the notes with 64 maps buttons..

How could I achieve that ? I don't know where to start..

Yes I know this one. It does what I need (map velocity to anything in Live) but I need to have it 64 times (the number of pads on the Push). I tried to copy this device in a drum rack 64 times but the CPU is going crazy... 

So what I would need to do is a single device that filter velocity according to the notes  with 64 maps buttons.. 

How could I achieve that ? I don't know where to start..


I guess a single device with 64 map buttons will basically give the same cpu problem.

Thx DOUBLEUG for the input. I do not know what you mean by "set the patcher arg to the desired pitch".. (sorry very beginner here)

I tried to copy 64 map buttons.. (they are not even working at the moment, I have to figure this out) and the CPU usage is going from 1 to 20% (in an empty live set, one midi track, no effects, no return tracks) and I'm still planning on adding a lot of effects, audio, and midi tracks.. (this is for a live act so I can't afford CPU overload..)

So I think the first patch that BROC posted (translating velocity to CC) would be much more CPU efficient but can someone explain me why I can't midi map it like every other encoder on my controllers ?

Is it because of the timing Live is accessing midi data ?

Maybe its better if I use a midi translator outside of Live ?

So I think the first patch that BROC posted (translating velocity to CC) would be much more CPU efficient but can someone explain me why I can't midi map it like every other encoder on my controllers ?
Is it because of the timing Live is accessing midi data ?

Maybe its better if I use a midi translator outside of Live ?


Midi mapping in Live works only for _external_ midi input. But you can simulate it with midi loopback, sending midi out from Live and back into Live over some virtual cable (for example IAC bus on Mac).

(midi) velocity to CC