Patrick

Is there a way to determine the deviceparameter id associated with a given encoder (i.e. knob) on the Push at a given time?

I'm making a tool for live performance, and ideally I would be able to tap an encoder and pass the associated deviceparameter id to the another part of the patch. (Using a mapper subpatch isn't really an option for the use case.)

I can't find a definitive guide the Push object model anywhere. Is there any function I'm missing that exposes current encoder associations to Max? Or is the Push API "dumb" enough to only provide information regarding touches?

I'm making a tool for live performance, and ideally I would be able to tap an encoder and pass the associated deviceparameter id to the another part of the patch.  (Using a mapper subpatch isn't really an option for the use case.)

I can't find a definitive guide the Push object model anywhere.  Is there any function I'm missing that exposes current encoder associations to Max?  Or is the Push API "dumb" enough to only provide information regarding touches? 

getting-the-device-parameter-associated-with-a-track-control-on-the-push-2

To anyone who stumbles upon this later- there is indeed a solution for this.

After days of searching for details of the Push object model, I happened to stumble upon the 

It let me see that the encoder objects (i.e. Touch_Control_X) have the property last_mapped_parameter, which is exactly what I was looking for. The patch works flawlessly now.

After days of searching for details of the Push object model, I happened to stumble upon the LOM Navigator about an hour after posting this.

It let me see that the encoder objects (i.e. Touch_Control_X) have the property last_mapped_parameter, which is exactly what I was looking for.  The patch works flawlessly now.


Getting the Device Parameter associated with an encoder on the Push