My OS and internal drive is pretty clean with only the required apps (no iPhoto, or other nonsense) and I don't keep old projects stored in it either. Been tracking into the iMac's internal HD for 3 years+ with samples spread out like this without any issue ever. I also run Reaper rewired in Pro Tools on the iMac to sneak in some more samples here and there. MIDI keyboard and audio interface on the iMac, recording MIDI tracks and monitoring the MBP audio with an aux track all in PT. Also, it's free! (if you have a macbook sitting around doing nothing, and two extra I/O channels on your interface) Routing the audio through Ethernet with VE Pro is even cleaner, but my way is super stable and I won't touch it until I'm forced to. Using the built-in OSX Ethernet network for MIDI (under System Preferences, Network), routing the 2-ch audio out of MBP through an attenuator > preamp > converters. Macbook Pro slave: 64bit Reaper (128 buffer) with many samples on ext USB3.0 HD. IMac master: 32bit Pro Tools (128 buffer) with some samples on internal HD and more on ext FW800 HD. Today, I'll be writing swampy rock stuff, so I don't need strings or synths.I won't activate those VEP instances, which keeps the load off my computer. I have my VEP instances grouped rock band instrumentation, strings, synths, epic perc, etc. In PT, I can keep a VEP instance disabled until I need it, which helps me keep working fast while saving some system resources. I don't work on dozens of cues a day.more like 3 or 4 a day, but I still find it extremely convenient to have my template up and running in the background while I switch between sessions.Īlso, you can have more than one instance in any given session. Works without a hitch.I'm on PT 11, so VEP helps me use VI's and plugs that aren't yet compatible with the AAX plug in format.ĭrBill said the same thing to me when I was considering this a while back. I keep new elements that are unique to the cue hosted in my daw (PT) and the main template in VEP. If you load your template in VEP and leave it there, you load once, and forget it. I suspect that could take up to an hour of your day or even more depending on how often you're hopping between cues. If you're working on a film and jumping back and forth between dozens of cues a day, if you host your library in Logic, you will have to load and dump gigabytes of samples every time you close and open a new cue. The biggest advantage of the slave approach for me isn't just 64-bit/more than 4G of data, but having a large template's worth of VIs loaded constantly so any project can haveįull orchestra, perc, etc, and I can use the host for loading project specific VIs/tempo-sync'd synths, etc. Once it's setup, you can save the config and load it easily later. And for a basic hosting system, it's really not a big deal to work with.ġ -Just add a duplex audio device (ASIO on PC), and use the output device.Ģ - Add midi input devices for however many midi ports you have/want to use.ģ - Add the VIs you need (Kontakt, Play,etc) and route a corresponding midi port to each.Ĥ - You can add various mixers to combine audio outs of VIs to run into the audio output device if desired. It isn't as intuitive as VEPro, Bidule can also be setup with some more complex midi processing, Both use almost no cpu on their own.īildule is a modular application - once you figure out the concept, it's easy to setup. unlimited) installs on your own computers. The advantage with Bidule is that it is relatively inexpensive (the "full" version is coming, and will be more, but it's only $95 currently),Īnd one license gives a single user multiple (i.e. I don't use the ethernet streaming for slaves with VEPro - hardware for audio there and MidiOverLan for midi, as with the Bidule slave. You get two licenses with VEPro, so you can run it outside your DAW on the host, and on a slave at the same time. The advantage over Bidule is that you can stream audio via ethernet, it's more intuitive, and it's a full mixer with the ability to load plugins easily on VI outputs, setup internal bussing, routing for multi-out VIs, etc. VEPro is fantastic - well worth the price. I use both VEPro and Bidule on different slaves (and VEPro locally on the host as well).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |