I think I've solved this - I've pushed a new version of Ubermap to Github, so you can download and reinstall it (you can just run the install script again, you don't need to remove the previous version).blakjesus wrote:That sucks... I guess ill have to stick with only editing the filter envelope from push. I have faith that someday a workaround will be made available.TomViolenz wrote:Just for your information: There was a similar problem with one of the Live devices (I think it was Operator and Shaper Amount and Shaper On with both being named Shaper)), where 2 different parameters had the same name for the API. In the end we could not solve this, and had to accept to only use one of them.
What I've done is made it so that it adds the index (i.e. position) of each parameter in Live to the mapping file, so e.g. for Diva, there are two parameters called "Attack", but one is the 34th automatable parameter and one is the 45th... so now, in the exported mapping, you'll get "34_Attack" and "45_Attack", so they are uniquely identifiable. You will have to do some trial and error to work out which is which, but it seems to be working for me (have only tried for 5 mins though so apologies if it doesn't!).
Existing config files (without the index prefix) should still be backwards-compatible, but if you want to recreate the mapping for a device with the new format, just delete the existing mapping file and reselect the device, and it'll export a new one.
Let me know how you get on!