Unable to stream with ATEM Mini Pro directly on network

Wow, Adrian, this sounds awfully painful.
If you assign the ATEM a static IP - can you check your router and determine whether the router thinks you're a client? When you switch it to DHCP - does your router's dashboard show any sign of that client - or do you have access to any router logs that might indicate why the DHCP request is being rejected?
It sounds like your router is refusing to forward your traffic - your Mac has no such reluctance which is why that's working when you passthrough the Mac (because the router sees the Mac as a client).
We have an ATEM Mini Pro - we have used it with static IP, but I now leave it on DHCP - it has worked fine in both modes to stream to YouTube.

Good luck!

Tom

Just a suggestion:

Through the years I have always had need of some devices to have "static" IP's. This can be a challenge to manage. There are a number of ways to do this, there is no "right" or "wrong" way, there are just trade offs with each option.

The easiest way I have found to do this is by setting all devices to "DHCP", this allows management of all "static IPs" to be performed in one location: The Router.

If you look in the router you will likely find an option to assign a "static IP" to a given "DHCP Lease". Thus, all devices on your network use DHCP, but through the router settings some devices are exclusively assigned a static IP. This allows you to move things around when you need to, but also allows you to go into your router and actually see the leases and often their status (device online or not, and or time of assignment = power cycle the device). This then leads to a number of debugging options when things break that you don't have when the IP assignment is in the device itself.

The difficulty with this procedure is initial discovery of the device itself in order to edit its "DHCP lease". This usually must be done using the device's MAC address which Black Magic does not provide on the device itself, and from and IT perspective feel this is wrong (*) and all devices should make their MAC address available even if a bit buried in a menu.

As I recall the name you set a Mini Pro to is the name that appears on the DHCP lease in the router -- I can't access the network to verify this at the moment, but this is generally true of all devices. So set the Mini with a unique name and to DHCP. Then go to the router an look at the leases (may also show up in something called the "ARP Table") and look for the name of the Mini. On this list entry you will likely find the MAC address to, I copied those onto a label and stuck them to each of our Mini's.

So lack of the MAC address on the Mini introduces an added setup set for this method of network management, and for someone that has never done this and has no clue what I'm talking about, it may seem a bit overwhelming. But once you do it I think you may see the benefit. Then the next device you add to your network, and you follow this procedure, I think you may see how easy it can make things and allows you to detect problems. For example, a building switch got unplugged, or a cable failed or was damaged. Looking at the DHCP list often in your router you may notice (because you have built a mental image of what is right) a number of devices missing from the list, then it will hit you its not just that device but those devices on that switch. Problems just begin to stand out when looking at the list, because now everything is in one single place and being managed in that single place.

HTH

Charles

* Under the hood: The MAC address is used to establish device IPs, so the MAC address is more foundational to network communications that the IP is. In fact networks do NOT need an IP to be utilized and communicate. IP's actually "ride on top of" MAC addresses, which is how a switch works and knows how to route traffic .... Its a pedantic point, but very important to networking and sometimes very useful when debugging. And debugging is why it should be provided on the device.

There are four or five threads about ATEM Mini Pro/ISOs not getting DHCP addresses and mixed results getting them to work. This is the longest thread and just in case it helps anyone else, I'll I'd add my experience of the same and my diagnosis and solution.

My ATEM Mini Extreme ISO would not get an IP address via DHCP (it would eventually self assign an IP) nor would it stream (flashing ON AIR button), however both ATEM Setup and ATEM Software Control could otherwise see and control the device. An ATEM Mini PRO I also have has no such difficulties.

I hadn't thought to check before - because, well, why would you?! - but it turns out the NIC (ethernet port) has not been assigned a MAC address in the factory! It's pretty easy to work this out if you have the same issue:

Connect to your network and either assign a static IP or let it self-assign one. Check the IP in ATEM Control via the USB cable and then (on a mac) open terminal and type 'arp -na' (there is a similar command for CMD prompt on windows). You'll get a list of all the IP and MAC addresses of the devices your MAC/PC has recently discovered. Check for the entry with the self-assigned IP show in ATEM Control or static IP you gave it and if you see a MAC address of 0:0:0:0:0:0 (or 00:00:00:00:00:00) against that IP then the device clearly hasn't been properly programmed or tested on the production line. No amount of tweaking your network settings is going to get it to work.

I called up BMD and an RMA is being arranged. I am told I'm not the first but it's rare and connection problems are more usually network config or cabling issues. It's a hardware issue in the sense that the NIC hasn't been properly programmed, and it seems they won't try programming it on return but will send out a new unit.

I have been having a issues with my Extreme ISO from day one. Reading this entire thread is exactly what I have been going through. I have such a simple network. This should not be this difficult.

I have returned my Extreme 2x. Once for a fan that sounded like a jet engine and one for not being able to connect to it over the network or to stream. Yet, I have 2 other units that work fine, the ATem mini pro and pro iso.

My question is. In all of my time spending on this, for those that have had this issue, does their ethernet port ever go green or does it stay amber?

I've finally got it working by making a bridge connection between the wifi and the ethernet connection in the laptop. But sometimes I loose control over the atem via software when streaming. If I want control I have to connect it via usb also. But With the bridge I can stream from the atem connected to the ethernet port of the laptop via the wifi connection of the laptop. Is a solution for a needed situation.

I have an ATEM HD8 ISO and am having the exact same issue.

Was there ever a real fix for this? My ATEM Televsion HD8 ISO is having the same problem. cannot connect to streaming media. just hangs and fills the cache.

"Connect to your network and either assign a static IP or let it self-assign one. Check the IP in ATEM Control via the USB cable and then (on a mac) open terminal and type 'arp -na' (there is a similar command for CMD prompt on windows). You'll get a list of all the IP and MAC addresses of the devices your MAC/PC has recently discovered. Check for the entry with the self-assigned IP show in ATEM Control or static IP you gave it and if you see a MAC address of 0:0:0:0:0:0 (or 00:00:00:00:00:00) against that IP then the device clearly hasn't been properly programmed or tested on the production line. No amount of tweaking your network settings is going to get it to work."


Wow!
After many hours of studying I found this gold nugget of information.
My arp -a reveals just that: DHCP given address starts with 169.254 and physical address is full of zeroes.

I had a similar problem.
My ATEM Pro and Extreme are only connected to the router by Ethernet. They are NOT connected to my computer.
ATEM software control would show up on my monitor.
but
The LiveStream light would blink Red instead of solid and I could not stream.
I had to unplug the ATEM and plug it in again.
Then the Router would assign an IP address and everything worked.

The ATEM mini Pro is connected by cable to a TP link wireless extender.
As long as I have the extender powered I have no more problems.

The ATEM mini extreme is connected to the router 300 feet away by Ethernet cable.
As long as I have the splitter that also feeds my work station computer powered, I have no problems.