Vienna Symphonic Library Forum
Forum Statistics

181,766 users have contributed to 42,181 threads and 254,575 posts.

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

  • VEP 6.0.15318 makes my cubase template freezes

    Hi VEP team,


    From 9/29

    My Cubase stuck at " Loading MixConsole" when opening my template.

    I tried to remove each plugin one by one. 

    After I removing VST3 Folder => VEP four .vst3 files

    The issue was gone.

    I reinstalled VEP6 but still can't open.

    Please help 

    Thank you 


    Solo Wang

  • Hello Solo, 

    Which files exactly did you remove?

    Can you please describe this in more detail (which OS, which versions of software)?

    You can also contact us with screenshots at


    Paul Kopf Product Manager VSL
  • Thank you for your reply Paul,


    It is " Vienna Ensemble Pro.vst3 " file.

    I thought it was VEP's issue yesterday so I open a empty project in Cubase.

    Also I open a new project in Slave Machine VEP6.

    Finally I found out it is network issue.

    My DAW machine can't find my Slave Machine. 

    Slave Machine doesn't show up in DAW VEP connection list.

    I'm pretty sure the connection is OK because I'm still using screen sharing, file sharing. 

    So I manually enter LAN address, instance name. 

    It connected ! 

    After that, Cubase seems found out where my Slave Machine is and template can be opened now.

    The only problem now is that my Slave Machine doesn't show up in DAW VEP connection list.

    Everytime I have to enter IP address and instance name manually.

    Would you please give me some suggestions about it ? 

    Thank you 



    Solo Wang

  • Hello Solo, 

    Glad to hear that you resolved that one (still a bit confused here). 

    What are your network settings?

    As described in the VE PRO manual, you should definitely use static IP addresses, and avoid 169.x.x.x addresses (these are automatically assigned by your computer and tend to change).

    Please try the following: 

    Manually assign one of these IP addresses to the computers in your setup: 192.168.0.x or 10.0.0.x, and assign a subnet mask of (leave the other fields blank), then it should work. 


    Paul Kopf Product Manager VSL