Blackmagic SRT
#1641
Replies: 1 comment 3 replies
-
Does this work for you? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Blackmagic has updated their entire ATEM switcher line, now with SRT.
The SRT settings in the documentation do work, but there are two issues:
With the new update, all Blackmagic switchers have an interface for SRT that lets you put in a 'Server' and 'Key' value, without the requirement of creating a definition in the streaming settings XML. But how are these values sent to OME? Here is what I discovered.
In this example, we are setting the server with the 'key' being our intended stream ID of abc123:
![image](https://private-user-images.githubusercontent.com/33604674/338636671-8009d449-880c-4bef-9c29-d3238ba1be7a.jpeg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzMxMDIsIm5iZiI6MTczOTI3MjgwMiwicGF0aCI6Ii8zMzYwNDY3NC8zMzg2MzY2NzEtODAwOWQ0NDktODgwYy00YmVmLTljMjktZDMyMzhiYTFiZTdhLmpwZWc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMVQxMTIwMDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iY2M5MTBlMGVhOGU3OTIzMDgwZWNjMjQxY2NlZmY4MjExYjg0NTlkZmRkNzAzYTMzNDIzMmU0MzgxYzMyYWI4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.qncro6iIuSbrRJ7-YnHWdx9SdnmfpEzNEAYLQFtA14s)
On the OME side, we receive this string of arguments to the SRT Provider:
#!::u=abc123,bmd_uuid=b0d6667f-ef5e-47a8-88c3-125af516ebae,bmd_name=ATEM Mini Pro
This is actually a common method of providing SRT parameters, using #!:: followed by a comma separated list. So in OME all we need is the ability to parse the ID out of this string... A regex like this could cover it:
I tried to do this in my control server but unfortunately it is the SRT Provider that first receives the request and it does not get sent to the control server. Here is what the SRT Provider gets:
To my friends at Airensoft, would you consider working to add support for this other format of sending the stream ID? I think this might also solve the SignedPolicy issue. The ATEM series is one of the most popular streaming encoders on earth. It works great with RTMP already including SignedPolicy, and equally robust SRT support is very close.
As always, I have a stack of hardware here so happy to send tests or try different params as needed to assist with this.
Beta Was this translation helpful? Give feedback.
All reactions