zbtn

Is there any way to split incoming mpe data so that each 'touch' has independent control parameters? Essentially providing separate and distinct controls for each finger placed on for example, a ROLI seaboard.

I am aware of the mpetrack object which does something similar. However it's control parameters are grouped together in a way where all its control values are updated based on the touch number. As the touch number is constantly being updated, the control values can jump rapidly from one extreme to the other.

I have thought of a few hacks which could resolve this issue, but am looking for a more elegant solution.

Is there any way to split incoming mpe data so that each 'touch' has independent control parameters?  Essentially providing separate and distinct controls for each finger placed on for example, a ROLI seaboard. 

I am aware of the mpetrack object which does something similar. However it's control parameters are grouped together in a way where all its control values are updated based on the touch number.  As the touch number is constantly being updated, the control values can jump rapidly from one extreme to the other. 

I have thought of a few hacks which could resolve this issue, but am looking for a more elegant solution. 

Is there any way to split incoming mpe data so that each 'touch' has independent control parameters?  Essentially providing separate and dis

independent-mpe-control-based-on-touch-number

For anyone coming across the same issue, the trick is to route prior to unpacking

Have you noticed this only works until you until you touch another note? If so, have you found a solution to this problem?

This looks like a bug to me. Can you imagine any reason mpetrack shouldn't continue to pass pressure and slide values for active touches even after new touches are recognized?

It's a shame the MPE documentation and the range of examples are SO limited.

Have you noticed this only works until you until you touch another note? If so, have you found a solution to this problem?

This looks like a bug to me. Can you imagine any reason mpetrack shouldn't continue to pass pressure and slide values for active touches even after new touches are recognized?

Independent MPE control based on touch number