Vienna Symphonic Library Forum
Forum Statistics

181,948 users have contributed to 42,195 threads and 254,637 posts.

In the past 24 hours, we have 5 new thread(s), 14 new post(s) and 51 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VE Pro reluctant to see Slaves (please someone help out?? demo runs out..)

  • VE Pro reluctant to see Slaves (please someone help out?? demo runs out..)

    L
    L
    hi! i downloaded the demo of VE Pro and bought a vienna key to thouroughly test VSL Ens Pro before taking the plunge and enter the world of VSL... so far i have done anything the manual said but there are no slaves turning up where i can connect to. first thought would be a faulty network, but i'm running a macbookpro, asus laptop and 2 pcs in a network without any problems whatsoever (sharing mouse and keys with synergy, synced and shared folders, firewalls off with the pcs, on the laptops all DAWs are allowed to peek through) i'm runnign out of clues what can cause this..## anyone care tho share some input? i can't really go and test along while my demo gives me 10 startups left so i have to make this work fast before i can even consider buying VE Pro. # running Snow Leopard and Windows 7 / Logic9 and Samplitude 11.03 here. have also tested ableton live, reaper and renoise as hosts but with the same problem... thanks so much! enjoy your days! dikkie
  • D
    D
    1. Fixed IP? 
    2. All Firewalls off, not just the PCs?
    3. No ports blocked?
    4. No wireless networks enabled?
    5. Dongle with licence plugged into the PCs you want to "see"?
    6. Servers running before trying to connect?

    DG
  • L
    L
    last edited
    last edited
    dikkie

    @DG said:

    1. Fixed IP? 
    2. All Firewalls off, not just the PCs?
    3. No ports blocked?
    4. No wireless networks enabled?
    5. Dongle with licence plugged into the PCs you want to "see"?
    6. Servers running before trying to connect?

    DG

    hey DG!
  • 1: yes all four of em
  • 2: not untill you mentioned it but didn't solve the issue
  • 3: ? sorry if i come across as a beginner here, but if i disabled any firewalls is there still a chance ports are being blocked? any way to monitor this?
  • 4: not untill you mentioned it but didn't solve the issue
  • 5: yes
  • 6: yes
  • thanks for your fast reply!
    • small question, it can't have anything to do with either audio or midi drivers missing on the slave units? as far as i know all audio and midi will be streamed to the host so it shouldn't matter if the computers have their soundcards properly installed...? tnx!
  • PaulP
    VSL Team
    PaulP

    Hello dikkie,

    The connection between master and slave computer does not depend on audio or MIDI drivers...but it always helps to have the right driver for your soundcard installed [;)]

    Did you try to connect 2 computers straight ahead with a LAN cable?

    You can "recharge" your 30 demo starts as often as you like within the 30 days you have (click on "Validate License Usage Period" in the eLCC), so no worries here.

    Best, 

    Paul

    Paul Kopf Product Manager VSL
  • L
    L
    drivers make life easier i know :) still haven't been able to get things work. a thing i noticed is that in different hosts the Ensemble plugin either gives me the option to push the 'connect' button, entering the interface where my slaves should be mentioned where everything is just blank, OR pushing the connect button doesn't work at all. strange. i have a feeling it has something to do with windows 7. although all my networks run perfectly mayby i should try to get a xp machine in and see if i get that working. thanks for the recharge tip btw. helped me out already! i'm certainly interested in people who have VE Pro up and running perfectly with windows 7 in their setup.. thanks anyway everyone!
  • PaulP
    VSL Team
    PaulP

    Hi,

    I forgot to mention that there is a bug in the current public beta version that makes the Server Interface and GUI of VE PRO behave weirdly on a second monitor. This is already fixed for the upcoming version. Meanwhile, you can check out VE PRO 4.0.5436 if that is the problem now.

    Please let me know if that helped!

    Best,

    Paul

    Paul Kopf Product Manager VSL
  • J
    J

    Which computer do you have he dongle connected to? Slave or Host? 

    Try putting the VEPro dongle on the SLAVE machine and see if this changes anything.

    The HOST machine does not need the dongle -- only the slave.
  • J
    J
    Hi, I've got the same problem: Since I've upgraded to windows7 on the host (already had it installed on the slave) the vst plugin sometimes just can't find the slave till i restart both machines. I'm not entirely sure why this happends sometimes, but it looks like when there's something changed in the network it can't find the slave anymore. For example: when i unplug my usb WIFI adapter with which the host can be connected to the internet. Or change something in the network settings to test another setting, like enable or disable jumbo frames. The network itself seems to work after such a change, ensemble just can't find it's slave anymore. XP didn't have this problem.
  • L
    L
    last edited
    last edited
    hey everyone, for the first time i had my master recognize there are other computers in the network! haven't had time to test stuff out yet but i'm happy i'm seeing progress.

    @jvdieks said:

    Hi, I've got the same problem: Since I've upgraded to windows7 on the host (already had it installed on the slave) the vst plugin sometimes just can't find the slave till i restart both machines
    i solved the issues by A: disable bonjour service (http://arai.wordpress.com/2008/02/11/completly-uninstall-and-remove-bonjour-service-and-files-mdnsresponderexe-and-mdnsnspdll) B: assigning a default gateway in my gigabit network TCP/IPv4 settings and C: dissabling all TCP/IPv6 options... let me know if this works out for you!
  • J
    J
    Thanks, I'll try disableling bonjour. Allthough it could very well be that your network just changed from public to home because you set the gateway. You need to set a gateway in windows7 for your network to be a "home" network.