ATEM Mini TCP/UDP protocol

Hi

I would like to control my ATEM Mini with TCP. If I have fully understood, HyperdDeck protocol is not working for ATEM Mini.

I have make some network analysis and discover that 2 ports are open on the ATEM Mini.
TCP 9977 :
telnet 172.19.1.99 9977
Trying 172.19.1.99...
Connected to 172.19.1.99.
Escape character is '^]'.
PROTOCOL PREAMBLE:
Version: 1.0

ATEM SWITCHER DEVICE:
Model name: ATEM Mini
Unique ID: 2f3a0ea8c7c14fb48f3XXXXXXX
Label: ATEM Mini
Host name: ATEM-AVA-7c2e0dXXXXXX

END PRELUDE:

And port 9910 UDP.

TCP9977 is used by ATEM Setup, and UDP9910 by ATEM Software.

Does anyone knows which is the protocol used for 9910 ?

My goal is to send datagram to change preview, source, etc ...

Many thanks,

The raw control protocol is not available, the only supported method of doing this is through the Atem SDK. However there are many open source efforts to document and implement the protocol, such as the work by Skaarhoj - https://www.skaarhoj.com/fileadmin/BMDPROTOCOL.html - (although their open source stuff doesn't cover the version 8 software used by the Atem Mini). It's not an easy protocol to implement and relies on a load of binary data and specific timing.

@adebeau: I am looking for some similar solution for my Mini Iso Pro. Have you made any progress?

Perhaps I misunderstand your question/problem, but there's a couple of videos that BM put up on youtube that describe how this protocol works. It's not specific to the Mini devices, but I successfully built a device that gives me push-buttons to switch channels, and also gives me "tally" lights so I know the current channel using TCP/IP control based of what I learned here.

This is one of them that describes the overall structure of the text protocols they use (and one of the specific protocols)

this one describes the router protocol (this is the one I was able to use to make my switcher/tally lights)

I'm guessing, but I suspect there might be more videos, though I've not looked hard, since the router one had what I needed. There's definitely one on port 9977 that can be used to determine if the device is recording or streaming, and has some other stuff, but I've not been able to turn recording on using it.

I believe (and this might be the basis of your problem) that there are other ports with other protocols on them, but it seems that the whole "send a message that looks like the report" concept seems pretty repeatable. Certainly the basic router protocol was pretty handy and works easily, though I don't know what you want to do with it, so I can't say if it has all of what you need or not.

HTH
Toby.

@Toby, The router and Hyperdeck protocols are open and i believe telnet.
The Atem protocol that the topic starter is looking for is a Company Secret!! Skaarhoj did some fine reverse engineering for that protocol but since the change in the protocol after FW7.5.2 they do not update and support it anymore.

So basically there is no DIRECT way of connecting to the Atem. Just use the SDK for the Atem which will have a pre-build component to run the comms to the Atem...

The Atem protocol that the topic starter is looking for is a Company Secret!!

As indicated, I did wonder if I misunderstood. So, at the risk of hijacking a thread, what actions/information does this secret protocol support? I've been using the protocols I linked to and they've supported the interactions I have been interested in so far, but having the device network accessible is powerful, and maybe you can spark my imagination with more ideas for stuff to try?

I have make some network analysis and discover that 2 ports are open on the ATEM Mini.
TCP 9977 :
And port 9910 UDP.

TCP9977 is used by ATEM Setup, and UDP9910 by ATEM Software.

[...]
My goal is to send datagram to change preview, source, etc ...

Many thanks,

At the risk of being wrong again, OP asks to set the source and preview. That you absolutely *can* do with the router protocol--I'm doing it. Also, OP says two ports are open, but at least two more are open;

9993 (TCP) which signs on and responds to a "help" command by listing other commands it accepts.
9990 (TCP) which is the routing connection, which certainly allows the change of preview and source that' OP requests.

