Coming Soon: The New & Improved TokBox Account Interface

tokbox-inc_markSince we launched the new version of our platform back in 2012, one of our goals has always been to make it very easy to manage and understand how your applications are performing. In addition to simplifying how to build applications, we believe that those are the key elements for a great experience.

Over the last year we have been working on a completely new way to interact with your TokBox account. As our user-base grew and diversified, it was obvious that our previous dashboard was not enough and needed to be extended. With the number of new tools and services that are in the works, we realized that it was a good opportunity to future proof our stack and give you, our users, a much better experience.

0 Comments Read More

Introducing the One-to-One Sample App

tokbox-inc_markWe’re excited to announce the release of the OpenTok One-to-One Sample Application across web, iOS and Android.  This open-source application enables you to speed up your development efforts to set up interoperable, production-quality audio/video communication between users.

As you get started with this OpenTok sample, you will learn the best practices used to develop and manage the audio, video, and camera elements on mobile devices or in the browser. We recommend this is as your first step in delivering Real Time Communications (WebRTC) solutions on the OpenTok platform.

1 Comment Read More

Lip-sync Issues: When a Chrome Update Fixes your Application

This post was co-authored by Gustavo Garcia Bernardo, Philipp Hancke and Charley Robinson.

chrome logo

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.

0 Comments Read More

How to get a WebRTC Diagnostic Recording from Chrome 49+

WebRTC logoHave you ever had to support a WebRTC application and needed to get packet dumps from the user? Wireshark is a great tool for this, but asking a user to install it and make a dump rarely works. It’s just too complicated. So I was pretty excited when I read the Chrome 49 release notes which described (not in much detail) a new feature called the ‘RTC event log’. This is described as follows:

We now provide a new debug option in chrome://webrtc-internals for tracing internal details (e.g., BWE, jitter buffer state) for audio and video sessions. This option creates a log containing the timing and headers of packets as well as the timing of various internal events. We hope this will help resolve issues related to media transport and jitter buffers; attaching this log when reporting such issues will help us tremendously.

0 Comments Read More

TokBox at the Largest Hackathon in History

kodinghackathonThe Event

Set to be the largest hackathon in history , TokBox is proud to be sponsoring the Koding & Hacksummit hackathon, February 20-21.  More than 25,000 teams will participate in the hackathon for a chance to win some amazing prizes.

The Challenges

Participants can use any publicly available API to create something that fits into the theme of data visualization, productivity or gaming.

0 Comments Read More