Programmatically Updating Resolume Destinations in the M4L Parameter Forwarder?

[danewhero]

Hello,

I’m trying to see if it’s at all possible to dynamically update the Resolume Destinations in the M4L Parameter Forwarder using ParamGrabber, or an external Python script sending OSC messages, etc?

I read some previous posts like the ones below:

Parameter mapping and Parameter Forwarding

Hello, I am using Live 12 and Arena 7. When I map something like an LFO tool M4L to a parameter and forward the automated parameter to Resolume, the mapped parameter doesn’t send get forwarded. Without changing any settings, if I move the knob manually, the changes get sent to Resolume. If I automate it by drawing the automation, they also get forwarded. Any ideas of what to do? This used to work in Live 11 when the mapped parameters would get locked.

But nothing is directly helping me with my situation.

Ideally, I want to have it so that when I change to a new MIDI clip in Ableton, then the M4L Resolume Parameter Forwarder will have an entirely new set of OSC commands in the “Resolume Destinations” fields.

Any suggestions on how I’d get closer to this goal would be greatly appreciated.

[Mattijs]

Unfortunately the devices in their current form don’t support this use case. With experience using M4L, it is entirely possible to make this happen though by opening the device for editing and developing this feature in a custom version of the device.

[danewhero]

I see. Thank you for clarifying this!