Vienna Symphonic Library Forum
Forum Statistics

181,738 users have contributed to 42,180 threads and 254,564 posts.

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

  • VEP engine stops everyday after last update

    Running VEP 6.0.16068 on an i7 slave PC, and the engine now stops everyday (usually overnight).  

    Prior to this update, it was running 1-2 weeks before stopping (after I removed a couple of plugins that seemed to increase the engine-stoppage to 1-2 days).   Now it is everyday.  I may have to go back to VEP5 on this slave. 

    VSL - any ideas on this?  I know you want a repro, but this is a basic template in VEP6 - nothing but 16 instances of EW Play 5 running Hollywood Strings.  No other plugins.  Prior to this update, when VEP's engine would "stop" the cpu usage would be around 2% instead of its normal 20% or so.  Now, when it stops, it drops to 0.0%.  

    In all cases, the only solution is a force-quit in Windows task manager and restart VEP6.  This system is running Windows 7 Pro. 


  • I agree that the last three updates have been very unstable for me. I, too, am considering going back to VEP5.


  • Hi,

    We will look into it, let's see if we can reproduce this. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi, 

    I check on our Win 7 computers, engine kept running. 

    Are these VE PRO instances connect / decoupled / preserved / disconnected, when the engine stops?

    Maybe I am overlooking something here. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • This instance is decoupled and preserved - it uses hardware I/O instead of VEPro streaming to connect with the host PC.  

    It has been running for a few days now.  I can't find anything unique that would have caused the engine to stop the day or two after I updated VEP6.  Rather odd.  It still tends to stop after a week.  Removing Valhalla Room, Fabfilter ProQ and a couple of instances of Kontakt 5 with SampleModeling Brass seemed to have reduced the rate of engine stops from once a day (usually overnight while sitting idle), to once every week or so.   I don't know which of those three might have been causing more frequent engine stoppage.  I might guess SampleModeling Brass given the scripting involved, but that doesn't explain the stops occuring with only Play 4.2.2 in use. 


  • Hi, 

    I'm a bit confused now.

    Are you using VE PRO as a Standalone software?
    How else would you be sending audio via hardware I/O? 

    Thanks for a quick explanation, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul - sorry for the confusion - yes, this slave PC is running VEP6 standalone.  I have VEP6 on my host (Win8 i7), running as a server connected to Nuendo, but decoupled and preserved, and it has not exhibited this problem (i.e. it runs constantly for weeks at a time).  It only seems to be this standalone slave (Win 7 Pro), that is having the problem.  


  • Hi, 

    Thanks, I'll check with the Standalone version right away, then. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi dterry, 

    We still couldn't reproduce this here, also with PLAY loaded. 

    I'd check if the latest drivers for your audio hardware are installed and see if that maybe changes the situation. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • VEP6 on my Win7 slaves system was running for 3-4 days before the engine would randomly stop, but after the most recent 6.0.16778 update, it runs less than a day before stopping.  And with the last two updates, we still have the problem that VEP6 always shows 0% cpu usage, so I have to manually test to see if the engine actually stopped on this slave.

    Add to this that VEP6 on the host system will randomly stop responding (with both Cubase 9.5 and Nuendo 8), and I lose a lot of time reloading this large template every week.  Even with all SSDs on multiple systems, it takes quite a bit of time. 

    I know you can't reproduce this, but some bugs need to be addressed without a repro. I am happy to provide whatever info I can, but VSL may have to dig through the code without a repro.