A Cubase / Disabled VE Pro Template Part 3: Why Go To All This Bother?
Вставка
- Опубліковано 3 лют 2019
- This briefly looks at some of the alternative template ideas. and why they're all a bit more rubbish. Part 1 is the intro • A Cubase / Disabled VE... , Part 2 looks at setting it up in details • A Cubase / Disabled VE...
Hi Guy, it is a very nice approach with VEP, thanks for the videos. I have noticed here that my Cubase sessions start to be less stable if I have more than 4/5 VEP instances connected (even if they are on a slave machine) and with higher number of audio returns from VEP. I suppose you don't see this situation, judging from your VEP window, but I wonder where is the bottleneck or the cuplrit in my setup here. Have you ever experienced this behaviour I describe? Any ideas how to tackle it?
So you have to disable VE pro instruments individually or the whole instance of VE Pro? Thanks so much for all your hard work it is very helpful
Individually, one by tedious one. All the details of how to do it are in the Part 2 video.
May I ask a question? Can you monitor which instruments are disabled or enabled and how?
Hi Gorey, I don't know of an easy way to see what is enabled or not in VE Pro. I did ask VSL if it were possible to have a RAM monitor for each instrument, and apparently it isn't. As it is, I just have to scroll through visually, though in practice I tend not to worry about it unless I'm specifically building a template.
@@guyrowland4711 Thank you Guy :)
Why don't you use the VST Parameters for disable communication with VEPro? Those are actually saved inside cubase, you won't neet the initialization note when loading a project.
Hi. I know it's been awhile since you wrote it, but can you elaborate ? I'm actually setting up VE Disabled based template and I'm wondering how to recall session automatically without enabling all needed tracks manually with CC data on each used track.