EDIT: a thought occurs, if you try to use these text-based protocols on 9993 and 9990, they dont' work well with telnet on Linux at least, (something about the line ending, I suspect). They work just fine using nc, and they work just fine with network sockets opened in Java or C.)

Unbelievable but true.
Just connected using Putty to one of my ATEM's using port 9990
After more than 5 years deep in the ATEM API and documentation I have never seen mention of support for the router protocol in the ATEM's.

This would be awesome for ATEM's that have AUX output so you can use them like a video hub, especially the Constellation. I suspect the Video hub remote panels would also work to control the Constellation!

Nowhere near the control you get with the API but simple for switching only.

Here is the output from my Atem Mini
PROTOCOL PREAMBLE:
Version: 2.7
VIDEOHUB DEVICE:
Device present: true
Model name: ATEM Mini
Friendly name: ATEM Mini
Unique ID: 312306a5d55f4347a66348424a648c24
Video inputs: 13
Video outputs: 3

INPUT LABELS:
0 Black
1 Camera 1
2 Camera 2
3 Camera 3
4 Camera 4
5 Color Bars
6 Color 1
7 Color 2
8 Media Player 1
9 Media Player 1 Key
10 Program
11 Preview
12 Camera 1 Direct

VIDEO INPUT STATUS:
0 Internal
1 HDMI
2 HDMI
3 HDMI
4 HDMI
5 Internal
6 Internal
7 Internal
8 Internal
9 Internal
10 Internal
11 Internal
12 HDMI

OUTPUT LABELS:
0 Output
1 Program
2 Preview

CONFIGURATION:
Video Mode: 1080p30

VIDEO OUTPUT ROUTING:
0 10
1 2
2 2
END PRELUDE:

This is indeed whole new info.. Up till now / weeks / months ago Atems would not connect or respond to telnet / videohub protocol.

This is a great find!! We tried this on our 4ME Broadcast. But doesnt work. So it seams only implemented on the latest FW build for Constellation and Atem Minis..

Fingers crossed the older atems get this option too...

Atem FW 8.6
After announcement yesterday about the new Atem Mini Pro Extreme series with the full routing options also for the DVE, Wipes etc.

Just tested this on my Atem Mini Pro. With the newest FW 8.6 but there is just 3 Outpoints like the previous fw. So turns out that feature is only available on the new Extreme models for now..
#waiting for new update.,. Fingers Crossed

Atem FW8.6.png (153.96 KiB) Viewed 33305 times

[Gary Adams]

Hello Everyone. Currently only the ATEM Mini switchers (Mini, Pro, ISO, Extreme and Extreme ISO) support the Videohub telnet protocol for switching Program, Preview and the Output buses. When logged into the ATEM, there is a dump of supported I/O. Help will list supported commands. Any other switching would be under consideration for the future but there are no promises or guarantees. ATEM Mini models that support recording to external disk also have ftp capability in case anyone didn't know about that. I hope this helps. Stay safe.

Regards, Gary

...ATEM Mini models that support recording to external disk also have ftp capability in case anyone didn't know about that.

That is useful, yes!

It would be wonderful if BMD put out an official Arduino library for the same functions as the SDK, or at least a subset of the most important ones. The routing protocol is handy for basic switching, but it isn't really suitable for controlling things like the mixing function (for something like a stand-alone T-bar controller) or even some of the other adjustments that would be better suited to rotary controls (DVE positions, key levels, etc.)

It would be wonderful if BMD put out an official Arduino library for the same functions as the SDK, or at least a subset of the most important ones. The routing protocol is handy for basic switching, but it isn't really suitable for controlling things like the mixing function (for something like a stand-alone T-bar controller) or even some of the other adjustments that would be better suited to rotary controls (DVE positions, key levels, etc.)

The Atem control protocol is officially proprietary protocol and wont be released!!

Skaarhoj has done a great job fully reverse engineering the protocol up to 7.5 and made it public including Arduino libraries.

But they stopped supporting it as freeware and if you want anything to go over FW7.5 you have to buy there hardware.

