Independent MPE control based on touch number


    Jul 19 2018 | 3:56 pm
    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.

    • Aug 10 2018 | 8:19 am
      For anyone coming across the same issue, the trick is to route prior to unpacking