Vienna Symphonic Library Forum
Forum Statistics

182,245 users have contributed to 42,214 threads and 254,729 posts.

In the past 24 hours, we have 5 new thread(s), 30 new post(s) and 47 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEPro Freezes on loading anything that contains Play (EWSO)

  • VEPro Freezes on loading anything that contains Play (EWSO)

    A
    A

     I think this has only happened since the latest VEPro version, but anything I have that contains the EW Play plug in, gets stuck at "Preparing to load" (1%).  I have to exit VEPro (which causes it to crash), restart it,  load my (backup) viframe, and then connect Cubase to it. Alternatively I can disable the Play plug in before connecting to Cubase, and that will allow it load (minus the EW channel).

    I run VEPro  as a slave (64-bit Windows 7), and Cubase as the master networked, so Cubase will never connect to anything if VEPro contains an instance of EW Play,  I don't want to roll back to an earlier version of VE Pro, as Dimension Strings needs the latest version.

    I also use BFD and Trilian, so it's not a VST plug in issue, it does seem to only affect Play,  has anybody else experienced this, and is there a fix for this?
  • K
    K

    Do you happen to remember which was the latest version of VE Pro that didn't have an issue for you?
  • A
    A

     I was running version 5.1.11262 that was all OK,  I know strange coincidences can happen,  but the problems did seem to start when I updated VE Pro.
  • S
    S
    I had the exactly same issue some time after upgrading to VEPro 5. What fixed it for me was upgrading both Cubase and VEPro to the latest versions. After that it loaded just fine (doesn't get stuck at 1%) but in the process it duplicated all my instances but with generic names ("Unpreserved x" instead of "Strings"). After that I reassigned all VST instruments to the proper instances, saved and reloaded everything. From then it worked fine again.
  • K
    K

    I've just reproduced the Play loading issue. It started from version 5.1.11262 and only happens in specific circumstances. Will see what can be done about it.