* Honestly, I would not even call MS Teams a video conference application - it's a messaging app like Slack. Obviously, it's very disruptive for all viewers and wrongly makes it look as if the presenter (that's us) is at fault. Adding insult to injury, we also experienced at least 3 connection drops, due to the presenter (our encoder) being blocked (either muted or removed) by someone in attendance during the meeting! This is a known issue in Teams, but it cannot happen in a proper webcast. MS Teams reports are only available while the meeting is in progress and unlike YouTube, they do not provide information about the bit rates or screen resolutions delivered to viewers.ħ. The client claimed that a post-event survey indicated only 20% had clear video. But the anecdotal reports and screenshots coming in from viewers complained about blocky and blurry video for some users, many of whom seemed to be viewing on mobile devices.Ħ. We had continuous monitoring on two laptops and one mobile device and all looked good on our end. There are multiple reports online that MS Teams is limiting video quality for larger meetings, due to popularity of the service during the Covid-19 pandemic. If you need a meeting for more than 300 people, use a live event." Yeah, we were warned!ĥ. According to Microsoft: "Live events are an extension of Teams meetings that enable you to schedule and produce events that stream to large online audiences - up to 10,000 people. Simply put, a live meeting is a webcast with chat facilities. Keep in mind that feeding switched video into an MS Teams meeting is not what Microsoft calls a "live meeting".
So with Teams you're basically hoping they don't throttle your stream.Ĥ. And there is no fail-over redundancy provision like what you'd have in YouTube. This is different from say YouTube, where you have some control of the transmission quality. When sending switched video into MS Teams, there are no encoding settings. I'm still not sure that this isn't a Wirecast issue, but it frustrated me during setup, especially playing prerecorded video intros or roll-ins, and we did not have good control over levels.ģ. To hear what we were sending, we had to open a separate window and run Audacity, which was extremely clumsy. It was not possible to hear the encoded output when using the virtual mic to feed into MS Teams. Big hassle and I never experienced this issue using Zoom.Ģ.
#Streaming with wirecast software
The most recent version of MS Teams apparently does not support virtual camera, so we had to roll back to an earlier version and then (since we were testing over several days) prevent the software from auto-updating. Our internet connection was dope - 100 mbps up and down.ġ. The virtual camera and microphone were fed into MS Teams 1.5.
#Streaming with wirecast pro
We are running on Win 7 Pro with i7 CPU and Magewell SDI capture cards. Our setup is Wirecast 13.0.1 which is almost the latest version (but sadly is now unsupported). Bottom line is, if you have an audience larger than 200 viewers, use a proper webcast CDN, not a videoconference application*. We're writing this recap so no one should experience the same. The result was thoroughly unsatisfactory for the audience and client.
#Streaming with wirecast 720p
We recently produced a live stream encoded at 720p for an awards ceremony which was relayed to an audience of about 300 persons via MS Teams.
0 kommentar(er)
