Hi everyone,
while fiddling with my usual TouchOSC template, I thought it would be cool having Macro/PLE buttons that can be triggered via SysEx just by adding the relevant category/name in the Tag section on a button.
Here’s an example:
a button (“Macro Button Template” pictured below) is set with a Tag called “Transport/Set left Locator”, a category and command name chosen among the several Command Bindings already available according to the API Documentation.
Getting a SysEx out of TouchOSC and in Nuendo was easy enough - I followed pretty much the same method as for sending track names (a SysEx with F0, followed by “CMMD”, followed by the message itself, followed by F7):
Now for the tricky part.
I couldn’t do this with a custom variable because it’s missing the possibility to bind, so I did it with a TriggerPad.
I thought of making a function that, each time that it is called, “rewrites” the binding with the newly-acquired category and name into that same TriggerPad.
This doesn’t work - which is presumably because binding are only possible at initialization?
I just wanted a confirmation of this before I give up dynamically allocating and revert to mapping 3000 “invisible” TriggerPads instead.
The idea behind this is that a possible TouchOSC user could just, by way of a tag, have all the commands at the ready in his/her own templates, making for a more customised workflow.
Thank you to all that can contribute to shed some light 