Vienna Symphonic Library Forum
Forum Statistics

181,898 users have contributed to 42,190 threads and 254,623 posts.

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

  • VEPRO 6 plugin causing project to freeze upon open

    Hi,

     

    So I just got a Master/Slave pc combo going connecting with Vepro 6. Everything works like a charm however, when I save the project and try to re-open it... it freezes and hangs and I have to manually close and restart. I realized it wasn't the Vepro 6 on the server pc... it's the one running on my main pc alongside cubase.. For some reason if I connect both Vepro6 thats running on my server and master pc in my cubase sessions, save it, close and re-open it will hang. The only way to get the project open is to manually remove the Vepro6 plugin temporialy so the project will open. However, if I run one thats seperate just connecting to my master vepro6 pc one it works...and only connecting to the server it works. But having a session connected to both seems to freeze.

     

    Anyone have any ideas? 


  • Hi Dillon, 

    Please create a process dump when Cubase and VE PRO hangs, see the following image on how to create a minidump with process explorer:

    http://cloud.addictivetips.com/wp-content/uploads/2012/02/create-dump-1.png

    https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

    Send these dumps to support@vsl.co.at, so we can take a look. 

    Best,
    Paul


    Paul Kopf Product Manager VSL
  • Hey Paul,

    Thanks for replying. I went ahead and sent you those dump files. I was confused exactly which process you wanted me to make a dump for so I just made one for Cubase, Vienna, and 3 different conhost.exe ones. I hope one of them was the right one lol.

    Let me know if I can do or help in anyway to get his weird problem solved.

    Thanks!


  • Hi, I have been experiencing this behavior for years now. Any follow up on this thread from VSL? Did the dumps reveal anything?


  • The dumps didn't reveal too much besides it being a plugin. However, upgrading to vepro 7 solved my issue, as well as just recently last year I figured out the culprit, is the VEPRO Audio Input plugin. Since I never use the Audio Input plugin, I remove that plugin and don't even allow my DAW to scan it. I get no more crashes now.

    Not saying your exact problem and crashes are the same issue as with mine and the Audio Input plugin from VEPRO. However, that and upgrading were my solutions.

    Cheers,

    DMDComposer