ATEM Mini Pro IP address - How To Find It

My ATEM Mini Pro works fine when the USB-C out is connected to my iMac 27". The ATEM Controller software sees it and connects beautifully.

Part 1

I added an Ethernet network hub and connect my iMac and my ATEM Mini Pro to it and then run an Ethernet cable to my Internet Router. The router runs my Wifi just fine.

I used LANScan to identify devices on the network but can't see the ATEM Mini Pro even though it's connected with brand new cables.

The following is a picture of the LANScan output
/Users/paulcrick/Desktop/screenshot_25.png

I followed this YouTube video's guidance

but can't get it to work.

Part 2
Having had a play, I can see that when connected via USB-C the ATEM Setup offers two options:

1. DHCP

Here the IP address is 0.0.0.0
The subnet mask is 255.255.0.0
Gateway is 0.0.0.0
Primary DNS is 8.8.8.8
Secondary DNS is 8.8.4.4

2. Static IP

I've entered the default ATEM IP address 192.168.10.240
Subnet mask is the same
Gateway (Router) is 192.168.1.1

The ATEM Software Control works fine over USB-C but not over Ethernet. The Ethernet cables are all new. The (brand new) TP-Link Hub has flashing LEDs for the Router and for the iMac but not the ATEM unit.

The idea was to make the set up more flexible in terms of where the streaming was controlled from.

Many thanks for your help.

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).

Ethernet switches have such LEDs and I believe there are LED indicators on the Ethernet port of the ATEM Mini as well. 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.

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. This could either be due to a hardware-level issue (as described above) or a problem with the router/DHCP server.

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. So for example, a gateway IP address of 192.168.1.1 may or may not be correct depending on your local network.

Thank you. I’ll check all of those out this morning and report back.

Happy to report that a complete shutdown and reboot of everything now means that the setup now works as intended and all parts of the network are labelled and functioning as they should.

Thanks for the help and suggestions.

Cheers
Paul

Hi there - Whilst being a 'crack' when it comes to content creation, network setting are not my forte. 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. 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. This may be a wrong assumption - as I dont seem to be be able to change the ATEM's IP number. I can only take ATEMS existing IP and add it to Companion so that Atem 'talks' to companion and Comapnion 'talks's to StreamDeck.... now the Status on Campanion shows green OK, so thats great. 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... Thanks

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. You will usually run into problems if you assign two devices on the same local network the same IP address.

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. Here's an overview of some computer networking basics that may help (you can find lots more if you search online): https://www1.chapman.edu/~boldu101/netw ... basics.htm

If the ATEM is configured to use a dynamically assigned IP address (DHCP), then it will be assigned an IP address automatically by a network router (or other DHCP server) on the local network that it is connected to. If you want to assign the ATEM a static IP address, this may be done using the ATEM Setup utility software when the ATEM is connected to a computer over USB. How to do this is described in more detail starting on page 90 of the ATEM Mini Manual: https://documents.blackmagicdesign.com/ ... 1017210000

Finally, a post online that describes this nonsense in detail with a video to see. Thanks for sharing mate. I was about to break this thing in pieces.