This post was co-authored by Gustavo Garcia Bernardo, Philipp Hancke and Charley Robinson.
When WebRTC stuff is really broken, it gets fixed very quickly.
Early in December 2015, shortly after the release of Chrome 47 to the general public, we started to notice a subtle and strange behavior in the Audio/Video of streams during our many daily meetings using WebRTC: the video occasionally wouldn’t stay caught up with the corresponding audio. As with many bugs noticed internally by developers, it took a while for any of us to believe that what we were seeing was a real issue. We call this the inverse of productive dogfooding: rather than assume we are just like our users, we can just as easily decide we are nothing like them.
The evolution of live video has spawned new and engaging ways for brands, organizations and people to connect with their audience. Whether it’s participating in a team meeting held remotely, hosting a virtual conference for hundreds of people all over the world, demo-ing a new product to customers via a webinar, or broadcasting a live stream of an event, there is no question live video is now becoming a standard feature in any business or entrepreneur’s communication toolkit.
Early December saw the roll-out of Chrome 47. When doing anything with WebRTC, this is always an interesting time. A release brings new features or may break things, like removing the getUserMedia functionality for insecure origins.
Our metrics clearly track such roll outs as seen below:
Embedded communications is so powerful because of one very important factor – context. Whether that’s a web page, presentation, LMS, medical scan, (the list goes on), context enhances the conversation. Better still? When collaboration features are layered on top.
Using the OpenTok platform, our aim is to make it super simple for you to add rich collaboration functionality to your apps. Today we’re happy to introduce the Annotation widget for the OpenTok platform in beta – a pre-built UI component that can be quickly added to your application. The widget adds annotation and frame grab capabilities to the OpenTok web, iOS and Android SDKs and is completely customizable.
Today we’re thrilled to announce the launch of our powerful new session diagnostic tool, Inspector. It provides you with a high-level OpenTok session summary at a stream and user level to help pinpoint errors, failures, and quality issues. Our main goal? To simplify your post-session debugging.
Inspector takes the rich and complex operational data that the TokBox engineering team uses to debug OpenTok sessions, and makes it available to you in an easy to use interface. These vital metrics will enable you to drill down into session-level details around:
- Bit-rate, latency and packet loss graphs at user and stream level
- Event Logs (Detailed list and description of all session events)
- User Logs (Information such as location, SDK, browser and client)
- Error Logs (Details of all errors encountered, time of error and impacted end-users)
Now your technical support team can quickly glance through session data to determine whether an issue was caused by an end-user error, application error, network problem or the OpenTok platform.