yurki

it's very nice I can observe a device id number and

a track id number. But what about parameters?

I'm just trying to find a way to make controlling a certain parameter

of a device easier. For now I have to manually set

the parameter number. But since you often don't know them, and counting them doesn't do it alway in case of ableton devices, I have to try each number out. While doing so, al my data is going to the wrong parameters and it gets a mess etc. It's just not practical and not fast enough.

what would be great is you press a button in your max device and then select a parameter of any device, and then something is automatically linked to this parameter.

Hi there,
it's very nice I can observe a device id number and
a track id number. But what about parameters?

I'm just trying to find a way to make controlling a certain parameter
of a device easier. For now I have to manually set
the parameter number. But since you often don't know them, and counting them doesn't do it alway in case of ableton devices, I have to try each number out. While doing so, al my data is going to the wrong parameters and it gets a mess etc. It's just not practical and not fast enough.

observe-selected-parameter

https://cycling74.com/docs/max5/vignettes/core/live_resources_abstractions.html

These abstractions are new for me, but very usefull stuff so it seems. the last, M4L.api.SelectParameter.maxpat, might be a good solution, but I have to try it out.

observe selected parameter