Vienna Symphonic Library Forum
Forum Statistics

200,713 users have contributed to 43,209 threads and 259,122 posts.

In the past 24 hours, we have 3 new thread(s), 8 new post(s) and 61 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Latest version of VE Pro hosting latest version of Play

  • Latest version of VE Pro hosting latest version of Play

    T
    T

    Hi!

    I'm having some inconsistent troubles with hosting Play within VE Pro (64-bit). I often get the message saying that VE Pro couldnt create plug-in, when trying to open an instance of Play.

    If I rescan the plugin folder when this happens, Play will disappear from the list of availiable plugins. If I close the VE Pro server and restart it, Play won't be in the plugin list, but if I rescan it will reappear and it will work...most of the time.

    What can be causing this, and is anyone else experiencing this?

    -tom
  • K
    K

    Please make sure that you're using the latest version of Play. It has been fixed to work in VE Pro since 2.0.18. Also make sure you're using the latest version of VE Pro for maximum stability.
  • T
    T
     Hi Karel!

    I am using the latest version of Play (downloaded the latest version 2 days ago) and the latest version of VE Pro (build 7384). I'm trying to set up Play in my existing template. There are 10 instances of VE Pro, Play being the latest addition. The template consists of VI, Kontakt, Omnisphere, Absynth and Play. Vienna Suite plugins are also used.
    There is usually no problem adding Play to a new VE Pro project. But there is result in the main template. I've rescan several times, restarted VE Pro and SOMETIMES Play will be availiable. If I then get the error message when trying to create an instance of Play, it will disappear from the VST list if I try to rescan the VST directories. Also an VE Pro server restart and/or reboot, does not help. Sometimes it works, sometimes it doesnt.
  • G
    G
    last edited
    last edited

    @tommalm said:


    I'm having some inconsistent troubles with hosting Play within VE Pro (64-bit). I often get the message saying that VE Pro couldnt create plug-in, when trying to open an instance of Play.

    Hi Tom ,

    just for the record :

    PLAY is still 32bit on Mac ( ... due to the iLok drivers for MacOS X which are still 32bit  ... ) .

    Therefore you can not launch PLAY within VEPRO Server 64bit on Mac .

    You have to launch it in VEPRO 32bit Server .

    However , if you encounter the issues you've described on a PC setup ... well , then I don't know  the answer ...[:S]

    Best ,

    Gerd
  • T
    T

     Oh, yes I forgot to mention that I'm on a PC, Vista 64bit.

    I CAN get Play to work, but it is not consistent. Sometimes it will create the plugin, sometimes I get the error message. I have not had this issue in earlier versions of VE Pro (not counting the versions before Play actually began working). But I have not used Play in a while though.

    Not sure if this is a VE Pro issue, a Play issue or if it has something to do with my overall VE Pro setup...compability or something.
  • T
    T

    I got the same problem on a PC. I can load in PLAY in VE Pro in standalone. But if I got VE Pro Server and then want to load in PLAY, I get the mssage "Could'nt create plugin..." And I got all the newest versions.
  • T
    T

     Any word on this VSL?

    I can't load Play when reloading my template after a computer restart. I get the "Could not load plugin: play_VST_x64".
    I first encountered this problem after one of the latest updates to VE Pro got released.

    I've got the latest VE Pro installed, latest Play installed, latest pace drivers.

    Thank you
    -tom
  • K
    K

    Do you have your VST folders properly setup?
  • T
    T

    Under "VST Settings" VE Pro is pointed to both my 32-bit plugin directory and the 64-bit plugin directory.

    When I start up VE Pro,  Play_VST_x64  wil usually be listed when trying to add a VSTi in VE Pro, but then when I load my template, I will get the error message reported above. If I then use the "rescan all" under VST settings, Play_VST_x64 will be removed from the list of availiable VST plugins.

    Now if I restart VE Pro, play_vst_x64 will still not be listed as an availible VSTi. But if I now use the "rescan all", play_vst_x64 will USUALLY be availiable again and I will be able to load up an instance or load my template.

    Thoughts?
  • K
    K

    This seems like a problem with Play. Have you notified East West as well?
  • O
    O

    Hi,

    make sure all energy saving and sleeping-modes are turned off.

    That helped me on Windows 7.

    Best 

    Oliver
  • S
    S

    Hi,

    Using VEP on Win 7/64 w Cubase and as a server host on XP over gigabit. Considering getting EWQLSO and installing on VEP Server/Host machine.... just wanted to make sure VEP and current 'Play' engine are compatible. Any PC users out there using with VEP as host server over gigabit? I'm willing to upgrade the XP machine to Win7 if that's necessary.

    TIA,

    ---JC