Blackmagic Forum

Hi folks. I just recently purchased a Hyperdeck Studio Mini as a companion to my ATEM Television Studio. I'm currently testing two setups. 1. Using the two together without a laptop. 2. Using them together and controlling them via Laptop. This question is about the former. I've attached images of the below issues.

For some reason even though my computer (Via Blackmagic's "Hyperdeck Studio Setup" and "ATEM Setup"software) recognizes both devices without issue. When I open up ATEM Software Control it says no Hyperdeck device connected via Media Players, and if I go to preferences and try to manually ad my Hyperdecks IP address is says "failed to connect".

Anybody run into this issue? The irony is it does appear to actually work though. Because I can cut between cameras and Blk and Col1 within the Atem Switcher and the Hyperdeck follows suit. So I guess it says it doesn't work, but it does. But I do lose some functionality still because I can't Record, or preview anything.

What isthe IP address of your switcher?

Forgive the possibly weird response, but why?

Because they both have to be on the same network to connect to each other.

Also is your software up to date?

“Update your ATEM Switcher to software version 6.8 or higher. This process outlined in the ATEM Switcher manual and can even be done over Ethernet. Update your HyperDeck’s internal software to version 4.3 or later.”

Hi @Robertmsu. Got it, thanks. They're on separate networks. Do I need to try and manually adjust one of them to match then.

ATEM Software is currently 7.52

I adjusted the Hyperdecks IP Address to match the ATEM. No dice as of yet. It still functions for switching fine so it's not a big deal. But I'm assuming there are some disadvantages to the ATEM Software Control not seeing it. If it did I was going to test if I could monitor the program feed via my computer possibly.

Only the first 3 numbers should match in the IP address. The last number after the 3rd . should be different and is the IP address you enter in the ATEM setting for the Hyperdeck address.

You also need to select an ATEM Input that the Hyperdeck will be connected to (currently showing none in your screen shot) if you want auto queue to work when you select the ATEM input (assuming the HyperDeck output is connected to one of the ATEM inputs).

The HyperDeck also needs the "Remote" function enabled via the LCD menu.

As an example:

IP Addresses
Atem: 192.168.10.2
Hyperdeck: 192.168.10.3
Videhub: 192.168.10.4
Laptop: 192.168.10.5

Subnet mask: 255.255.255.0
Router: 192.168.10.1

Hmmm. So I made those adjustments.
-Remote is now turned on.
-I changed the IP so that all of it except for the last 3 numbers match the ATEM.
-I changed the input in ATEM Software Control (to Input Camera 3)

But still no dice. It doesn't recognize it. Again it doesn't stop it from functioning. I fully edit and record between the two devices. But Software Control still isn't recognizing it.

Are you getting network activity light on the Hyperdeck? Can you use the Hyperdeck Config tool to reach the Hyperdeck Mini via the network rather than via USB? Remove the USB connection from the Hyperdeck and what happens?

Also, from the Hyperdeck Mini menu where you enabled Remote, turn off DHCP. It is on by default as shown in this screen shot. Check that the IP shown is also correct in this screen for your setup 192.168.10.230

I'll throw my two cents in on this and say I'm dealing with the exact same issue, except I'm trying to run the ATEM and Hyperdeck both into my MacMini (using the built-in ethernet and a Thunderbolt to ethernet adapter) avoiding using a separate ethernet switch.





**This is basically a mobile setup where we will not need ethernet on the "video" end because we send our signal to the broadcasting side via an HDMI cable to a Boxcast.

The atem and Hyperdeck need to be connected to a switch to be able to communicate with eachother.

Hooking them both up to your laptop with separate network interfaces will cause your laptop to talk to them.. But not to eachother.

There are small 5 port and even 2 port switches if you do a good search.

We're also experimenting a strange beheavior with our ATEM 2 M/E Constellation HD.
For some unknown reason Hyperdecks (HD Plus ones) are not recognized at startup by the switcher. Albeit being the very same ones being used for a previous show.

In order to get them to be recognized/controlled by the ATEM again is to manually re-enter all the IP addresses. The same as the ones listed on startup !
The process is cumbersome as there is no refresh button to do so. So we have to put an other temporary IP address first to get the can't connect message. And only then to re-type the original IP address in order to eventually get the green "connected" mark (and the IP is strictly the same as the one listed at startup).
I have not try if the beheavior is the same with the 4 M/E Constellation HD.

And yes, we're using proper and unique IP addresses. Each device we own are listed on a specific spreadsheet that manages all of our IP addresses.

I am having the exact same issue with my client. IP settings entered correctly. Functions like normal. Power down. Upon startup, the ATEM Software Control can't find the Hyperdeck even though the IP scheme has stayed the same. Deleting, and reentering the IP allows it to connect again, but definitely don't think that should have to happen.

Anyone have a solution for this?

aaronrtw wrote:I am having the exact same issue with my client. IP settings entered correctly. Functions like normal. Power down. Upon startup, the ATEM Software Control can't find the Hyperdeck even though the IP scheme has stayed the same. Deleting, and reentering the IP allows it to connect again, but definitely don't think that should have to happen.

Anyone have a solution for this?

Try using .230 or above on the Hyperdeck IP. That solved my connection issue.