Vienna Symphonic Library Forum
Forum Statistics

186,358 users have contributed to 42,454 threads and 255,812 posts.

In the past 24 hours, we have 4 new thread(s), 15 new post(s) and 41 new user(s).

  • Support for Ensemble Pro


    I posted a question on this board about a week ago. Although the post has had many views, there has been no response to my question. Is there a way for me to submit the issue to VSL? Do they have a tech support area? I've not been able to find it, and I'm more and more frustrated with the Ensemble issue, since I've now tried just about everything I can think of. Just to repeat my origitnal post:

    ORIGINAL QUESTION: Ensemble Pro Server audio distortion. Major problem!

    Everything works fine with Ensemble Pro stand-alone, but the same instruments are distored when run from the Ensemble Pro server version. It does not seem to matter what the DAW is--the distortion happens with Finale, Notion, StudioOne, and Sonar. And all the same way. That is, the stand alone version works fine.

    Also, it doesn't matter whether I load Vienna Instruments or Kontakt instances in Ensemble. The stand alone works, but the server version is distorted. 

    Starting and stopping the audio engine does not help. Also, going back as far as 15864 does not help or change the effect at all. The number of instruments loaded does not matter. Even loading just one results in the distortion. 

    The DAWs I mentioned can all load Vienna Instruments vst instances and run them without problems. 

    ALSO: The current version of Ensemble Pro server WAS working a few days ago. In the meantime, I'm not aware of making changes to my system. I've spent the last three days trying everything I could think of, so I am hoping that either someone has the answer, or (if it is a VSL related issue) there may be an update with a fix. I'm the first to say it may not be a VSL issue, but something has caused the server version to stop working for me.

  • last edited
    last edited

    Hi John,

    You can always contact our support team directly via

    It will help to include some details about your setup, especially your OS and network details (you should use static IP addresses, as described in the VE PRO 6 manual).

    Just a thought: Could it be that you're trying to connect over your WIFI network?

    I see that you have been using VE PRO for a long time and upgraded to VE PRO 6 in 2016 - did you setup work before?


    Paul Kopf Product Manager VSL
  • Hello, Maestro

    Thanks so much for your time and getting back to me. Yes, everything was working until a couple of weeks ago--NO problems at all. The one thing I knew I could always count on was VEP server. Right now, everything is on a single computer, and your comment leads me to wonder what might be happening with the network. One thing that I found yesterday is that the Windows 10 resource monitor shows lots of sustained, high-level activity as soon as I open VEP and a host application. This is probably normal--I just have had no occasion to observe it before.

    I emphasize that this happens with the smallest and simplest configuration. One instrument on one channel. It does appear that something has changed on my system (since this was working perfectly for a long time). I can't find out what it may be. But as a friend of mine says, "That which is different is not the same."

    My audio interface is a Tascam UH-7000, which has been rock-solid. I'm using the hightest latency settings now (about 1 second), but the setting does not make a difference.

    As I said, the stand-alone versino of VE works perfectly. Again, I thank you for your help. Do you suggest that I contact your tech support department?

    By the way, I met you at NAMM in Anaheim in 2016 and want to let you know again how highly I think of the video tutorials you do. They are concise and friendly. And clear! 

    Thanks again


  • last edited
    last edited

    Hi John, 

    Thanks for the compliment 😊

    You should check your network settings.
    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
  • Hello, has your issue resolved? I'm having the same issue.