Last week, we released OpenTok v2.15, the latest version of our Client SDKs. We wanted to update you on some of the great new features included and how you can use them.
Audio Enhancements in Web and Windows SDKs
In opentok.js 2.14 we added the ability to switch cameras using the Publisher cycleVideo() method which was really well received. Version 2.15.0 of opentok.js and our Windows SDK add the ability to switch to a different audio source. In opentok.js you do with using the Publisher setAudioSource() method and in Windows you use the AudioDevice.SetInputAudioDevice method. The obvious use-case for this API is to allow your users to switch microphones without needing to create a whole new publisher. But it can also be used to switch to other supported audio sources, for example loading audio from an audio file, or creating custom audio. In opentok.js you do this using the setAudioSource() method and passing a custom audioTrack. In the Windows SDK you do this using the AudioDevice.setCustomAudioDevice method and passing a custom audio driver.
In an effort to make our APIs more accessible and easy to use, we’ve spent some time improving all six of our server SDKs. The OpenTok Server SDKs provide a convenient way to to interact with the OpenTok REST API in a variety of languages. Please note that these enhancements will not break your implementation should you choose to upgrade.
In this blog we look at how to connect OpenTok Live Video sessions with traditional PSTN phone calls. We will demonstrate how to connect an OpenTok session to PSTN with an audio stream that connects through OpenTok SIP Interconnect to a Nexmo SIP-PSTN Gateway.
OpenTok SIP Interconnect is a general purpose SIP capability that can be used to connect to many different kinds of gateway or other SIP systems. TokBox is now part of Vonage, so in this blog we will use our own Nexmo programmable communications APIs to bridge the call.
In April, we announced updates to our pricing and packaging, which allows TokBox customers to have more flexibility with the ability to add-on features a la carte to their accounts. With this in mind, we’ve been hard at work over the past couple of months to make our entire user experience more flexible and allow users to have more control in configuring their OpenTok projects.
Today, we’re excited to announce that we’ve made several improvements to the Account Dashboard, which provides users with more self-service functionality. These updates will make it faster for users to configure their OpenTok projects and make quick changes, and to gather critical information on the add-ons they have access to.
[UPDATED July 31] We’d like to welcome all WebRTC and TokBox API developers, wherever you are in the world, to our TokBox Live Video and AR Online Hackathon! How would you like the chance of winning a $600 prize for each of two top teams – plus OpenTok Developer credits and two second place prizes bringing total prize value to $2520. It’s up for grabs for the teams which create the best OpenTok Live Video apps of any kind, with a special prize for combining Augmented Reality and Live Video. Read on to find out how to get involved. Your app will be developed in your own time during August/September 2018 in teams of 1 to 3 people – with your app submitted online at DevPost by September 18th.
[UPDATED September 6] As you may know, Google recently announced the deprecation of inline installation of Chrome extensions in an effort to improve transparency and security. For end-users, this means that the process for installing screen sharing extensions will change from inline installation to installation from the Chrome Web Store. Below, you’ll find information on the deprecation timeline provided by the Chromium team:
Diving into data on OpenTok sessions can provide developers with the tools they need to understand bugs and make improvements quickly. That’s why we built Inspector – a tool to help developers understand what happened in specific OpenTok sessions. Users can either enter a session ID or use the Session Dashboard to access the information. This includes user data, errors, video and audio quality and events about a session.
If you had to choose one memorable thing about the upcoming iOS 12 when it was unveiled at WWDC’18, it would probably be the inclusion of ARKit 2.0, Apple’s Augmented Reality toolkit for iOS. I bet you still remember that cool demo by the Lego guys playing on the stage.
In fact, ARKit is probably the component which is going to grow the most in the new version of iOS, with many new features, improvements and even a new app to easily perform real-world measurements.
Recently, my colleagues and I were in Las Vegas sponsoring HackHLTH at the inaugural HLTH conference on the future of healthcare The hackathon was geared towards building health tech solutions that would improve the health industry and create a more robust ecosystem. In little more than 24 hours there were over 80 projects from over 250 participants.
Many of those projects took advantage of the OpenTok platform to include live video in their apps. It’s a testament to the great work of the TokBox engineering team that it’s so quick and easy to get live video up and running. I was proud to see teams build such a variety of solutions in such a short space of time.
Today, we’re excited to bring support for 720p HD to our Recording and Live Streaming features. With this release, our APIs will provide developers an option to record OpenTok and live stream OpenTok sessions in high definition, and as a result create more engaging live video experiences.
Live video sessions on OpenTok already support 720p, but until today, customers could only record and live stream at 480p. With a growing number of education, webinar and media and entertainment customers, demand to support HD resolution for recording and live streaming has been gaining momentum and we are pleased to finally make this available for our customers.