bengt

i have a problem: building a very simple device that writes certain CCs into automation-lanes via numbox.

problem: as soon as these CCs (=the numboxes) are recorded and automated and i replay the automation,

i suppose the problem and its solution lies somewhere within the numbox re-receiving values

and i've been reading up on live.remote~ but don't know if it would help me (because i don't understand it:)).

can anybody help? is there a solution to this? thanks very much.

i have a problem: building a very simple device that writes certain CCs into automation-lanes via numbox.
problem: as soon as these CCs (=the numboxes) are recorded and automated and i replay the automation,
they get disabled. 

i suppose the problem and its solution lies somewhere within the numbox re-receiving values
and i've been reading up on live.remote~ but don't know if it would help me (because i don't understand it:)).

can anybody help? is there a solution to this? thanks very much.
here's a tiny patch 


circumvent-automations-being-disabled

It is not clear what you want to achieve?

 50 not the cc number and then you send the cc number to the live.numbox.

3) you grab the MIDI cc data from the channel input. Why not just mapping the live.numbox to cc with Live and record the automation of that parameter to the channel?

Maybe I totally miss the point but I don't get it ....

1) you are filtering cc value 50 not the cc number and then you send the cc number to the live.numbox.
2) you output the other cc values as a raw midi byte  (not as a note or cc value).
3) you grab the MIDI cc data from the channel input. Why not just mapping the live.numbox to cc with Live and record the automation of that parameter to the channel?

Maybe I totally miss the point but I don't get it ....
...


circumvent automations being disabled