Automating Macro Variations

[todd_gochenour]

Launching Macro Variations via automation is not possible in Live. MIDI CC mapping to the variation's launch button seems to be a solution. I want to trigger multiple variations across several racks and devices all at once with a single event.

With Live 12 I've used loopMIDI (Windows) and IAC (Apple) as virtual MIDI loopback bridges that automate CC messages in dummy tracks to control Live transport and instrument selection. These external utilities don't function on Push 3 standalone.

Today I tested a solution for Push 3 Standalone that simply plugs MIDI Port 3 OUT (track) to MIDI Port 3 IN (track and remote) using a short 3.5mm TRS male to male connector. The dummy track routes to Port 3 OUT and multiple 1-beat clips have automation on MIDI CTRL to send a different 'Undefined' CC number. I can then launch the clip to send the CC to whatever in Live has it's mapping. I can place a dummy clip on a scene so the desired macro variations are triggered when the scene is launched.

Is this a novel approach? I haven't seen this technique discussed in the forum. I've seen the M4L Variations device which accomplishes the same by taking a snapshot of the track/project. I'm trying to utilize Macro Variations as the snapshot format instead. This approach seems more accessible to my workflow in Push 3 track view, since variations can be triggered with the jog wheel. (Would be nice if the play button highlighted the current variation like it does in Live.)

Standalone Push 3 doesn't have MIDI mapping functionality or Clip Envelope Automation functionality so configuration must be done in Live first and then transfered ro the Push.

Bonus functionality...a smooth quantized transition to the Macro Variation for extended drops and risers.

[todd_gochenour]

I have mapped CC 14 to multiple device's RAND function in the SELECTOR drum kit to scramble parameters of each device. I have added a Macro Variation called 'default' to each of these chained devices. I want to launch all of these variations simultaneously. When I map CC 15 to a second controller I get the message

"The selected controller conflicts with the previous mapping to 1 Kit Producer | SELECTOR Kit Producer | Selector Kit Producer | Recall Variation. Do you want to replace the previous mapping?"

Why can't I map Recall Variation to more than one controller?

[ecthroi]

this is really interesting if i'm understanding it correctly, not at my Push now...i guess there's no concerns w/ MIDI feedback in that routing structure?