Vienna Symphonic Library Forum
Forum Statistics

201,247 users have contributed to 43,236 threads and 259,222 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Loading new samples stalls on slave computer when DAW computer loads existing project.

  • Loading new samples stalls on slave computer when DAW computer loads existing project.

    B
    B
    I'm having an issue: when a project is launched on the master(DAW/Sonar X1) computer the slave computer tries to load the instances of VEP that were used with that DAW project. The second (of three) instance(s) always stalls on the "Loading" dialog box and VEP has to be terminated in order to continue. I notice that when I load the same instances manually, they load smoothly and without a problem. I've tried using the "Discard Data" setting on the slave, but it seems to behave in the same manner. Any suggestions on how to make this work correctly? Thanks!
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @BentleyOusley said:

    when a project is launched on the master(DAW/Sonar X1) computer the slave computer tries to load the instances of VEP that were used with that DAW project.
    This is what is supposed to happen if the DAW project and VE Pro frames are coupled.

    The best solution in my experience is simply to decouple them via the VEP server connection in the DAW. Manage saving the two projects separately. Then the DAW project connects to the VEP frames without confusion. It will connect to whatever configuration you have up on the slave side per 'slot' instantiation; so if you have metaframes with corresponding names per the DAW project you're golden, just load the VEP slave side before opening the DAW project.

    EDIT: in addition, with VEP 5 if you have saved the DAW project with them coupled, decoupling later still means that reconnecting has VEP 5 as slave reloading what was loaded last save; ie., what the DAW remembers supersedes the last metaframe save.

    The DAW being tasked with remembering what is loaded means a slower loading time in general and a larger project means a lot more time loading.