Vienna Symphonic Library Forum
Forum Statistics

182,251 users have contributed to 42,214 threads and 254,729 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Connection to Servers Issues

  • Connection to Servers Issues

    F
    F

    Hi,

    I've been using VEPro for a while now and loved VEPro 5 & 6. Since I upgraded to 7. I've had nothing but connection issues.

    I'm using Cubase 10.5 along with two 64gb slaves. Since VEPro 7, half the time, I can't see the servers withing the VEPro plugin in Cubase. If I open a project or template, they connect automatically but if I try to reconnect, I still can't see the instances in the plugin. The reason this is so frustrating is that it's not consistant.

    Sometimes they show up, and sometimes they don't and I my solution has been rebooting my slaves until they show up in the master's plugins in Cubase.

    Is this a known issue? Should I go back to VEPro 6? Can I have my money back? It's been very frustrating and we can't keep going like this.

    Please help!
  • F
    F

    It seems when I reload a server project, it appears and makes the other slave disapear. But it's still random... I've read in other forums that a lot of people are having this issue.
  • F
    F

    Is anyone at VSL taking this serioustly? If slaves are not showing up in the plugins, how are we suppose to work? Currently we have to recconnect using the IP adress and exacte instance name. This would work with small templates but not when you have up to 100 instances spread through multiple slaves. This is a major issue and 3 out of 4 coworkers here have the same probleme since we upgraded to VEPro 7. Version 7 has been out for a while now, any formal explanations comming up from VSL? Can you at least acknowledge the issue and let us know you're working on some fix?
  • bbeliusB
    bbeliusB

    Hi!

    If you are looking for support please contact us via support@vsl.co.at
    This is mainly a user forum to get help from other members of the community as well as exchange ideas.

    I suggest to send us a mail with detailed information about your setup, so we can analyze the problem. Please provide exact details about the used systems like operating system version numbers, VEP version numbers, what networking hardware you are using and how the computers are connected.

    Best, Ben

    Ben@VSL | IT & Product Specialist
  • F
    F

    Hi Ben, thanks for the reply.

    Why not do it here where where we can document the issue and then anyone can read the answers so then can troubleshoot on there own like on every good forums. I can't imagine this is news to you. It was  working 100% with VEPro 6 and then VEPro 7 can't see the servers half the time. That issue has to be well known inside your organisation. It's an issue on 3 out of 4 setups at the compagny I work for so it's not simply my own setup and has to do with some changes between VEPro 6 and 7.

    Maybe a support forum would be a good idea to help the whole community. I can't tell you how many times I found answers to my problems by reading other people's issues.

    But if VSL wants to hide user issues and keep every little bug out of the public eye, then it makes sens I guess.
  • bbeliusB
    bbeliusB

    Hi François,

    First of all: This is not an issue we are aware of to my knowledge. Also I have not seen many emails in this regard, and in these cases most of the times it's a simple misconfiguration.

    There is nothing to hide. It's simply our official support channel. Not all of our support team reads / monitors this forum.

    Regarding your issue, please consult the networking chapter in the manual: https://www.vsl.info/manuals/vep7/setup#network

    Best, Ben

    Ben@VSL | IT & Product Specialist
  • F
    F

    I'm sorry I though this was a known issue, this guy must have been another Ben from VSL...

    https://vi-control.net/community/threads/vepro7-after-update-cannot-recognize-server.89322/
  • bbeliusB
    bbeliusB
    last edited
    last edited

    No, don't worry, it's me. But please check the date when this was posted... and make sure you are running the latest version 😉

    Ben@VSL | IT & Product Specialist
  • F
    F

    I did both. I check if I had the latest version and then deleted the .ini file on all 3 computers. It reset all my settings but I still cant see the servers from my master PC.

    It has been setting us back for a few days now. Very painfull to work with. We are loosing a lot of time.
  • T
    T

    I too am experiencing the exact same issue.  It really does slow down the workflow.  I came here in hopes to find a solution as the first question that most support asks is "did you try to find a solution in the user forums".  I too will be contacting support so they know it is indeed an issue.
  • F
    F
    last edited
    last edited

    @bbelius said:

     your issue, please consult the networking chapter in the manual: https://www.vsl.info/manuals/vep7/setup#network

    Best, Ben

    All these steps we're already setup properly but we still can't see the slave computers since we updraged to VEPro 7. If I hear one more time this is not an issue with VEPro 7 and not even a known issue at VSL, we'll simply abandon the software. It's causing us more trouble and is more time consuming than having all of our samples loaded locally. We are running a video games sound and music company and we've wasted enough time on this allready. Please fix this and let us know when you guys have a working software.

    If only the server projects were backwards compatible, we could easily go back to VEPro 6 but even going back to VEPro 6 would be a major pain and we'd have to reconstruct our newest templates all over again. That is probably what we'll do when we get a break.

    If it ain't broke, don't fix it they say. Well now that you broke it, please fix it!
  • PaulP
    VSL Team
    PaulP

    Hello François, 

    I found one support case of yours in our database, from 2017 - would you like to contact us again, directly, with a few screenshots and more information about your system?

    Network troubles are not so easy to fix, remotely, but we can probably get there with some additional information. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • F
    F
    last edited
    last edited

    @Paul said:

    Hello François, 

    I found one support case of yours in our database, from 2017 - would you like to contact us again, directly, with a few screenshots and more information about your system?

    Network troubles are not so easy to fix, remotely, but we can probably get there with some additional information. 

    Best, 
    Paul

    I will, we have a few important tracks to deliver this week but we also really need this to work asap so I'll contact support when we've delivered. But like I said, I really feel this issue is on your end since previous versions where working flawlessly and none of our systems and setup have changed aside from the server projects.
  • PaulP
    VSL Team
    PaulP

    Hi François, 

    We're happy to take the blame, we just want to help. It looks like an exception. 

    Good luck with your project!

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • B
    B
    last edited
    last edited

    the same Issue. I've made a new thread to exaplain this.
  • M
    M

    Vienna Ensemble Pro 7 network discovery relies on standard Bonjour service.

    Please ensure that you don't have anything blocking this service - or have manually turned the Bonjour services off on your master/slave computers.
  • F
    F

    We're contacting support now but just so you know,

    We've just added a new computer as a master with a fresh install of Windows 10, all the latest versions of VEPro 7 on all slaves and master, TCP and UDP ports are setup properly, advertising on local network is turned on and the bonjours service is running on all machines. We also tried both VST2 and VST3 on the local machine. It feels like we've tried eveything and the same issue is happening on multiple setups at different locations. 

    Since my collegues and I are experiancing the same issue on different setups and networks means this is NOT a isolated case. We strongly feel we should get compensated for all the time we've spent troubleshooting this without any positive results. At this point, it feel like we are beta testing this software that is simply now working properly. We need to be able to see the servers we connect to. Manually entering the IP adresses and instance names is not a viable solution for us.

    By now, we have read the manual several times and both the manual and this forum have failed to help us in any way. We now wish there was an alternative software to VSL's Vienna Ensemble Pro.

    We strongly recommend to anyone who is thinking about upgrading from VEPro 6 to VEPro 7 to keep working with VEPro 6 as it works fine and no added features of the newer release is worth all this hassle.