Because789

I'm working on a device which is supposed to send fixed values to one parameter of another device by pressing different buttons which are KEY mapped/MIDI mapped to a controller (

http://www.maxforlive.com/library/device/1657).

 It works as intended as long as you're not trying to record automation. Then the real mess begins (which is no surprise regarding how the device is designed right now).

1. I wasn't able to find a way to link actions of mutiple live.button and live.numbox objects together to one envelope. Live uses "Long Name" to identify and record a change and this parameter has to be unique within a patch. Is there a way to get around this limitation? In the example below this would mean, if you record automation, changes in both numboxes should end up in the same envelope. Is there a workaround for this?

2. The way I trigger the value right now (with a live.button, "Bang when transition from" set to both, see patch above) is ugly and of course Live doesn't record the value I want but an on/off change. I tried different approaches with live.tab (you can only assign the whole object and not the single buttons), with mapping the live.numbox itself (a button press sets the value of the box to 0/127) or using live.text (this looked like the most promissing but I couldn't get more then on/off recording out of it). Is there maybe an approach for this which I overlooked?

A different approach would be to make Live only record the parameter change of the target device and not of the m4l device itself. I don't think that's possible but I might be wrong?

I'm very close to choose a completely different road without using the Live KEY/MIDI mapping system, but I want to make sure that this is really a dead end and I'm not overlooking something. Thanks in advance.

I'm working on a device which is supposed to send fixed values to one parameter of another device by pressing different buttons which are KEY mapped/MIDI mapped to a controller (http://www.maxforlive.com/library/device/1657). It works as intended as long as you're not trying to record automation. Then the real mess begins (which is no surprise regarding how the device is designed right now).

2. The way I trigger the value right now (with a live.button, "Bang when transition from" set to both, see patch above) is ugly and of course Live doesn't record the value I want but an on/off change. I tried different approaches with live.tab (you can only assign the whole object and not the single buttons), with mapping the live.numbox itself (a button press sets the value of the box to 0/127) or using live.text (this looked like the most promissing but I couldn't get more then on/off recording out of it). Is there maybe an approach for this which I overlooked? 

I'm very close to choose a completely different road without using the Live KEY/MIDI mapping system, but I want to make sure that this is really a dead end and I'm not overlooking something. Thanks in advance.


Automation recording issues