Vienna Symphonic Library Forum
Forum Statistics

180,772 users have contributed to 42,140 threads and 254,363 posts.

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

  • VEP6 - engine stops every couple of days

    I am running VEP6 on a Windows 7 Pro SP1, i7 PC with 24G ram as an external slave system (hardware I/O back to the Nuendo host with MidiOverLan instead of VEP streaming). 

    Every couple of days, I will come into the studio in the morning, and VEP6 on that PC will show 0% load - i.e. the VEP server engine will no longer be running.  The only way to restart it is to quit VEP6 and reload - which takes quite a while even from SSDs.  "Start/Stop audio engine" doesn't work.

    Does anyone have any ideas how to resolve this?  It is costing me a good bit of time having to reload this slave system 2-3 times a week. 

    This system is running VEP 6.0.15567; many instances of Play 4.2.2 with Hollywood Diamond Strings, and 3 instances of Kontakt 5.3 with Sample Modeling Brass.  Midi is via MidiOverLan.  Audio is an RME 9652.


  • Hi dterry, 

    Hm, no idea why the samples would unload from RAM without you triggering it. Any sleep modes that might be in the way?

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Same problem with a 2xslave setup cubase 9 host.

    i7-6770k 64gb ram win7 host - RME raydat (radar24-clocked) 256buffer - cubase 9 (latest)  - vep6, 16+kontakt, ew play, spire, serum, sylenth, uvi wrkstation, omnisphere, keyscape

    i7-2600k 16gb ram win7 slave1 - vep6 - same software

    i7-2600k 16gb ram win7 slave2 - vep6 - same software

    Gigabit through hardwired switch and static ip. cat6 cable I crimped myself.

    Literally the same issue... the audio engine is just blank after an extended period of time. it's never quit during use, just after returning from a 24 hour period+ of not being used. Midi appears to be functioning but no audio seems to be coming back through the ASIO lanes.

    Paul, if you want to track this down even further, let me know what you would need. I have a background in software development so i'd be open to helping you nail this one down. Definitely not a sleep or hibernation issue on my end. What else could possibly cause a timeout issue?

    Also, I have not taken the time to roll back to 5 or 4 and wait for the problem fyi. Next time I get the issue, I'll see if there is ANY way outside of close and reload that can fix the issue. might help in tracking down the source.


  • last edited
    last edited

    @Paul said:

    Hi dterry, 

    Hm, no idea why the samples would unload from RAM without you triggering it. Any sleep modes that might be in the way?

    Hi Paul,

    It isn't unloading samples.  Windows task manager still shows 18G+ loaded for VEP.  I don't have any sleep modes active.  I It is the playback/audio engine that stops running, and can't be restarted within VEP.  When this happens, I can quit VEP, but usually the VEP process remains active until force-quit.  

    So far this has only happened on the Win7 Pro slave, but not on my host system (also running VEP6, Windows 8.1).  Both are i7s. 

    Regards,
    Dedric


  • Hi, 

    I have been trying to reproduce this on my Win7 computer, to no avail so far.

    Are you instances connected or decoupled when this happens?
    Does it also happen when you have only Vienna Instruments loaded (you can check with Epic Orchestra)?

    Thanks for the additional info,
    Paul 


    Paul Kopf Product Manager VSL
  • This server instance isn't connected/coupled.  I am running MidiOverLan for midi to that slave, and hardware I/O, so no VEP streaming.  When I have time I do plan to connect that instance to the host and test without MOL and hardware.  When I have time I will try with Epic Orchestra - currently I only have Play 4.2.2 (HW Strings) and Samplemodeling brass (Kontakt 5.3) loaded on that slave/instance of VEP.


    Regards,
    Dedric


  • Hi Dedric, 

    Sorry, I mixed this up with a different problem. Will check with the Standalone version now. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Paul,

    Since you asked, I HAVE been running decoupled... I love being able to label the tabs clearly in this way.. however for troubleshooting I'll do a few trials overnight with cubase-coupled instances. I kept in same thread to help narrow  down. No intent on confusing the issue however I suspect both configurations could be faulted by the same issue.

     

    Jesse


  • last edited
    last edited

    @Paul said:

    Hi dterry, Hm, no idea why the samples would unload from RAMwithout you triggering it. Any sleep modes that might be in the way?
    Hi Paul, It isn't unloading samples. Windows task manager still shows 18G+ loaded for VEP. I don't have any sleep modes active. I It is the playback/audio engine that stops running, and can't be restarted within VEP. When this happens, I can quit VEP, but usually the VEP process remains active until force-quit. So far this has only happened on the Win7 Pro slave, but not on my host system (also running VEP6, Windows 8.1). Both are i7s.Regards,Dedric I'm experiencing exactly the same thing. I have to reboot my Win7 slaves every single morning and reload a bunch of Kontakt/Spitfire libraries which takes up about 30-40 mins each day. Same set up - staric IPs on cat6 gigaswirtch. All sleep settings turned off everywhere. Looks like VEP chooses to disconnect automstically after an hour or so of no activity. Only thing I can think of that might be interfering is the wifi - I have wifi turned on on both master and slaves, but not sure if or why this would cause a VEP disconnect (when it's actually showing itself as loaded and connected to the Cubase Master - but actually isn't). Anyone got any ideas how to remedy this?

  • I'm still tracking it down... but try updating Kontakt 5.6.6... I'm using a slightly lighter setup (not fully loaded) and haven't had a disconnect in the last two days. I'm thinking it could be library specific to Kontakt... or perhaps they did fix something in recent update. later this week I'll be able to load a maxed template again and see if the disconnect will happen. Are we certain it is VEP6 specific? I just can't remember if I ever had this issue on 4 or 5.. music-brain.


  • windyweekend,

    I have a feeling that if the kontakt update did not provide the fix... we are going to need to detail out the specifics of our vienna racks to track this down fully... Im 5 days into a slave configuration that hasn't had the issue... though like I said before, my racks aren't fully loaded as normal, where i first experienced the problem we've all reported in this thread... based on what I know now, I'm almost positive the problem is not hardware, os configuration, network config... has to be DAW-VEP or VEP-INTERNAL.. both server and standalone.

    I'm about to architect a new upgraded multi-slave setup of a friend of mine who happens to be a much busier and credited composer than me and really would like to have this problem licked before signing off on his templates...

    I will post the details of each setup that either has the issue or does not as soon as I can guys. peace.


  • Updated Kontact to 5.6.6. Issue still remains unfortunately. Need to get VSL to fix this me thinks...


  • Hey I made some progress... is everyone using the same sound card for system audio and also daw use? I noticed my RME driver not changing with a buffer change while recording vocals the other day... tracked it down to the system audio (windows 7). As soon as I disabled the use of my RME in windows, cubase was switching the buffer perfectly.

    Just curious to see if anyone has the problem even if their operating system isn't using the interface for system sound.


  • I noticed a similar problem on my windows server.  As I filled it up to be quite large (around 90gig ram taken up of 128) the cpu usage went to 0%.  However when I turned off or deleted a couple of channels of instruments it would pop back on as then indicated by a 10-19% cpu usage at idle.  The instance stop start / server on / off had no effect.


  • Any update on this?  Having to reload this large slave system every couple of days is time consuming, especially in the middle of a score. 


  • Hi, 

    There was a similar thread on VI-Control, where our head developer suggested it could be related to some plugin using a 32-bit integer for timestamp, which could possibly wrap after ~25 hours.

    We would need a reliable minimal reproduction for this to go any further, any input is very welcome.

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • It doesn't appear to be a 25 hour issue with timestamps:  I removed a few unused instances of two plugins (Valhalla Room and Fabfilter ProQ2), thinking they might be the source, and VEPro ran for about 3-4 days.  But I came back to the studio today, and the audio engine had dropped to 2% from its normal 18-20%. As usual, restarting the audio engine didn't work - I had to kill it and reload.  I only have Play 4.2.2 and Kontakt Player 5.3 running in this server now. 


  • I removed 4 instances of SampleModeling Brass from my slave PC template, and VEP6 has been running for about week now.  


  • This is worse with the latest update to VEPro 6.  I just updated a slave PC that had been running for about 2 weeks now after removing a couple of plugins.  But I updated VEP6 yesterday, and this morning the engine was sitting a 0%.  

    Whatever the latest update added has made the engine-stop issue much worse.


  • For sake of comparison, I replaced VEPro6 on the standalone slave system with Cantible for hosting VIs, and it has been running for about 2 weeks now (this works as a replacement as I am using hardware for audio back to the host, and MidiOverLan for midi - I wasn't using VEPro's streaming audio/midi system).  

    The problem with VEP's audio engine stopping every couple of days seems isolated to VEPro.