Vienna Symphonic Library Forum
Forum Statistics

182,270 users have contributed to 42,216 threads and 254,745 posts.

In the past 24 hours, we have 3 new thread(s), 25 new post(s) and 38 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. Microsoft Remote Desktop and VE Pro - Running them on separate ethernet cables

  • Microsoft Remote Desktop and VE Pro - Running them on separate ethernet cables

    G
    G
    I posted this question over at gearslutz.com first but maybe this forum is a more appropriate place to ask this. I'm running VE Pro on a slave PC with my Mac Pro running PT. I can get no crackling with the buffer size set to 'none', which is great. Although, things change as soon as I run the remote desktop software to control the PC from my mac, and the only usable latency is x2. I'm using a second keyboard and trackball on the PC but I'd rather get rid of all that. Since I have two ethernet ports on my mac and I can install a second ethernet card on the PC, is it possible to configure one of the mac ethernet ports to send the remote desktop data and the other to deal with VE Pro exclusively? That way there wouldn't be the bandwidth problem which I'm experiencing right now.
  • T
    T

    Yes it is (I think)

    You would need to configure separate IP addresses for each card and each machine.  Don't use automatic IP allocation or DHCP (off a router).

    So for example you could have

    MacPRO - NIC#1     IP:  10.0.0.1 (VEPRO Traffic)

    MacPRO - NIC#2     IP:  10.0.1.1 (RDP Traffic)

    PC NIC#1 IP: 10.0.0.2 (VEPRO Traffic)

    PC NIC#2 IP: 10.0.1.2 (RDP Traffic)

    Also set the VEPRO NIC to be higher in OSX network stack (i.e. move it to the top)

    Also ensure you are using a direct connected ethernet cable (i.e. no router in the middle) and that each route has no default gateway specified otherwise the computers get confused.

    Sorry if that's all a bit techie...

    Tim
  • G
    G
    Thanks timkiel, I've tried to configure both the mac and the PC the way you described it in your post. Unfortunately, it doesn't work but I noticed one thing. I can use only the mac ethernet port that's highest on the stack, so if ethernet n.2 is at the top of the stack list in osx, that's the only one that VE Pro and RDC will see. Do I have to install a pci-e ethernet card on the mac pro to get a working second connection? Thanks in advance for any help.
  • W
    W

    I don't think so - but only because I got it to work on my system (I'm no expert in this!). If it helps, I use the following numbers:

    Master Mac Pro:

    Ethernet 1 (connects also to internet) IP4v: "Using DHCP with manual address"  IP: 192.168.0.110; Subnet Mask: 255.255.255.0

    Ethernet 2 (connected directly to MacPro slave): P4v: "manually" IP: 192.168.2.110 ; Subnet Mask: 255.255.255.0 Router and rest left blank!

    MacPro slave: IP4v: "manually" IP: 192.168.2.111 ; Subnet Mask: 255.255.255.0 Router and rest left blank!
  • G
    G
    I finally got it working. I'm no expert either so I must have been lucky :) Anyway, I used the IP numbers as described by timkiel but on the second port I used the following address, 11.0.0.1 on the mac pro and 11.0.0.2 on the PC. So, now I have RDC on one ethernet cable and VE Pro running on the other. In addition, I can also see the ethernet cable/connection used by RDC in the VE Pro plugin inside PT. Unfortunately, the performance hasn't improved on my mac pro so I'm forced to use 2 processors out of 4 available. Maybe that's just a PT problem.
  • T
    T

    Glad it's working for you.

    Be careful about using 11.*.*.* addresses as these are not classified as private, but as long as you aren't trying to connect to the Internet from these machines you will be ok.

    10.0.0.* and 10.0.1.* should be fine but ensure you use the subnet 255.255.255.0 for both otherwise you would get problems.

    Regards

    Tim
  • G
    G
    Thanks Tim. Both the mac pro and the PC are not connected to the internet. What's so dangerous about 11.*.*.*.*?
  • T
    T

    It's not dangerous, but 11.* addresses are not reserved so they actually belong to people out there on the Internet.

    10.*, 172.16.* - 172.31.* and 192.168.* are all reserved for private (or internal) networks so you can use these ranges as you see fit. 

    everything else can be used by people on the Internet which would mean you couldn't connect to some sites for example vsl.co.at is located at 212.24.125.70 so if you had set one of your slaves to this number you wouldn't be able to connect to the vsl website.

    Interestingly 11.0.0.1 is the US Department of Defence (DoD) Registry Service so you wouldn't want to mess with that ;-)

    Regards

    Tim