Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Options
Go to last post
Posted on Tue, Jul 20 2010 16:04
by Jeffrey Peterson
Joined on Thu, Jul 01 2010, Posts 17
Also should you run your cable through a router or switch or directly from PC to PC? How long can the cable be?

Thank you

-Jeffrey
Cubase 5.5, Pro Tools 8.0.4, VE Pro, i7 920 Master, i7 930 Slave. PLAY 2.0.21. Omnisphere, RMX.
Posted on Tue, Jul 20 2010 21:46
by Jeffrey Peterson
Joined on Thu, Jul 01 2010, Posts 17
This is a very simple question...anybody?
Cubase 5.5, Pro Tools 8.0.4, VE Pro, i7 920 Master, i7 930 Slave. PLAY 2.0.21. Omnisphere, RMX.
Posted on Wed, Jul 21 2010 07:02
by Anthropy
Joined on Sun, Mar 26 2006, Watson, Posts 74

I connected mine two computers directly together with a straight cable.

good luck! 

RW

Posted on Wed, Jul 21 2010 07:40
by DG
Joined on Wed, May 12 2004, Posts 8608

Traditionally you would have had to use a crossover cable, but according to the VSL software developers a normal cable should be fine. You could also use a switch, but a router should be avoided.

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
Posted on Wed, Jul 21 2010 09:58
by yt020490_13791
Joined on Wed, Apr 20 2005, Posts 40

We have two rigs, each with a pair of Mac Pros (nehalem).

In each setup, the master Mac Pro has a long (straight) CAT6 cable going from Ethernet port 1 to an Apple Airport router to provide an internet connection and network file sharing etc.

For VEP, a dedicated and very short CAT6 (straight) cable is run Port2<->Port2 between each pair of Mac Pros. (The Mac pros automatically implement a hardware crossover).

I've then set up so that on Ethernet Port 1, the master Macs have IPs 192.168.1.10 and 192.168.1.11 on our studio network (via the Airport). And CRUCIALLY, on Port 2 BOTH of the master Mac pro's have the IP 192.168.2.1 and BOTH slave Mac pros have the IP 192.168.2.2.

Neither slave machine is connected to the Airport Router, as this would allow both slave machines to be seen from each master machine (this wouldn't allow us to load cues in either studio, and have VEP to connect to the correct slave machine for that studio). I have ethernet cables that are available to be plugged between the Airport and the slave machine's port 2's for doing installs and updates, but day to day, the slave machines are without internet connection. DO NOT USE OSX's BUILT IN INTERNET SHARING FEATURE! (Which allows you to pass an internet connection between ethernet ports on a Mac Pro) I SPENT DAYS TRYING TO FIGURE OUT MAJOR AUDIO DROPOUT ISSUES, EVENTUALLY I FOUND THAT OSX'S INTERNET SHARING WAS THE PROBLEM! (bear in mind this was several VEP versions ago - it _might_ not be an issue anymore).

So each master Mac participates in two networks, one to the rest of the world via the router, and also in a micro network of only itself and its corresponding slave (with each of the two micro networks set up with identical IPs). This way we are able to load cues in EITHER studio, and VEP will automatically connect to instaces on the appropriate slave machine.

It works great! Hope my rather lengthy post makes sense and is useful to someone!

Will

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.