The Atem control protocol is officially proprietary protocol and wont be released!!

Exactly. That's what I hope would change. BMD has other efforts that assist DIY'ers, so it seems odd to leave a hole here.

I'm thinking specifically about the ATEM Mini products. They're pretty capable button-wise, so there's no need to duplicate everything. So, when someone like me just wants is an extra lever or dial -- some form of analog input -- Skaarhoj and M/E panels are economic overkill. They're accessories that cost 2X - 10X (or even higher) than the device they're controlling.

If BMD was worried about cannibalizing M/E panel sales, they wouldn't even publish an ATEM SDK for Windows and macOS. But I do understand the need sometimes to keep a low-level protocol private. Perhaps, instead, another Arduino shield with locked-down firmware that acts like an I/O version of an SDK. One could send simple serial commands from the Arduino to the shield which then translates them into the UDP commands.

Just some food for thought.

Arduino is already a platform that has a high level of users that have no idea what they are doing..

We have seen this with the Arduino SDI shield people asking if someone can create the code for them.. As they have no clue how to..

Releasing a timing sensitive protocol that has the power to crash an atem if used wrong. ( Let a skaarhoj 7,5 FW arduino code connect to an Atem with FW 8 and you know what i mean )

The support on such a library would be so high for the support team due to people not knowing what they are doing.. A Simple delay(10); could already mess up the full control of the Atem core.. Something that doesnt happen in a multitreading enviorement like the PC SDK's.

So no i dont see this happening anytime soon.. Unless BMD decideds to have a Simple protocol opened up next to the full protocol... But that means stepping out of UDP traffic with timers and keys to keep sync between devices.

So basically the Telnet router protocol is the next best thing you will ever get. Just a shame it isnt implemented on the older Atems..

@Toby, Sorry to disturb, I saw the interesting posts here, but I am a bit stuck in the search to the text commands over telnet.

Can you point me in a direction?
As background i would like to make a Tally Light in a ESP8266 or ESP32 board.

Any thoughts on how we could escalate this within BMD? I'd love to see an open protocol here. BMD would benefit from the innovation as well.

I have make some network analysis and discover that 2 ports are open on the ATEM Mini.
TCP 9977 :
And port 9910 UDP.

TCP9977 is used by ATEM Setup, and UDP9910 by ATEM Software.

[...]
My goal is to send datagram to change preview, source, etc ...

Many thanks,

At the risk of being wrong again, OP asks to set the source and preview. That you absolutely *can* do with the router protocol--I'm doing it. Also, OP says two ports are open, but at least two more are open;

9993 (TCP) which signs on and responds to a "help" command by listing other commands it accepts.
9990 (TCP) which is the routing connection, which certainly allows the change of preview and source that' OP requests.

EDIT: a thought occurs, if you try to use these text-based protocols on 9993 and 9990, they dont' work well with telnet on Linux at least, (something about the line ending, I suspect). They work just fine using nc, and they work just fine with network sockets opened in Java or C.)

@Toby, Sorry to disturb, I saw the interesting posts here, but I am a bit stuck in the search to the text commands over telnet.

Can you point me in a direction?
As background i would like to make a Tally Light in a ESP8266 or ESP32 board.

@Toby, Sorry to disturb, I saw the interesting posts here, but I am a bit stuck in the search to the text commands over telnet.

Can you point me in a direction?
As background i would like to make a Tally Light in a ESP8266 or ESP32 board.

Hit google and hit Search on Atem Tally ESP32. It is out there and it's easy like pushing it to the controller and there you go.. Why re-invent the wheel???

Just for reference...

