[FR] Old Fashioned Live Set List - Step Fwd / Back With Midi or MMC

[Protocol_b]

Currently I host Mulab Plug inside such a live hosting app, but that introduces certain problems/limitations - I'd love to lose that shell and select my next tune directly from Mulab, with no mousing. My non-developer brain thinks it might be a fairly simple proposition...

[pljones]

A fairly easy and low latency way to switch projects:
- load multiple projects into MuLab as separate "Composer" modules
- stick a Note Despatcher into the Project Modular area and connect the main event in to the Note Despatcher
- set the Note Despatcher to "Keyed" ("Whenever a note-on with Special Key is received, the next output is selected")
- set the special key to a special key for moving to the next composer
- then have each composer trigger playback off a single note

Hm... how to actually switch between play and stop once you have the project selected... I'm not so sure on that bit.

[Protocol_b]

- you know, I conceived that exact approach! I love that dispatcher, and I do use it to switch 'scenes' inside my composer. But I thought about the overhead - each of my songs has a pretty large set of VST's, not always the same ones, and I'm concerned that the sum total of VST's used in an entire show might cause a problem with the overall Mulab environment. Maybe I worry too much? Good extra point you made as well - start/stop may be a challenge indeed....

[pljones]

You might want to look at the live matrix and what it offers (something I've not needed) - linking that to nested composers might be fun.

[fde101]

But I thought about the overhead - each of my songs has a pretty large set of VST's, not always the same ones, and I'm concerned that the sum total of VST's used in an entire show might cause a problem with the overall Mulab environment.

This is one of the main reasons for using one of the dedicated live performance apps. They keep the plugins loaded into memory so that they are ready at an instant when switching between patches, but put them to sleep if they are not in the current patch, in order to keep them from consuming CPU time; some DAWs can be set up to do this as well to some degree, but many do not handle it as well as the tools which are designed for the purpose.

[Protocol_b]

But I thought about the overhead - each of my songs has a pretty large set of VST's, not always the same ones, and I'm concerned that the sum total of VST's used in an entire show might cause a problem with the overall Mulab environment.

This is one of the main reasons for using one of the dedicated live performance apps. They keep the plugins loaded into memory so that they are ready at an instant when switching between patches, but put them to sleep if they are not in the current patch, in order to keep them from consuming CPU time; some DAWs can be set up to do this as well to some degree, but many do not handle it as well as the tools which are designed for the purpose.

Right, exactly - as said, I currently do use a live performance app but it introduces certain limitations in routing of MIDI and audio. At this time, it is also (in tandem with Mulab Plugin) having audio crashes, so it doubles the amount of analysis - which one is the problem (I believe it is LiveProfessor 2)? So I was just wishing I could cut the middle man out of the equation to simplify life. Then I only have to whimper to one developer.