In their latest blog post, Wowza is doing a great job at explaining in simple words latency, and the use cases that could benefit for having under 500ms, a.k.a. “real-time”, latency. However, the section about streaming protocol is somehow confusing me. This blog post is an attempt to put those protocols back into perspective to have a fair comparison.
Which codec, and which flavours of codecs are supported by which browsers. This is a tricky question for every product manager that wants to define product expectations and roadmap. Should I support only VP8 / H264 ? Should I wait for VP9? What is multi-stream, simulcast, and SVC versions of those codecs? Beyond all those questions really is: when can I tell my customers I support Desktops browsers, Android, iOS? If I can’t should I have a native app instead. This blog post aims at putting everything back in perspective.
I used to be very entertained by stories given by different webrtc consultants. The “Cat roulette” example by L. Barr last year during a conference in Miami was exhilarating. I was thinking: those guys have all the fun!
What people don’t tell you when you go into that business is the wide variety of clients you end-up facing. Now that I am on the other side of the fence, the grass is not exactly greener. In an effort to give people a glance of how hard it can be sometimes, and to keep my mental sanity by letting it out, I’m writing a post about the horror stories we’ve faced so far, or, to put it in amore diplomatic way: about the inherent bias clients can have about our perceived value, or WebRTC perceived value.
CoSMo and Meetecho have been working together for some time as the #webrtc A-Team. So far the contributions described in different blog posts have mainly been on the server-side, with Double-Encryption, VP9 SVC, or more recently better bandwidth management support. This time, we are going to speak about several client software options to connect to Janus Instances that have been just been made available.
Security in Real-Time Comms.
Security is important for communication, and in the wake of XXXX (pick your favorite) revelations, the IETF RTCWEB working group and other standard committees alike had decided to up their game. With respect to webrtc, that’s for example when the decision was made to mandate the more secure DTLS-SRTP over SDES-SRTP. The entire Security architecture is documented within a corresponding documents and some dependencies:
Encryption is only really useful if it is end-to-end and if you are sure who you are talking to.
Main Coders and Architects: Sergio Murillo, Lorenzo Miniero,
Facilitator, Motivator, and Secretary: Dr Alex Gouaillard.
Janus Bandwidth management has been incrementally updated to support the latest technologies available in a joint effort between CoSMo and Meetecho, a.k.a. The WebRTC A-Team. This article describes the original design of Janus and its VideoRoom plugin with respect to bandwidth management, and the incremental changes that were needed to bring it to automatic bandwidth estimation and adaptation on the sender side, and availability of simulcast for bandwidth management on the receiver side. A concrete example about how to leverage simulcast with the Janus VideoRoom Plugin is provided for illustration and testing purposes.
One week ago, KITE daily runs results were made available on webrtc.org. This signs the end of a first phase, and shows that webrtc automated testing in desktop and mobile browsers is doable today. This blog post reflects on the path taken to get here, the ongoing maturation of webrtc implementations, and KITE as tool for the RTC industry to achieve End-to-End testing, as well as load testing, and benchmarking.
We had started the cosmo adventure in a co-working space. It was great: we were surrounded by entrepreneur-minded people, supported by great staff (kudos Claire and Evelyn), the space was nice, the roof top incredible, and it accommodated our growth from 1 to 13 local employees in 2017. If you’re looking for a centrally located co-working space in Singapore, I could not recommend any place more than WOTSO co-working space at 19 Cecil Street. The hard truth was that we had outgrown our co-working space.
Ever since I designed and wrote with an intern the infamous IE/Safari plugin, I had pledged to make it obsolete and redundant. Unfortunately, that had never happened. Until today that is. Come and check what this new free ($, beer) and free open-source (freedom) plugin brings you.
While intense discussions happen on the W3C Webrtc mailing list (someone asked everybody what they want to see in Webrtc NV ….), it’s nice to take a step back and look at the first results of KITE, a new end-to-end testing tool designed to make Webrtc 1.0 and all applications using it better.