Max for Live dial updating all instances of patch on separate Live tracks

    Apr 26 2017 | 1:57 pm
    I am very new to Max for Live and have been following some tutorials. I have created a M4L patch that uses [live.dial] objects to control parameters of a basic Max synth. My Live set has two tracks. Each track has an instance of the synth. I am finding that if I turn the dial in Live on track 1 both synth instances change with the setting. What I would like is for the dials to behave independently per track and not globally.
    Is there some kind of setting for the dial object I am missing? I have seen references to varnames in other forum posts, but I don't know enough to know where to look in the documentation.

    • May 03 2017 | 12:57 am
      I figured out how to resolve this issue in case anyone stumbles upon this post...
      My mistake was that I was using [send]/[receive] objects that connected the [live.dial] objects to a [send] object to avoid patch messy patch cords. The [receive] objects were elsewhere in the patch. My patch now does not use the [send] objects and the receives are replaced with [live.param~] objects.
      With this configuration, changing the dials in Live does not update all instances in the Live Set.
    • May 04 2017 | 2:07 pm
      alternatively, you can still use send and receive, just precede each name with 3 hyphens (---) and M4L will automatically limit their scope to that instance of the device
      [s ---dialout]
      [r ---dialout]
    • May 04 2017 | 2:21 pm
      Thanks for the clarification. That is very good to know for other situations.
      The [live.param~] works well in this case because it also removes the objects serving the [send] function, which cleans up the UI space when the patch is unlocked.