$Page Mapping $TargetName Mapping *Navigating to a parameter to map* This device lists the parameters of the device to its left. When choosing a parameter, it modulates it with a sine. To map a [live.remote~] to a device parameter, you first need to navigate to it. This example shows some patching to navigate the Live structure to find the device to the left of the Max device and iterate through its parameters. Mapping.png -> To know the position of a device in a track, [zl sub] is used to find our device ID among the IDs of all devices in the chain. -> If the mapped device is no longer to the left of our Max device, the parameter will still be mapped. Once set, the mapping of [live.remote~] is independent of what is in the dropdown menu. -> Whenever the device is moved or the devices in its chain change, the parameter dropdown is repopulated and if possible, the mapped parameter is restored in the dropdown menu. -> To map parameters at signal rate, you can use [live.remote~]. Note thought that although the mapping is continuous, the mapping is not necessarily sample-accurate for sudden changes: [live.remote~] interpolates the incoming signal according to its smoothing attribute. -> Storing the mapping once it is chosen is done with [live.object] because [live.remote~] will not give us back its stored id. To prevent the mapping being stored twice, [live.remote~] has its Use Persistent Mapping attribute set to 0. $Link Learn more about controlling parameters