Then it would not really an alias anymore. Personally I don't think you will see the change you are asking for. I would at least like the choice of having new plugins in memory for each patch vs changing their settings on patch change. up to 20 second delay when changing the settings of an instrument plugin. Memory is a major bottleneck for me when using Mainstage and this feature would make a huge difference for me as in my performance environment it is often possible to tolerate a e.g. And using channel strip aliases at the moment is not as useful as it could be as plugin settings are not easy to change when a patch changes. If you have lots of patches, you will see that memory usage increases really fast with Mainstage. plugin settings which may be multi-timbral), A and B, I would like the choice whether to have two instances of Omnisphere in memory (one for sound A and one for sound B) vs changing the sound of a single Omnisphere instance (which may entail a delay due to sample loading). I was just interested if others also wished to save memory by being able to change sounds on a channel strip already loaded into memory rather than needing *a new channel strip in memory for each sound*.įor example, if I have two Omnisphere sounds (i.e. Thanks, I had already submitted my request there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |