Guy Rowland
Senior Member
Ah good to hear - sounds like things are heading in the right direction at least.
Why does it have to be one or the other? I'm building a Cubase template that has both VE Pro tracks and Cubase disabled tracks. If I had a slave or multiple slaves I would go all VE Pro.Get rid of VEP in lieu of a disabled track template and save yourself boatloads of stress and unnecessary confusion...
Well for me it means not having to mess around with midi tracks whatsoever and having separate audio and midi tracks for every single instrument. Having a clean mixer without millions of sends coming back from VEP. Being able to automate my instrument track instead of finding the audio return and automating that. Too much complexity for my blood, I'm a simple man...Why does it have to be one or the other? I'm building a Cubase template that has both VE Pro tracks and Cubase disabled tracks. If I had a slave or multiple slaves I would go all VE Pro.
Well for me it means not having to mess around with midi tracks whatsoever and having separate audio and midi tracks for every single instrument. Having a clean mixer without millions of sends coming back from VEP. Being able to automate my instrument track instead of finding the audio return and automating that. Too much complexity for my blood, I'm a simple man...
But for me I don't even see any midi nor audio tracks until I enable the tracks I want and then it's only a single audio track per instrument and dirt simple automation. With VEP you still have to stare at and deal with untold number of midi and/or audio tracks as they are always active. I only see what I've enabled period plus my groups and sends which are separated with visibility agents.To each his own. But it doesn't have to be so complicated once you get it set up.
I just click off the visibility of the MIDI tracks and then it's one audio track per instrument.
Do you have any plugins in Cubase? If you have some heavy plugin chain in any of your tracks/buses, that could be the reason.I did when 6 One of my cores is STILL doing much more work compared to the others, but the GUI in VEPro is stable and there is no crackling, so I got that going for me at least.
With apologies to the OP for drifiting off topic - I think yours is a perfectly valid and sensible approach, InLight-Tone. The simplicity is very appealing.
The most important thing for anyone making a decision on which way to get themselves organised is to have a good and realistic overview of what the compromises are in the different methods. For a large monotimbral Cubase disabled template, it’s primarily the poor CPU performance in Cubase, a wait for each instrument to load, massive project sizes (which multiply in autosaves and cue versions) and long save times. None of these are deal breakers for everyone necessarily, and if you can live with those it’s a great option.
All these drawbacks (except the wait for each instrument to load) disappear with a disabled VE Pro template, but then you get other drawbacks - complexity of initial setup and separate midi and audio tracks. For some, waiting any time for an instrument to load is too annoying to contemplate, and they might go for a conventional VE Pro template which offers instant access to all instruments but also huge RAM consumption and long load times at the start of a project, along with those separate audio and midi tracks.
None of these approaches is right or wrong, it’s just choosing your poison really.
Do you have any plugins in Cubase? If you have some heavy plugin chain in any of your tracks/buses, that could be the reason.
Hi! I have the same problem, and can´t figure it out. It is definetely a Play problem as I see it. It happens in my main computer and when I tested the same instance in my slave so it is not hardware related.
I have been in touch with vienna support also but no luck.