Thank you. I notice in your signature that you use VE Pro 5 with C Pro 8. How do Cubase’s Rack and Track Instruments work with VEPro? Are they separate things or do they work together? I’m very intrigued by VEPro and is on my list of things to buy.
I have been making 2 templates. One with Racks and one with Tracks, mainly to see what works best for me. I love the Instrument Track approach more. For a few reasons. I can disable and Enable which ever track I want, when I want, and its very quick (and does indeed stop using RAM - it didn’t take long to use 16gb of RAM -bugger, I need more! A lot more haha!) to do so. Its also a lot simpler to automate each Instrument Track (for me). The main things that are a pain are the loading times of Projects (much faster when using Racks) and the Saving time of Projects. Am I right in thinking VEPro solves this problem as its essentially like Rewire, or an external rack that you connect to Cubase? Sorry If I have this wrong, and thanks for the advice. Its amazing all this stuff actually works really haha!
Jono[/quote]
I use vep for live conditions. (performing, not producing) Two people are connected with one system on a live condition and they really give a hit to the system, and it is thus a bit necessary to be sure that you are able to have a stable system. VEP is a server based system and is independent and very efficient. For example on a 1 hour 15 minutes gig i need 75 or something like that tracks to be loaded and active at all times, and what i really do not want is any any interference. Since VEP delivers audio to cubase, and thus the audio driver is not being compromised, this is ideal and has been the choice for me to go, certainly with V7 that has had quite some issues with spikes in the past. (that has been solved in 7.5.3), but still, if you look at my specs, i’m using not the most powerfull laptop on a stage. (but it is a nice unit) Laptops are weak in terms of performance, certaintly when you are having a lot of tracks active. So the Vienna server based solution is ideal for me.
The loading times: With 1000 or something like that instrument tracks (disabled) in my template with a simple 2,4 ghz i7 laptop, it takes less then 5 seconds to load a templatein V8. With Vienna, it takes several minutes to load for example 100 vsti’s. (but they are not disabled and active and that is f.e. 10 gig) With a second PC connected, i can go walking to the shop and buy something and return, before it is loaded. (let’s say several minutes )
I have to say i am busy for the moment to try to go back to cubase without VEP. Still have to see if this will be working, since the new workflow means redesigning the entire thing, and that will take some time. And i have a lot of good expectations of it. Since going the Vienna way also means that you have twice the amount of workflow and templates to deal with.
With V8 you have different ASIO2 settings. It comes a bit more close to VEP, but not all the way. But the ASIO2 is buffering things deeply in the backyard and saving a lot of resources. (and ofcourse not all the tracks are armed all the time for me)
It’s the same, more or less, i did in VEP where you can define buffer settings for each instance, but in CB it is one setting for all tracks.
What i do like with the new C8 approach is that when you have a massive amount of sounds, you can directly “print” them on to the main workflow window. So searching for a decent sound, once you have done the preparations, is reduced to very little time. In a live condition, that is not an advantage, but in a rehearsal environment that is a very good thing. So i still have to see how things go, and if there is any performance issue, ok, i drop it to a Vienna instance again. So having the choice is for me for the moment a no brainer. We’ll see.