I will buy Ableton Suite in an instant if I can be sure that it will work for this scenario. ![]() I would rather have a minor delay when switching from one patch to another while unneeded AUs are removed and new ones instantiated so that I don't have to worry about memory regardless of how many patches I have.Ĭan the above be done with Ableton? My problem is that much as I love MainStage conceptually, it is just not 100% stable and I always get nervous when I'm doing a live gig with my band that something will fail, and so everytime I change patch, I have to make sure that MS sent out all the program changes properly, that AUs in the current patch are actually working, and so forth. These mappings are also tied to a MainStage patch and so when I change the patch in MainStage, those devices will now send data elsewhere as desired.ģ - optional) How does Ableton handle multiple AUs when you switch from one patch to another? MainStage seems to instantiate all AUs needed for the entire concert and so it's very easy to run out of memory. I can either click on a new patch in MainStage or I can send a program change to MainStage which will consequently send out multiple program changes to devices as needed.Ģ) In MainStage, I can define devices (pitch wheel, knob, button, pedal, etc) and then map them (possibly changing the actual MIDI data they transmit) to various parameters of AUs and external devices. I realize that the feature sets are quite different but I'm trying to determine whether Ableton has the right functionality to support the two key features of MainStage on which I depend.ġ) MainStage supports multiple "patches", each patch of which contains channel strips each of which can be responsible for sending MIDI program changes to external hardware when the MainStage patch changes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |