Vienna Symphonic Library Forum
Forum Statistics

189,264 users have contributed to 42,653 threads and 256,739 posts.

In the past 24 hours, we have 1 new thread(s), 7 new post(s) and 75 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP engine start/stop issue
  • A
    A
    thanks Paul, sorry, I missed your message. Sending now.
  • A
    A
    do you want the mframe file too? or just the .cpr?
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi aptmusic, 

    @aptmusic said:

    thanks Paul, sorry, I missed your message.

    Seems like you were very busy posting [;)]

    Send me everything you think is relevant!

    Best, 

    Paul

    Paul Kopf Product Manager VSL
  • A
    A
    any progress? It seems that this issue is cause by VEP not disconnecting when a project is closed. interestingly enough, a VEP mframe will preserve the error by saving. For instance, lets say i close my Cubase project and the instance remains "connected localhost" as usual. I save the metaframe, and reload the metaframe. The Instance will load and STILL say "connected localhost". The reason I don't force disconnect is that the instance is rendered useless and the engine wont start after its been forcibly disconnected. However, if you load a viframe preset into the "connected localhost" instance, this will remedy the issue. Its something fishy with PLAY, I'm sure. I've just had too many issues with PLAY in the past. If this was happening with regular VSL instruments I'm sure you would have heard about this glitch by now. Thanks -Andrew
  • A
    A
    My temporary solution is to manually disconnect the VEP instance everytime. However, when reconnecting it takes a long time for the engine to start. like 30 seconds to a minute where i'm wondering if it will start at all. A good feature to include in VEP5 would be some kind of info screen that tells us VEP is still active and trying to start the engine. The windows activity wheel stops spinning, so it leaves the user with the assumption that the VEP engine failed to start.
  • A
    A
    Tried it with another project and can again confirm this issue with forcibly disconnected instances. The engine light will briefly flicker after several seconds, but will never actually turn on, and the only way to resolve this is to reload the viframe...
  • A
    A
    got the EWQL people working on this finally....
  • A
    A
    any updates on this? I've verified many occasions where the Engine simply wont start unless the template is reloaded....
  • A
    A
    Seriously, I've bought VEP5 and the issue still persists. I hope the EWQL ppl are working on it...
  • A
    A
    bump. this really defeats the whole purpose of VEP. if I have to reload the template all the time whats the point?