maor efrati

for some time now I've been working with my band on a full live show that every song in the set has a max /Jitter based visual behind it.

I'm working this way because I didn't want all the patches to be open at the same time so max won't crush.

after every song I have to open the file of the new patch and close the last one myself.

this process so that I could open and close different patches with midi commands or something like that.

Hello, 
for some time now I've been working with my band on a full live show that every song in the set has a  max  /Jitter based visual behind it.

Evey song has a different visual idea, and a different patch as well.
I'm working this way because I didn't want all the patches to be open at the same time so max won't crush.
after every song I have to open the file of the new patch and close the last one myself.

I'm looking for a way to automate this process so that I could open and close different patches with midi commands or something like that.

Hello, 
for some time now I've been working with my band on a full live show that every song in the set has a  max  /Jitter based visual beh

working-with-different-patches-a-full-live-show

keep control patch on the top, and send open, close or whatever messages you use to load unload the patches.

For example send dispose message to thispatcher in each patch to kill it,

very easy
keep control patch on the top, and send open, close or whatever messages you use to load unload the patches.
For example send dispose message to thispatcher in each patch to kill it,
max open message to load next etc

poly~ can be helpful here, too, in case you need more than one patch running at a time. You can load multiple patches into poly~s (each with a single voice) then activate/deactivate them as needed.

Working with different patches - a full live show