# nmap -v 192.168.1.102
Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-10-21 15:11 PDT
Initiating ARP Ping Scan at 15:11
Scanning 192.168.1.102 [1 port]
Completed ARP Ping Scan at 15:11, 0.39s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 15:11
Completed Parallel DNS resolution of 1 host. at 15:11, 0.00s elapsed
Initiating SYN Stealth Scan at 15:11
Scanning atem-extreme-iso-hdmi.dachshund-digital.org (192.168.1.102) [1000 ports]
Discovered open port 80/tcp on 192.168.1.102
Discovered open port 21/tcp on 192.168.1.102
Discovered open port 445/tcp on 192.168.1.102
Increasing send delay for 192.168.1.102 from 0 to 5 due to max_successful_tryno increase to 4
Increasing send delay for 192.168.1.102 from 5 to 10 due to 11 out of 11 dropped probes since last increase.
Discovered open port 5357/tcp on 192.168.1.102
Completed SYN Stealth Scan at 15:11, 12.18s elapsed (1000 total ports)
Nmap scan report for atem-extreme-iso-hdmi.dachshund-digital.org (192.168.1.102)
Host is up (0.00031s latency).
Not shown: 996 closed tcp ports (reset)
PORT STATE SERVICE
21/tcp open ftp
80/tcp open http
445/tcp open microsoft-ds
5357/tcp open wsdapi
MAC Address: [Redacted] (Blackmagic Design)

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 12.82 seconds
Raw packets sent: 1107 (48.692KB) | Rcvd: 1001 (40.044KB)

Scan against ATEM Extreme ISO (HD Variant not SDI) with if I recall right control software 9.6.2? Whatever the latest is as of this post. So firmware is 9.5.1.

I have been using PyATEMMAX and PyATEMAPI (see via github) python modules to connect and control said switcher just fine. And as far as I know PyATEMMAX is based at least in part, on the reverse engineering noted above.

BTW... 9993 and 9990 respond to TCP direct query still as noted above...

# nc 192.168.1.102 9993
500 connection info:
protocol version: 1.0
model: ATEM Mini Extreme ISO
friendly name: ATEM Mini Extreme ISO
unique id: [Redacted]

# nc 192.168.1.102 9990
PROTOCOL PREAMBLE:
Version: 2.7

VIDEOHUB DEVICE:
Device present: true
Model name: ATEM Mini Extreme ISO
Friendly name: ATEM Mini Extreme ISO
Unique ID: [Redacted]
Video inputs: 23
Video outputs: 5

INPUT LABELS:
0 Black
1 Camera 1
2 Camera 2
3 Camera 3
4 Camera 4
5 Camera 5
6 Camera 6
7 Camera 7
8 Camera 8
9 Color Bars
10 Color 1
11 Color 2
12 Media Player 1
13 Media Player 1 Key
14 Media Player 2
15 Media Player 2 Key
16 SuperSource
17 Clean Feed
18 Multi View
19 Program
20 Preview
21 Camera 1 Direct
22 Camera 2 Direct

VIDEO INPUT STATUS:
0 Internal
1 HDMI
2 HDMI
3 HDMI
4 HDMI
5 HDMI
6 HDMI
7 HDMI
8 HDMI
9 Internal
10 Internal
11 Internal
12 Internal
13 Internal
14 Internal
15 Internal
16 Internal
17 Internal
18 Internal
19 Internal
20 Internal
21 HDMI
22 HDMI

OUTPUT LABELS:
0 Output 1
1 Output 2
2 Webcam Out
3 Program
4 Preview

CONFIGURATION:
Video Mode: 1080p59.94

VIDEO OUTPUT ROUTING:
0 18
1 18
2 19
3 5
4 3

VIDEO OUTPUT LOCKS:
0 U
1 U
2 U
3 U
4 U

END PRELUDE:

This is an interesting thread.
Long Story Short : I am an infrequent user of my ATEM Mini Pro, and very recently created a few Lower Third Graphics - but the Down Stream Keyer cannot be activated on the switcher - I must also have the Control Software running on my Laptop

I do also develop hardware and software based on Arduino Microcontrollers ( which augments control of my Amateur Radio Equipment ) and recently adopted the use of a WiFI capable uC in my new prototype controller.
Lightbulb moment ! Perhaps I could create a simple device to issue a UDP packet ( after the press of a button ) to turn on or off the DSK ?