Vienna Symphonic Library Forum
Forum Statistics

193,985 users have contributed to 42,905 threads and 257,892 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VE Pro slave randomly not appearing

  • VE Pro slave randomly not appearing

    P
    P

    I'm running build 5436 on two computers. The host computer runs Cubase 5.1.1 in Windows 7 x64 and the slave runs Windows XP. I'm running VE Pro 32-bit Server both locally on the host as well as on the slave.The firewalls are disabled for both.

    Most of the time these days when I fire up my session, the plugin in Cubase simply doesn't see the slave computer over the network. Usually this gets fixed by closing all the programs and then starting again. It's frustrating because there doesn't seem to be a pattern to this, and I'm spending a lot of time doing restarting, basically every day.

    The weirdest thing is that I can start an empty session in Cubase and then the plugin *will* see the slave, but when I load my full session, it's missing again. It's just really random. Then it suddenly gets fixed when I close everything and start everything up again.

    Is there any way to debug this issue further? There doesn't seem to be e.g. a manual way to connect to an IP address from the plugin. I've made sure again and again that the network is fine between the computers and traffic's not getting blocked, so there's something else going on, but it's really hard to tell what.

    EDIT: Forgot to mention that the local server appears in the plugin every time. It's simply the other computer that's randomly missing.
  • M
    M

    This sounds indeed odd. First of all please check to have the same version of VE PRO installed on all of your computers. Moreover please check if all of the ports which are needed by VE PRO are opened in your router and/or Firewall settings.

    Here is a description of the used network ports:
    6472: 32bit server connection (TCP)
    6473: 64bit server connection (TCP)
    6474: 32bit server discovery request (UDP)
    6475: 64bit server discovery request (UDP)
    6476: 32bit server discovery response (UDP)
    6477: 64bit server discovery response (UDP)

    Best regards,

    Maya
  • P
    P

    Thanks for the port descriptions, very informative. Both computers here are running build 5436, and the ports should be open, since I don't even have a router in between, just a switch (and for what it's worth, the same happens with a direct link with a crossover cable). And the computers have their firewalls turned off.

    However, what is really interesting is that as I mentioned in the other thread, I changed my slave computer name and the instance name to only include letters from "89eiodfghjklcbn", which are the only characters I can input manually in the VST3 client on this build. Of course, I did that so that when the computer doesn't appear in the list, I could input it manually... the only thing is, now it appears every time, so I don't need to!

    So, unless I'm having weird luck here, it *could* be the input and discovery bug are related in some way.
  • K
    K

    You'll be glad to hear that the input bug has been fixed for the next update. On another note, make sure you are not using the VST2 and VST3 plugin at the same time, because this could lead to slaves not showing in either one of them.
  • civilization 3C
    civilization 3C

    This has occurred two or three times for me. I am running 5436, slave and master, never used VST2 as a plugin.

    It has occurred after Cubase 5.1.1 has been using the instances in question but after coming back to that project after working on another.

    However, 'new' instances are available. It's just not giving me the named instances in a metaframe in these cases. Quitting both hosts, restarting the slave and relaunching solves it, but this means loading samples one more time. One of these instances not shown is purely VI and Vienna Suite, by the way.
  • D
    D

     You guys are using fixed IP, aren't you?

    DG