Copying Interfaces in Lemur with new name
Posted: 12 Sep 2014 05:40
Hi All,
I am working with Lemur on an iPad 3 for controlling PureData on MacBook Pro OS10.6.
I have several copies of a drum module in PureData that are identical except for the fact that each of their parameters listen to an address which has the specific drum name in it.
For example, I have Drum a, Drum b, Drum c... etc, so the amplitude envelope of Drum a will respond to the parameter Drum-a/AmpEnv, whilst Drum b would respond to Drum-b/AmpEnv.
Therefore in lemur I want to copy the whole interface for Drum a and rename it Drum b. However, on Lemur I would then need to go through each and every parameter address, changing the 'a' to 'b'. This is totally impractical because if i later make any changes to the module, I'd have to make them in every instance of it.
Instead, I'm hoping there's a way, similar to PureData, where I can program all the OSC addresses to reflect the interface name change, so that the 'a' in drum-a/AmpEnv will be supplanted by a 'b' when I rename the interface to Drum B.
Can anyone help here?
Another issue I found is that it doesn't seem possible to have more than one object of the same name, even if they are contained within different interfaces, so when I copy Drum a to Drum b, the AmpEnv becomes AmpEnv2. I tried changing it back to AmpEnv but it then changes to AmpEnv3!
I don't understand this logic because if you are addressing a parameter/object contained within another container, it is necessary to include the address of the parent first (which is logical), therefore it should not matter to have two objects of the same name within two different containers.
Brett
I am working with Lemur on an iPad 3 for controlling PureData on MacBook Pro OS10.6.
I have several copies of a drum module in PureData that are identical except for the fact that each of their parameters listen to an address which has the specific drum name in it.
For example, I have Drum a, Drum b, Drum c... etc, so the amplitude envelope of Drum a will respond to the parameter Drum-a/AmpEnv, whilst Drum b would respond to Drum-b/AmpEnv.
Therefore in lemur I want to copy the whole interface for Drum a and rename it Drum b. However, on Lemur I would then need to go through each and every parameter address, changing the 'a' to 'b'. This is totally impractical because if i later make any changes to the module, I'd have to make them in every instance of it.
Instead, I'm hoping there's a way, similar to PureData, where I can program all the OSC addresses to reflect the interface name change, so that the 'a' in drum-a/AmpEnv will be supplanted by a 'b' when I rename the interface to Drum B.
Can anyone help here?
Another issue I found is that it doesn't seem possible to have more than one object of the same name, even if they are contained within different interfaces, so when I copy Drum a to Drum b, the AmpEnv becomes AmpEnv2. I tried changing it back to AmpEnv but it then changes to AmpEnv3!
I don't understand this logic because if you are addressing a parameter/object contained within another container, it is necessary to include the address of the parent first (which is logical), therefore it should not matter to have two objects of the same name within two different containers.
Brett
