2 things: one, Play x64 has been reported as featuring a slow loading problem in the past in VEP(4). However there was admittedly a bug that appeared in some sytems which has been addressed by VSL. was Play loading fine before?

2: I never liked coupling the p;rojects. I don't know of any particular advantage to working that way and it is ture that the loading time is seriously faster decoupled, loading VEP first, fully, and then launching the Cubase project which will automatically connect properly.

I'm still having this problem, even with the VEP instances decoupled. There are a couple Play instruments, but the majority is Kontakt.

Guys,

Thank for the input! I want to clarify smth:

1. To civilization 3: I've heard about some trouble waters with Play x64, but I never actually experienced it. Slow loading time, well, everything run from SSDs here, but the lack of background loading in Play unlike Kontakt and VSL, definitely make you feel that time. For me, I feel it's ok! I don't mind waiting 1 time. The trouble is that when Cubase automatically invoke all the loading of Play in VEP Pro, then it's just stuck on 10 samples or so and don't go any further. If I create an instance manually, Play loads just find and everything works as it should.

2. What about usefullness of the automatic loading, well I cannot agree it is useless. It is definitely the perfect companion. Imagine ptbbos loading 3 slaves manually all the time, let's talk loading times there! [:)]

Thx

ptbbos: can I ask what kind of computers do you use for slaves? I think I will need to expand my station even if loading everything on 1 computer is pretty convinient, 24gb becomes short with those mamooth libraries nowadays.

Everytime I get a new PC, the old one just joins in as a slave. So the main PC is currently an i7 2600, with 3 slaves (i7 920, Q6600 and E8600). All running Windows 7 64-bit, with 8-24GB of RAM, and libraries spread over multiple SATA drives.

in my experience, which isn't trivial, decoupled loads quite a bit faster per se. if there is a personal preference in not loading loading three times rather than loading faster, I of course have no quarrelt with that. they would have to be pretty far apart for that to make up for the difference in loading time I would think. Maybe I have larger project, don't know. I have found that Cubase projects are less stable coupled with VEP as well.

I'm only offering my experience. I don't have these problems.

Agreed 100% - decoupled loads significantly faster. My issue, is that if the VEP servers are load, Cubase will not load the project (with decoupled VEP). I have to load Cubase first, then load the VEP servers, and then manually reconnect all the decoupled VEP instances. With version 4, I was able to load the servers, load the Cubase project, and everything linked up automatically.

Guys,

There's no quarell at all about loading coupled or decoupled. I have my template, but I like to vary things and the way I work so to vary the end result and the choice of instruments. Thanks for the input, really.

The problem remains the same: right now, at least for me, it doesn't work as it is supposed to. I'm just like ptbbos: can't load the project with the VEP server on.

Similar problem here;

If I load a previously saved project at some point in the load up an instance of Play will freeze ('preparing to load 0%) and the only route out is to use task manager to close Cubase - then load the project in Cubase with no VEP Servers running, then load the Metaframes, then re-connect.

I guess although maybe it is true that loading VEP and Cubase separately is quicker - it does mean I have to set up 3 separate slaves (finding and loading the right metaframes), which I'm sure uses up any loading time advantage - plus, as I say above - the one click load option allows me to get on with something else while Cubase chugs away.

Hopefully some miraculous update will get released which returns things to the old behaviour (without anyone having to admit it was their previous update that broke the workflow in the first place [;)] )

Cheers,

D.

well, since you report a loading problem, you have to be realistic and deal with that frame, don't you. I don't think you can blame the behavior of a version unless all things were equal. it's true that coupled projects (where cubase is the agent) load *very* slowly, and if there is a problem cubase will hang, as it's liable to do with a plugin. you might reasonably look at the Play version, which has been reported to load quite slowly.

"to set up 3 separate slaves (finding and loading the right metaframes), which I'm sure uses up any loading time advantage"
I wouldn't be so sure about it. Have you any experience? I do with both workflows. I would assert with real confidence that it does not unless you have very small projects. the loading time is seriously faster if cubase is not involved. there is no maybe. I'm pragmatic, so I decouple the projects. It just works more smoothly. you can be stubborn but it does work more smoothly, that's a fact of life.

@ptbbos said:

Agreed 100% - decoupled loads significantly faster. My issue, is that if the VEP servers are load, Cubase will not load the project (with decoupled VEP). I have to load Cubase first, then load the VEP servers, and then manually reconnect all the decoupled VEP instances. With version 4, I was able to load the servers, load the Cubase project, and everything linked up automatically.

I noticed one thing though about VEP 5, that is troubling. I have forgotten to decouple certain instances and saved the Cubase project with a coupled instance; although I decoupled and saved, if I have to reconnect to that instance it will reload according to the last Cubase save as though coupled. this I believe is new to VEP5. If so, BAD IDEA.

Now VEP 5 is heavier software than 4, it might load a bit slower per se. But I haven't noticed it decoupled. In the sitch I just described I don't notice slow loading at all, in fact very fast but it's not a heavy frame.