Vienna Symphonic Library Forum
Forum Statistics

196,086 users have contributed to 43,014 threads and 258,388 posts.

In the past 24 hours, we have 2 new thread(s), 13 new post(s) and 158 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. East West Play finally fixed!!?
  • M
    M
    last edited
    last edited

    @inwinterhesleeps said:

    To be fair, Doug's comments on this latest update state that to fix this incompatibility it required work on both sides.

    To be fair, Doug initially swore up and down that everything was just fine on the EW side and that it was totally Vienna's fault and that it would require a fix from Vienna and EW didn't need to do anything about it.  I hope he remembers this next time there's an issue and is more diplomatic instead of immediately blaming everyone but his own company.
  • S
    S
    last edited
    last edited

    @Karel said:

    Try Play 2.0.18 in older versions of VE Pro and you'll know for sure 😉

    Lolll Sorry, but I don't like the arrogance and presumption of Doug.

    Even I've some EW products...
  • I
    I

    So Karel, you are stating that absolutely nothing has been done by VSL to make things work? Or is it just that the VSL team implemented their side of the fix a lot quicker?
  • M
    M

    Anyone want to try the latest PLAY with earlier versions of VEP?  It would be interesting to see how long it has been fixed on the vienna side.
  • K
    K

    That was actually just a hint to state that nothing was fixed on our side. The new version of Play should work fine in all versions of VE Pro.
  • I
    I

    Wow, that is very interesting indeed. [:)]
  • M
    M

    Does that mean all as in recent versions, or all as in since the very first release of VEP?
  • K
    K

    It should work in any release of VE Pro.
  • W
    W
    I have been getting some white noise off and on with Play.. I am using Sonar, Win 7. For me it's not 100% rock solid yet.
  • K
    K

    And this behavior is exclusive to using it inside VE Pro? If not, I recommend taking this to the Play support team.
  • A
    A

    On that Geaslutz thread where shills for EastWest were outed he explcitly said nothing was wrong with PLAY and it was VSL's problem.  Too bad they deleted that thread.  It was a beauty.
  • S
    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.
  • M
    M

    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.
  • K
    K

    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 ;)
  • L
    L

    Any reports from users that the v2.0.18 update is now really working with VE Pro? I had a few libraries from EastWest and ultimately had to stop using them completely in my template because of the incompatibility with VE Pro.
  • K
    K

    Seemed to work just fine here.
  • D
    D

    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.
  • L
    L

    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?
  • G
    G
    last edited
    last edited

    @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
  • L
    L
    last edited
    last edited

    @gerdkaeding_31947 said:

    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.