Millicast has been using #WebRTC for large scale streaming for many years now. There is a request that comes back very often: “Can I add latency and keep the quality of the media as high as possible?”. To answer that question, one need to look at the concept of reliability, and how it varies depending on the protocol of choice.Continue reading
It’s Xmas! Or, depending on your time zone, it’s about to be Christmas. It’s the season to be jolly, and CoSMo would like to bring you a few gifts.
While we have been hard at work in the background to make sure #Webrtc gets better (some overview of that here), we have put a lot of effort in the last year into remote collaboration workflows for content production and post production.
Which is why we are releasing multiple products and services in time for Christmas, bringing Broadcast Quality to Real-Time streaming across devices.Continue reading
Thanks to a collaborative work between Millicast and Teradek engineering teams, Teradek products have now best in class support of the MilliCast.com platform. This shows the dedication of Teradek to position themselves as the best provider for live and real-time encoders, and MilliCast to extend their support of capture devices and Hardware encoders.Continue reading
From the broadcasting industry perspective, WebRTC is not “complete”. It can’t be implemented once and forgotten, like many other protocols before. It lacks a standard signalling protocol to go along. From the web industry perspective, it’s a wanted feature, and it did allow the protocol to be used for vastly different use cases than originally anticipated or designed for. That situation has been frozen in place for many years, as neither the web community (we have what we want), nor the broadcasting community (who needs realtime anyway, VOD will rule forever), seem to be interested in jumping in and filling the gap. Until COVID-19 that is ….Continue reading
I’m a little bit late on this one, but in May 2019 Microsoft had its “Build” event, and disclosed the new iteration of their windows native webrtc Library. This is the third iteration, and it s remarkable in many ways, especially for Gaming and Hardware Acceleration, so let’s dig into the history and current support of libwebrtc on windows, backed by Microsoft!Continue reading
CoSMo provided the H264 simulcast implementation to chrome and safari (based on earlier patch by highfive, kudos to them). We helped Intel and Apple work together to put H265 in libwebrtc. AOMedia members, we also were among the first to have a realtime implementation of AV1 in libwebrtc, and have been regularly speaking publicly at different conferences about it. Today, some of this work is becoming available in consumer versions of the browser. Let us give you through enabling it, and taking it out for a ride.Continue reading
Around came up with a big dream: being able to have a meeting in a room where other people would have a meeting, without earpiece, and without echo! Surfing the Work From Home wave, they came out of stealth mode a few weeks back, but they had been at work for months with a team of very gifted engineers and WebRTC experts alike.Continue reading
With COVID-19 out there, people have to reinvent the way they live and the way they work, remotely from the office but also remotely from each other. Webrtc technology being rooted in conferencing and collaboration, those topic understandingly take the front line.
However, this is not the only space being disrupted by WebRTC.
For a certain time, webrtc has been pushing the boundaries of can be done in real-time streaming, and the pandemic is only accelerating this. This blog post is a follow-up of previous posts and show the evolution of the situation, and how the pandemic is actually creating new use cases and transforming the streaming market.
While scalability is often the first excuse some use not to use WebRTC, a persistent claim even though that myth has been debunked long ago and many time over since, “quality” is certainly the second one. Webrtc cannot do <put a resolution here>, it’s just good enough for webcams, it cannot use more than 2.5 Mbps, ….. . While all of those previous claims are false, there is one that was correct: the default audio codecs in webrtc implementations, and especially in browsers, are not as good when it comes to spatial info than their streaming or gaming counterparts… untill recently!
This is really a great week with so many of the projects cosmo has been working on or helping for the past years coming out almost at the same time. During last IETF Hackathon, at the webrtc table, and then at cosmo offices in Singapore, INTEL and Apple came together to add HEVC support in webrtc.
INTEL chips have been supporting Encoding and Decoding for some time now. They support it in non-GPU hardware, making it a big deal for devices that can’t afford full discrete GPU. Most Apple devices integrate those INTEL chip, so having support in WebRTC for H265 HW acceleration was de facto enabling H265 in all of Apple devices in one shot (without legal issues). Of course, the more support there is for INTEL features in media stacks above, the more hardware they sell. Win-Win
INTEL (webrtc group in Shanghai) had an implementation for Desktop, android and iOS. CoSMo acted as a catalyst between the two teams, and the two language/culture (chinese and french :-)).
This blog is about the tech details of H265 in particular, and Hardware Accelerated Codecs implementation in libwebrtc in particular.
Updated on april, 7th, to add info about GPU acceleration support, in addition to INTEL CPU HA acceleration support.
(*) CPU Hardware acceleration means the CPU has dedicated silicon circuit to implement the function, as opposed to running a software implementation in the generic x86 CPU. Even though both use the CPU, the former is much faster.