196,149 users have contributed to 43,014 threads and 258,393 posts.
In the past 24 hours, we have 0 new thread(s), 7 new post(s) and 168 new user(s).
My own experiences with Play as VSTi in Cubase are not good: frequent crashes or no sound output when using Play, also some graphic errors sometimes. I try to use my older Kontakt versions of EW instead when ever possible.
So I would definetely believe that this is an EW problem - not a Vienna problem.
I did see a post elsewhere from someone who tried running the new PLAY with an older version of VEP - it ran but there were some functionality bugs which went away when he updated to a newer version of VEP. So it does look like there were some fixes made on the vienna side that helped PLAY work better.
There were some overall improvements to plugin hosting in VE Pro updates, which could indeed also affect Play. No Play specific fixes were ever done for the hosting of Play in VE Pro however. I think this is not a matter of pointing fingers though. Let's just be happy that the compatibility problem is resolved and get on with our lives ;)
It's only been a few days and I haven't pushed it (I normally only use a few EW sounds at a time anyway), but it's working great for me so far. It's a HUGE relief. Before, I had all my VSL libraries on a Mac Pro slave with VE Pro, working great, with Play alongside Sonar on my Windows XP master, and was constantly having trouble with Play taking over CPU resources, missing notes or sustains on export, etc. Whether it's just finally getting Play onto a slave rather than the master computer, getting it onto a Mac rather than PC, or some other improvements they've done, it's totally working great. There's been much less swearing in my studio this week. :)
Of course, to stay on topic, it's thanks to VSL and VE Pro that I can do it! And VSL is still the vast majority of my sound. I pretty much only use EW for instruments VSL doesn't offfer.
I updated to the latest versions of Play (v2.0.18) and VE Pro (v4.0.6150, both master and slave) and tried to add a SD2 plugin to my slave PC's VE Pro (64-bit) and I still get the "Could not creat plugin play_VST_x64". I'm having a deja vu :/
I got it working yesterday just once, but I haven't been able to recreate it. I've tried everything, including an empty VE Pro (not server) instance with no other instances open. In my VE Pro instances, I have VSL sounds, plus many Kontakt's (v4.10.3681, loading samples in background) and MidiOverLan. In my master, all VE Pro plugins are in Bidule.
Any ideas?
@lenersen said:
I updated to the latest versions of Play (v2.0.18) and VE Pro (v4.0.6150, both master and slave) and tried to add a SD2 plugin to my slave's VE Pro (64-bit) and I still get the "Could not creat plugin play_VST_x64". I'm having a deja vu 😕
On Mac PLAY (2.0.18 ) is still a 32bit app , because EastWest - like other developers - has to wait for PACE 64bit drivers .
Therefore PLAY has to be loaded into the 32bit VEPro Server on Mac .
Best ,
Gerd
On Mac PLAY (2.0.18 ) is still a 32bit app , because EastWest - like other developers - has to wait for PACE 64bit drivers .
Therefore PLAY has to be loaded into the 32bit VEPro Server on Mac
My Slave is a 64-bit PC, not a Mac. Sorry, I left that info out.
@lenersen said:
My Slave is a 64-bit PC, not a Mac. Sorry, I left that info out.
Ah , okay , I see .
Sorry , then I don't know the answer to solve your issue ....
In Kontakt 4.1 in a 64-bit instance, there is no need for the memory server. It's switched off by default I think. Here, the two memory servers, EW's and KMS will not co-exist at all. I am separating out Play (only 32-bit available on mac) from Kontakt in all cases now.
Play is still not working here.
If I try and instantiate a 64bit version of PLAY (Windows) in the 64bit VE Pro server, I get the same old "could not create plugin ..." error. Reproducible 100% of the time.
I've checked the version numbers of VE Pro and PLay and both are the latest. Looks to me like this still is not fixed.
Jules
