Building a live-set: Question about preset automation/program changes (solved)

[MOROSFOLD]

Hola,

I'm trying to build a live set for a gig. I've done it before but I've always had issues with managing CPU. The way I've done it before is to build tracks in separate groups and move through my set that way. Because this way of doing it uses a lot (LOT) of tracks, with at least one or two VST's like Diva running per group. The total of groups/tracks in my live-set was about 12, which adds up to 24 instances of Diva in one project, and then there's still all the other tracks of course, so it's very challenging to keep CPU at a manageable level like this.

Now I was starting a new live set and was thinking of a way to slim this down drastically. I was wondering if it is possible to automate preset selection for a VST? This would really solve all my problems at once, here's an example:

Example:
Track 1 has Diva running with "Preset 1" on clip 1
Would it be possible to automate the preset selection for track 1, clip 2 to be "Preset 2"?

If this is possible I could reuse the same instance of Diva instead of taking a new one and therefore using more CPU.

[pottering]

https://www.ableton.com/en/manual/clip- ... ram-change

Besides that there are M4L devices. Some plugins may allow automation of preset browsing.

[MOROSFOLD]

Ah great, thanks for pointing out the documentation!

Do you know the names of any of these M4L devices by any chance?

[MOROSFOLD]

I found what I was looking for thanks!

For future reference:
M4L device: https://maxforlive.com/library/device/4 ... am-changer
DIVA user guide page 10: https://uhedownloads-heckmannaudiogmb.n ... -guide.pdf
Ableton documentation: https://www.ableton.com/en/manual/clip- ... ram-change