Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
VEP instances (workflow)
Last post Sun, May 08 2022 by Terence_, 4 replies.
Options
Go to last post
Posted on Wed, May 04 2022 02:27
by Terence_
Joined on Wed, Apr 20 2022, Australia, Posts 12

I'm new to VEP. Actually, just doing my first VEP project and being challenged to rethink my workflow - how much I want to rely on the DAW vs how much i want to load into VEP. I'm thinking I may as well go the whole hog and load pretty much everything into VEP and just use my DAW as a 'sequencer' as suggested by the continuous usage of that nomenclature in VSL documentation.

So my question is, what is the typical reason/useage-case for needing more than a single instance in VEP?

What is the disadvantage of just loading everything into a single instance.

Specifically, I am looking for reasons that go beyond using multiple instances as purely an organizational function.

What are the technical reasons for multiple VEP instances in a single project?

(I use a range of DAWs)

Posted on Sat, May 07 2022 18:00
by Mavros
Joined on Mon, Apr 19 2021, Switzerland, Posts 26

Hi Terence, a first reason for several instances not related to organization is that one of your DAWs might not support more than 16 midi channels per port nor multiple ports. I think the Logic multiport version is still a Beta. It might have changed but when I got my M1 MBP Logic did not accept it.  I had no time to further test. 

As you would normally use the same VEP file for multiple DAWs and multiple music pieces not always using the same instruments It is also of advantage to group your instruments in instances. I usually save a file with all instances on Off and based on the instruments I plan to use in a new piece, activate the instances with the instruments I want to use. Usually I have to connect 4-5 instances per piece linked to the template. 

Posted on Sat, May 07 2022 22:18
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1942

The only times I instantiate an instrument in Cubendo is 1) to establish and/or continue automation of parameters via live interaction with its interface, or it's something that rather than take MIDI note-ons to make it sound generates its own sounds, so a performance of it has to be captured by a record operation; or 2) this is the first in well over a decade, an instrument whose performance in VE Pro is atrocious and it happens to perform quite well in Nuendo currently. This thing is not supported for my hardware or OS, and for whatever combo of reasons does not work well with the iLok VEP, it brings my system to its knees at once. But performs very well in Nuendo 11.

I mix using VE Pro's automation mapping. I do some further work with rendered audio in certain cases but the orchestration and that mix is all from host automation lanes. And at this time I'm only outputting one stereo out per instance. And two instances that are pretty different from each other, mainly to not have one unwieldy auto map in the single instantiation, another reason is to see what is using CPU more (this being some very different approaches, where the smaller instance is using more CPU (cymbals, tails...).

MacBookPro 18,3
Apple M1 Pro: 2.3 GHz 8-core i9

Mac OS 12.3.1
VE Pro 7.1298, Nuendo 11.0.41
Posted on Sun, May 08 2022 03:29
by Terence_
Joined on Wed, Apr 20 2022, Australia, Posts 12

Interesting. Thanks for the reply guys. It seems that people use it very differently according to their needs. I appreciate you guys sharing with me how you like to use it.

I ended up doing a "first look" video where I share my progress of what I have learned thus far.
https://www.youtube.com/watch?v=keUxJpkSpZo

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.