What is true about devices on a local network is that they need to be within the same local subnet IP address space in order to be able to communicate with each other without going through a router. You will usually run into problems if you assign two devices on the same local network the same IP address. Generally speaking, every device on a local network has a unique IP address as the IP address is used to route network packets to a particular device. But what happens if i want to broadcast live via the Ethernet connection that I have connected to a Switch (plugged in Router cable + ethernet to PC + Ethernet to Atem Mni Pro) - would I be able to still braodcast via Ethernet conencted to ATEM Mini Pro although the IP address of the ATEM-Comapnion connection is now not the same as the static IP address that I created in my Windows 10? Terribly confused. now the Status on Campanion shows green OK, so thats great. I can only take ATEMS existing IP and add it to Companion so that Atem 'talks' to companion and Comapnion 'talks's to StreamDeck. This may be a wrong assumption - as I dont seem to be be able to change the ATEM's IP number. Now my understanding was that I would need all devices in the production chain to have the same IP number so they can communicate with each other. Here is my "silly" question: I changed my Win 10 IP address to a static IP address as it seems that dynamic IPs may change the IP and make my computer no longer communicate with Streamdeck and/or ATEM Mini Pro. Hi there - Whilst being a 'crack' when it comes to content creation, network setting are not my forte. So for example, a gateway IP address of 192.168.1.1 may or may not be correct depending on your local network. If using a Static IP address, you'll want to make sure that you use the gateway IP address and network settings from your router. This could either be due to a hardware-level issue (as described above) or a problem with the router/DHCP server. If DHCP settings report an IP address of 0.0.0.0, that generally means that it could not obtain an IP address from the DHCP server. If you have an Ethernet cable connected and devices at either end of the cable powered on and you don't see any LED activity for that connection at either end, that is a good indication of some kind of problem at the Ethernet layer such as: bad port on the Ethernet switch, bad Ethernet port on the ATEM Mini, or bad network cable. Most Ethernet ports have link status and activity LED indicators, these are often solid indicate if an Ethernet link has been established and start flashing to indicate that there is network activity on the link (colors vary depending on the manufacturer).Įthernet switches have such LEDs and I believe there are LED indicators on the Ethernet port of the ATEM Mini as well.
0 Comments
Leave a Reply. |