Vienna Symphonic Library Forum
Forum Statistics

193,964 users have contributed to 42,904 threads and 257,885 posts.

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

  1. Home
  2. Software
  3. Vienna Ensemble Pro 7
  4. USB 3 to Ethernet adapter not being recognized by Vienna

  • USB 3 to Ethernet adapter not being recognized by Vienna

    E
    E

    Hi Vienna team,

    I have two PCs, one acting as the master and the other as the slave, both running Windows 10 and Vienna Ensemble Pro 7.

    Both PCs are equipped with 1.0Gbps USB 3 to Ethernet adapters to connect to my home network.

    However, Vienna on my master PC fails to detect the Vienna server on the slave. Interestingly, when I connect the network cable directly to the motherboard of the master PC (which operates at 100Mbps speed), my DAW on the master PC can see the IP address and instances.

    I'm aiming to have both computers run at 1Gbps Full Duplex, not just 100Mbps.

    - Could you please advise on why Vienna is not recognizing the 1.0Gbps USB 3 to Ethernet adapters on my master PC?

    Adapters: https://www.amazon.com/dp/B08KWC7D78?ref=ppx_yo2ov_dt_b_product_details&th=1

    Thank you.
  • Andreas8420A
    VSL Team
    Andreas8420A

    Hi!

    I can only add that I also use some 10€ USB3 to Ethernet adapter I purchased off Amazon 3 years ago, and never had issues. I am afraid all you can really do is try a different adapter.

    VSL Team | Product Specialist & Media Editing
  • E
    E

    Hi Andreas,

    I've encountered a peculiar issue with my setup. Both PCs are set to automatically obtain IPv4 addresses via DHCP, with no manual IP addresses configured. Sometimes, my master PC DAW can see the IP address of the slave, and other times, it cannot. This inconsistency is quite frustrating. Rebooting both PCs sometimes resolves the issue, but not always.

    Furthermore, when the server does not appear in my DAW Vienna plugin, and I manually enter the IP address of the slave, it creates its own instance on the slave server. This behavior is quite odd and not what I intend. I simply want to connect to my slave without any complications.

    Any insights or suggestions would be greatly appreciated.

    Thanks!
  • PaulP
    VSL Team
    PaulP

    Hi Epicurse,

    I'd go with static IP addresses, as suggested in the VE Pro 7 Manual.

    "You should use static IP addresses, and avoid 169.x.x.x addresses (these are automatically assigned by your computer and tend to change).

    A classical stable setup may look like this: Manually assign one of these IP addresses to the computers in your setup: 192.168.0.x or 10.0.0.x, and assign a subnet-mask of 255.255.255.0. If you are working with a router, you should add the IP address of the router (e.g., 192.168.0.1)."

    Paul Kopf Product Manager VSL
  • Andreas8420A
    VSL Team
    Andreas8420A
    @Epicurse said:
    This inconsistency is quite frustrating.

    DHCP stands for Dynamic Host Configuration Protocol. Meaning: Your network gets random IPs assigned, and they can change at any time. Hence, we highly recommend avoiding random IPs and going with static ones.

    VSL Team | Product Specialist & Media Editing
  • E
    E

    This issue was resolved by me adding all the IP addresses in the HOSTS file located in the "C:\Windows\System32\drivers\etc"

    Thank you all for your help.