Forum Jump
I have read the other threads on this topic, but they mostly deal with PC's. I have a Mac master and two Mac slave computers.
After not working with VE Pro for several months I just updated both VE Pro (to 5.4.13888) and OSX (10.11.3). I am using Logic 10.2.1. I cannot seem to connect to the slave computers anymore. No metaframes are listed. I have made sure the ethernet network is functioning.
I have tried setting the slave computers to a manual IP address as suggested in this other post (http://bit.ly/1NsI2Lz), but I have not solved the problem.
Any other suggestions for trouble-shooting this?
|
|
|
|
It seems I am able to connect to my slave computers by returning the network settings to DHCP (with the 169.254.x.x IP addresses) and manually typing in each IP address and VI frame name.
However, when I open up a another empty file, there is still nothing under the list for "AVAILABLE INSTANCES" - as there used to be in previous versions.
I have the above work-around for now, but I would still like to solve this.
|
|
|
|
Hi Ander,
I had the exact same issue although i'm running two 10.8.5 MacPros'. After i updated to the latest versions (5.4.13888) it was impossible to connect so after an hour of head scratching, i rolled back to the previous releases which are thankfully in the Software Archive. Now everything works accordingly. My Server IP is DHCP with a manual address (I use Synergy to control both MPs' with one keyboard/mouse and the server needs a static IP) and the Slave is DHCP. It is possible that there's an additional network issue also in 10.11.3 but i can't confirm as i'm still running around with ML.
Hopefully VSL will pick up on this and find the cause.
If i can help further, please let me know.
Thanks,
MD
Mac Pro 5,1 OS X 10.13.6 12 Core 3.46GHz 48gb RAM Cubase Pro 10.5 Mac Mini i7 running VEP 6 .5 Pro MacPro 2,2 2 x 3Ghz running VEP 6.5 Pro
|
|
|
|
Two thoughts for all of you:
- If you can't find the slave, yet Networking is working fine, set to DCHP, connect and then set the IP to be fixed to this address for future connecting.
- If there are no instances, look out for invasive apps like Little snitch or even check that the Firewall is set to allow VEP though.
DG
Nuendo 6.03, 4.3 2 x Intel Xeon x5675 3.07GHz Hex Core 48GB RAM Windows 7 (x64)Pro RME Multiface II Intensity ATI HD5400 series graphics card
|
|
|
|
HI DG,
Thanks for your reply.
When you say 'then set the IP to be fixed to this address for future connecting.' do you mean in the SysPrefs/Network or in the VEP pref page on the Client (The mac with the VEP plugin active in thevDAW).
Since i rolled back, it kind of works ok now but i would prefer to have the latest update etc.
Thanks,
MD
Mac Pro 5,1 OS X 10.13.6 12 Core 3.46GHz 48gb RAM Cubase Pro 10.5 Mac Mini i7 running VEP 6 .5 Pro MacPro 2,2 2 x 3Ghz running VEP 6.5 Pro
|
|
|
|
Originally Posted by: MacDude 
When you say 'then set the IP to be fixed to this address for future connecting.' do you mean in the SysPrefs/Network or in the VEP pref page on the Client (The mac with the VEP plugin active in thevDAW).
SysPrefs/Network. VEP should remember this IP for connecting in future.
DG
Nuendo 6.03, 4.3 2 x Intel Xeon x5675 3.07GHz Hex Core 48GB RAM Windows 7 (x64)Pro RME Multiface II Intensity ATI HD5400 series graphics card
|
|
|
|
Hi DG,
I'll give that a try.
Thanks,
MD
Mac Pro 5,1 OS X 10.13.6 12 Core 3.46GHz 48gb RAM Cubase Pro 10.5 Mac Mini i7 running VEP 6 .5 Pro MacPro 2,2 2 x 3Ghz running VEP 6.5 Pro
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.