Microsoft Teams has built and delivered solutions to enrich virtual experience across the spectrum of communication needs, from 1:1 meetings and calls, to webinars and broadcasts. Last year we introd...
Updated Jul 21, 2021
Version 1.0
Blog Post
In layman's terms, with this solution, assuming I am using OBS studio... is my understanding correct.
Essentially we setup a VM in Azure, that will have OBS studio installed (or vMIx, or some other production software).
When a teams meeting starts, I assume the bot joins the call as a participant, and as noted converts the different streams into SRT streams. I assume this a parallel to NDI (same concept)... that each stream in the teams meeting is then exposed.
The bot allows the SRT streams from that teams call to be captured by your VM in Azure.
In a use case for training with a host (in LA) and two remote experts (in Pittsburgh and Orlando), all three might join a teams call with their video on, and each would have a SRT video stream that is captured and sent to the production software.
The production software would be set to ingest those three streams as sources. With OBS, it looks like the software wants a URL to ingest a SRT stream.
A fourth participant, the producer might create different layouts from the VPC in Azure, where all three experts are together, or separate layouts, and output the composted signal from the production software (OBS or other), via the BOT to the teams meeting (as a participant).
The bot can be spotlighted, so that is what everyone else who joins the same teams meeting sees.
Through the call, the remote producer could be changing the scenes as the different experts and moderators and talking/presenting.
The remote callers/presenters audio/video feeds are all going up to the Azure cloud, and the solution for the remote producer would be low latency because it is being done on a central VPC, and fed back into teams at the source, and broadcast back down to the remote endpoints (teams connections).
The remote producer would have their production studio running on the remote VPC (in Azure), regardless of where the producer was located, the production is happening at the best possible location in the Azure cloud.
Am I understanding this correctly?