#OMNISPHERE 1 WON'T LOAD PATCHES HOW TO#

You then copy the instrument slot from these patches and use 'Paste as alias' in your new patch. Each of these patches only has one instrument loaded - e.g. Piano, Hammond, Rhodes etc., that are commonly used in most of my patches. For live work it makes little difference to the sound, but quite a difference to loading times and CPU usage. I have spent some time optimising the way that large VIs are utilised: VIs used include Keyscape, Omnisphere and Kontakt instruments such as Ravenscroft and Canterbury.

I don't have an issue with MS on a 2015 MacBook Pro on sets with over 40 songs using quite complex setups and splits. The one advantage I do find with MainStage is the ability to use an 'alias'. Again, good luck you play & write great stuff so you should have a setup that lets you concentrate on that and not on all this technical stuff! That's been my goal with my setup and while I've had a few bumps along the way, I would not trade what I have for any hardware keyboard!

#OMNISPHERE 1 WON'T LOAD PATCHES HOW TO#

I don't know exactly how to do this since I don't use MainStage, but I'm sure there are others here (and elsewhere) who do. Devnor in his post above has a good idea: separate instances of Keyscape active at the same time in your MainStage setup. You have power and flexibility but there is a cost to it. Because you deal with mixing different companies' hardware and software, it can sometimes be a drag to get things working the way you like. I've been doing it for a long time I started 17 years ago (!) with a Titanium PowerBook G4. I can only say that I, and a few others here, have laptops playing some great instrument plugins without issues. I can't help you much because I rarely play these other keyboards. It sounds like you're ready to give up on the laptop for gigs.

Omnisphere 1 won't load patches