Vienna Symphonic Library Forum
Forum Statistics

181,970 users have contributed to 42,196 threads and 254,641 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Urgent help needed: Slave not appearing anymore!

  • Urgent help needed: Slave not appearing anymore!

    D
    D

    Hi,

    So I set up VE3 on my G5 slave via ethernet yesterday and everything worked fine. This morning I can't get the MacPro (running Logic) to see the slave (under available slaves there are no machines listed). The network is connected properly and the VE server running on the slave. Any ideas? It's not a license issue. 

    Thanks,

    David 
  • D
    D

    When I put the dongle in my main computer and load the VE3 Service app, I can use VE3 on the local host, but no joy on the network slave. Anybody seen this before? Am I missing something obvious? - as I say, it was working yesterday.

    D 
  • T
    T
    Sometimes VE3 doesn't pick up the available host names - not sure exactly why but it's probably something to do with the way networking is setup on your Mac rather than anything else. Simplest thing to do is just manually re-enter the IP address of the slave.

    However, this problem should only occur when you're creating new projects, existing projects shouldn't suffer this problem at all.

    Regards

    Tim
  • M
    M

    I´d recommend the same. Please enter the IP of your slave computer manually (you´ll find it in System Preferences/Network).

    Best regards,

    Maya 
  • D
    D

    Thanks Maya & Tim - after a few hours and several restarts, I eventually got it to 'find' the slave again, but will keep that trick up my sleeve if it happens again! Best,

    David 
  • cmC
    VSL Team
    cmC

    david, this is an issue related to multihomed computers (= such with more than 1 network interface) - though VE3 on the SLAVE should annunce itself on all networks the MASTER does not always listen to all. there is a thing called *order of binding* and you can notice a similar effect with filesharing to more than one network.

    having fixed IPs on your audio network and connecting to such a known IP works always (as long as the connection itself works)

     

    an important part to check is to have no multiple gateways on a single computer (on a mac labeled router) - only the network intended to be used for internet connections should have the appropriate gateway set, it tells the computer where the *door* to the *wide world* is

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • D
    D

     Hi Christian,

    So this happened again and I did as Maya and TIm recommended and entered the IP address manually and it worked! However, I'd really like to stop this happening as it means everything takes a bit longer to get going on the music - especially as I seem to have to do this with every project I load up.

    But I'm afraid I don't understand your advice on how to fix this (I don't know much about networking). I don't have a router - I just have an ethernet cable running between my G5 and my Mac Pro, but there are other machines (laptops) on the wireless network. Can you explain a bit more what you mean about gateways and so on (feel free to email me instead). Many thanks,

    David
  • cmC
    VSL Team
    cmC

    this is a question of *order of bindings* and there is no easy way to change this order - especially if you are not familiar with networking i wouldn't touch anything ... a macPro has 2 network interfaces and i can't tell which is the first and which the second ... if the other one is not in use you could try to disable it.

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • T
    T
    last edited
    last edited

    @dschweitzer said:

     especially as I seem to have to do this with every project I load up.

    David - this shouldn't happen at all as saved projects note down the IP address or Machine Name and you shouldn't need to reconnect with every saved project. New projects yes this could be expected unless you use a template (which in itself would already store the IP address for the connection).

    Now, I think (and I'm hoping I'm right) that the issue is your networking, you say you aren't using a hub just a straight cable between G5 and MacPro, I am also assuming you've turned the wireless off on both (this could cause issues and also reduces performance of VE3). If that is the case then I think the problem lies in the fact the MacPro and G5 are automatically negotiating IP address each time. You really need to use fixed IP addresses on both machines. For example, my setup is as follows

    MacPro 10.0.0.2
    MacMiniA 10.0.0.3
    MacMiniB 10.0.0.4
    etc

    With automatic address allocation your machines obtain a different number each time which is why you need to reconnect on every project load. It's worth noting to users who have hubs that DHCP could cause the same problem too. Fixed IP is the best way to setup VE3.

    Now if you are using fixed IPs then I'm stumped and have spent too long typing this post.

    Please keep us posted...

    Regards
    Tim
  • D
    D

    Hey that's really helpful Tim. I got it all working now with fixed IPs... I thought those IP numbers were rocket science, but I just copied yours and it seems to work!

    Thanks,

    David 
  • T
    T
    Excellent news - glad I could help!

    VSl Team - might be worth adding some notes to the tutorials about using either manual fixed IP or static DHCP addresses for the DAW and slaves....

    Tim
  • O
    O
    Hi, I have a similar problem as above ... My Set-up is: 1. MacBook (2.1Ghz Intel Core 2 Duo 4GB) as my 'main' computer on Logic 8 2. G5 (Dual 2.3Ghz 5GB) as my 'slave' computer running VSL VI Special Edition 3. Ethernet cable which works; e.g. I can share files between the two with no problem. Vienna Ensemble 3 (demo) is installed on both. When I come to set up the VE3 on Logic (multi output), it sees my slave machine with IP address (which has the VE Service already up). My problem is that it always FAILS to connect. Networking: MacBook IP is 169.253.41.116 Subnet: 255.255.0.0 G5 IP is 169.254.239.143 Subnet: 255.255.0.0 >>> set up with DHCP With DHCP at least I actually have the Main computer seeing the slave. When I set up with a manually fixed IP address (as yours above) 10.0.0.2 etc VE3 doesn't even see the slave. Throughout this process Airport Wireless is OFF. And file-sharing works fine. Weird eh? Any idea where I might be going wrong? Is it something to do with Intel vs PPC? O.
  • cmC
    VSL Team
    cmC

    welcome owain,

     

    you share files probably using afp-filesharing or something else ... but your TCP/IP configuration is definitely not working ....

     

    both IP addresses are from a different class B network (since you choose mask 255.255.0.0 this will not work) and are from the auto-configure range ...

     

    i'd recommend to use class C networks instead with a netmask of 255.255.255.0 and IP address range withing 192.168.x.y

     

    where x and y are between 1 and 254, on both computers x needs to be the same, y to be different

     

    attention: if a single computer has more than one network interface 2 of them MUST NOT reside in the same class C network and only one gateway must exist (to the internet) ... don't forget wireless adapters ...

     

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • O
    O
    Fantastic! thank you for this Christian. VE3 is up and running at last! Maybe there should be a small paragraph on this in the manual? O.