kind of. you load the template metaframe as if it is to be a separate uncoupled template, but then you load the sounds which are part of the host project anyway, coupled. Therefore it loads the same sounds twice in different instances of PLAY - (a) the ones you first loaded, which are unconnected and unused, and (b) the instances you loaded while loading the host project.

this is fine because PLAY doesn't reload samples already used elsewhere, therefore the unused instances don't take up any extra memory, with the advantage that this problem is worked around.

alright, I follow you, but does it load but the one time as a metaframe or vi frame on the slave side? Is this a workaround for people that like coupling the seq. and VE Pro projects in other words. I always decouple which obviates many problems with loading.

I haven't loaded Play 3, tbh I don't trust the Play engine in VE Pro until I see others using it. Play 2 in VE Pro was a fiasco until finally EWQL fixed it (claiming all the while 'not our problem').

I too am interested in the progress of this issue (PLAY3 + VEP compatibility). I'm having big problems with Choirs and WB multis (stuck notes, severe unrecoverable cubase crashes) and updated to PLAY3 to see if that had been addressed. I should have read the forums first!

For my part, the loading of instruments in VEP with PLAY3 simply takes forever.  I gave up after waiting 40min for my template to load and rolled back to the latest PLAY2

I have the same problem. Actually I think it loads them about 3-4 times here... But as described, it takes much shorter to load the 2nd, 3rd etc time because samples are already in memory. But it is an annoyance. This is with newest version of PLAY, newest Vienna Ens. Pro on a PC running Windows 7.

I'm anxious to hear how the solution to this issue is progressing as well.

well, I finally tried it, loaded a couple of things from RA, which loaded but once and quick.

edit: OSX.6.8, VE Pro 4.8008, decoupled from Cubase.

I would personally avoid coupling an instance containing something reported as dodgy with the seq. host. 

 Is this only a problem with coupled metaframes?

Nope, I never have anything coupled and I still have the problem.

I get a slow load problem only when coupled.

 Anyone tested if Play 3.0.21 makes any difference? And, yes, I'm a mid-projects coward ;-)

I am running 3.0.21 - no difference.

Problematic here as well. Not good :(

@Paul said:

Hello Jmichael, 

can you give us a few more informations?

Who did you talk to at East West, and who did they contact at VSL? Also, which system is this happening on?

Best, 

Paul

"His name is Jonathan Kranz. Here is the thread... http://www.soundsonline-forums.com/showthread.php?t=37299 I'm just using the demo so I thought it might be a problem with just the demo version, but other people seem to be having this problem as well. I'm excited to buy VE Pro cause it works great, except for this one issue. And the epic orchestra pack is an amazing deal! Legato flute...oh man."

Where are we on this problem? Any confirmation from either side?

 Just got HB and loading into VE Pro I have the same problem as everyone else. Everything is loading twice. I've not run into any other problems so far -- just the double-loading.

Mahlon

I don't have any issue using Play 3.0.15 in VEP 64-bit v4.1.8008 standalone.  I can load as much stuff as I want, and it doesn't load the samples more than once (even on re-opening of file).  It's still kinda slow, but once stuff is loaded it's fine.

running 10.6.7 on 4,1 2.66GHz Octo macpro.

Simon5413, gee I wonder why - maybe it's because we're discussin a PC issue, you are on a Mac...:)

I thought it was a mac thread. I think most of the replies have been from mac users.

it works with no problem here still, no redundant loading, and it's pretty quick.