Vienna Symphonic Library Forum
Forum Statistics

181,978 users have contributed to 42,198 threads and 254,643 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. PLAY and VE Pro issue loading

  • PLAY and VE Pro issue loading

    E
    E
    I read someone having a similar issue a few months ago but it seemed to be unresolved. Basically, If I start up VE Pro (without loading cubase or anything) and I load PLAY as a VST and then open a saved .ewi Hollywood Strings file, PLAY will only load around 10% of it and then the loading will completely freeze (note that neither PLAY nor VE Pro freezes - it's the loading process that freezes). This only happens in VE Pro, and when PLAY is used in cubase to open these files, it works flawlessly. Has anyone had this issue? This only happens when PLAY .ewi file is loaded in VE Pro server. It seems to load OK in the regular VE Pro. Obviously this doesn't help though, because I need it to load in the server so that I can connect with Cubase. EDIT:For what it's worth, that same .ewi file loaded with no problem once the server was connected to Cubase FIRST. So this really makes no sense but from what I've gathered, PLAY has issues loading Hollywood String .ewi files on the server ONLY when the server is not connected.
  • K
    K

    Make sure you're using the latest version of Play. If this doesn't help, unfortunately you have stumbled upon a technical design flaw in Play in that it relies on a running audio engine to be able to load its sounds. Though EastWest has been made aware of this already in the past (and I believe it was already fixed at one point too), it's probably best to contact their support with the issue.
  • A
    A

    I load my big HS & HB Play in VE Pro template on my slave PC and a smaller one on my Mac before I open Logic Pro and connect to them almost every day with no problem, so this is a system specific issue, not an overall Play or VE Pro issue IMHO. 
  • K
    K

    I suspect he's just using an older version of Play. This issue was fixed quite a long time ago as far as I remember.
  • K
    K

    I am having the same issue, albeit on a slightly different system configuration. I have a Mac Pro as my main DAW and a slave PC running PLAY 3.0.32. After VE Pro starts up on both machines, if I open a Digital Performer file with the saved instances intact, my entire template will load, up to the point where Hollywood Strings starts to load up on the PC slave. It gets through about 10% before it just hangs. (Interestingly, I also have Hollywood Brass loaded on the same PC slave, and it has no problems loading the template without hanging.)

    Now, if instead of loading up my template by opening my DP file (with nothing loaded in VE Pro), if I open the metaframe on the PC first and then launch DP to connect to the loaded instances, I have no problems.

    This, of course, is not how it should be. I understand that it will work using the second option I just outlined, but I like to load everything up at once simply by just opening my DP file and having all of the instances load up with it, instead of manually having to load my metaframe first and then launching DP.

    EDIT: Looks like Hollywood Brass just started to hang as well. Also, I made sure that the audio engine was running in VE Pro by creating a dummy instance with the engine turned on. Also forgot to mention that this never happened when I was using Macs as slaves. This problem only started occurring when I bought a new slave PC last month and moved all of my PLAY libraries over to it.
  • K
    K

    A dummy instance with the engine turned on doesn't help. The instance in question has to be connected to the master host and the engine enabled (which is the default behavior).

    I suspect Play has a regression since previous versions. Perhaps try rolling back to a version that did work properly?
  • A
    A

    You suspect incorrectly :)

    I am EW's Online Coordinator as well as one of your beta testers and as a result, I use every new version of Play before it is released, as well as every  new version of VE Pro 5 before it is released.

    So that is why I suspect It is neither a Play or VE Pro issue, it is system specific. That said, I am working strictly decoupled so possibly I guess it could be a coupling related issue.
  • K
    K
    last edited
    last edited

    @Ashermusic said:

    So that is why I suspect It is neither a Play or VE Pro issue, it is system specific. That said, I am working strictly decoupled so possibly I guess it could be a coupling related issue.

    A coupling issue with PCs only - remember - this never happened on my Mac slaves.

    I have an educated guess, though, as to why it may be happening. In my template in DP, I have all of PLAY's Hollywood Strings instances next to each other. The way VE Pro loads the instances happens to follow the way the instrument tracks are loaded into the mixer (or V-Rack, in my case). So, when I load an instance of Violin 1, VE Pro usually waits until Violin 1's instance has completed loading. It then moves on to my next instance, Violins 2. 

    My guess is that VE Pro (or DP) is sending out the command to the slave PC to load the next instance before the first one has had a chance to finish loading, causing the hang. That guess is based on the fact that the Hollywood Brass instance (which loads way before the strings in my template) loaded once successfully due to another Mac slave machine loading its template to give it time to finish, but then on subsequent loadings after I had to reboot, it hung when trying to load the next PLAY instance (which was Violin 1). The other Mac slave, since it already had non-PLAY instruments loaded, sent the message to DP/VE Pro that it was already loaded, which cut down on the time to load up the next instance of PLAY.

    I know that sounds confusing, but I suspect it's an overlapping loading issue. Of course, I could be completely wrong. [:)]
  • E
    E
    Ok guys, here's something else I found out. Kevin Kliesch, see if this also happens to you. Although it loads to 10% and hangs after that, if I check CPU memory usage, the RAM continues to climb until it hits around 13 gigs (which is about the size of that .ewi file). To me this means that it actually DID load, but the PLAY interface itself had some sort of hangup. Just like Kevin, I found a workaround. As long as I connect the server to Cubase, I have NO problems loading anything.