Some larger EWQLSO samples go to another bus. If figuring it out within Mainstage wreaks havoc with your channel strips, doesn't defeat the purpose? Isn't Abelton way more stable in this regard? (I don't know, just starting to use it, ideally in conjuction with Mainstage.) What I'd ideally like to do is figure out the best low CPU way to outside plugins. Any of you guys use it? Is it worth getting? When you say VEP, you mean Vienna Ensemble Pro? That looks like a better, albeit more expensive solution then Bidule. I like the idea of eliminating Soundflower from the chain as I am dubious about it's stability. Maybe the best way is to set up heavy load plugins with both formats (with Bidule + Soundflower and without) and do a shootout. It sounds a little tricky and makes Mainstage rouitng hairy with all the additional auxs. I am curious about your idea to use Alaises in pairs. My gear is in my signature - MacBook Pro, Intel Core i5, 2.5 GHZ, 8GB RAM, 256 SSD, OSX 10.8.4, Motu Ultralite-mk3 hybrid. He didn't even bother to close songs that had already been played. They were small, loaded in no time between songs. Oh, let me add something I saw Thomas Dolby do live - a Logic file per song. I'd get 16GB RAM if you're doing a lot of sample-based stuff.Īgain, I'm not going to tell you not to proceed - if you have lots of time to spend then great! Besides, there actually are reasons to do what you're trying to do (in my case Omni remote app via iPad). SSD for your system and apps disk is fine. I think I've asked this before, but is your kit currently what you have listed in your signature? an i7 gives you 4 more cores. My next move is SSD for samples (Samsung makes a really cheap 1GB SSD). It all works quite well and right now, I'm not anywhere near being CPU or memory bound. I'm running a 16GB rMBP, and I run lots of instances of Kontakt, Omni, Ivory. In the Omni case, I think Eric P has said he's done some live rig setup stuff for Herbie or Chick that is amazing, but it's not like that's been shared. Has made me look at VEP instead, partly because in my opinion, it seems more specific to just being the best surrogate host tool w/o trying to be a Swiss army knife. Seems it's still pre-v1.0 and I don't understand their licensing offer either. I'm dying to be able to use Omnisphere's TR remote live, only with multiple instances of Omni throughout a concert - the remote app doesn't know which instance of Omni to connect to, which kind of sucks, as I have to parameter map a bunch of stuff that's already in a ready-to-use iPad app.
#Plogue bidule send program change signal Patch
I want to see if making these patch busses works, or works better, but have been laid up for a while (back surgery). I add an audio channel strip (not aliased) in the patch that "picks" up the audio from the bus where Ivory is sending to, and EQ, effect, transpose (octave shift) away, no prob.
That gets pasted as alias on any patch requiring a piano. I use the Steinway samples, but output to a bus. Using Ivory pianos all over the place, different EQs, mappings, layers per patch, but with only a single instance of Ivory itself. Yes and no regarding what you can change on one alias and it affecting all instances of the aliased strip. I suspect the ins from the Motu are confusing Plogue. I used this technique before with my previous soundcard (Apogee One) and it worked great. I've got my audio in in Mainstage set to this device as well.įor some reason any ins from Plogue to Mainstage past 1-2 are not registering in Mainstage. I've called this device "Plogue+Motu to Mainstage". I've created an aggregate device with soundflower that I've setup as my audio out from Plogue. I'm trying to add an effected vocal into live situations and I am using my new soundcard to do so, the Motu Ultralite. This also allows me to take advantage of Kontakt's multitimbral capabilities and work around a midi loop issue created by the IAC Driver. I've been using Mainstage 3 in conjunction with Plogue Bidule to conserve CPU usage. I'm trying to do something a little tricky and can't seem to figure it out.
0 kommentar(er)
