Today we are releasing the OpenTok iOS SDK v2.1.7 that includes:
- This version fixes peer-to-peer publishing and subscribing issues between iOS and Chrome.
- This version fixes memory leaks in OpenGL rendering.
- This version fixes issues when disconnecting from a session.
Learn more about our iOS SDK >
This update will be available to developers starting today.
With last week’s WebRTC Conference and Expo in Santa Clara, California coming to a successful conclusion, the second big WebRTC event of the year is now behind us. Sure, there are other WebRTC-related conferences – the IIT RTC conference in Chicago, the WebRTC Summit at Cloud Expo, next month’s WebRTC 2013 conference in Paris - but with what looked like 700 people in attendance, the twice-annual WebRTC Conference and Expo is the big one.
- Archiving—You can record audio-video streams in a session and download the recording as an MP4 file (with H.264 video and AAC audio).
- Dynamic frame rate control—This feature lets you reduce bandwidth usage of a Subscriber’s video stream. This reduces CPU usage and the network bandwidth consumed, and it lets you subscribe to more streams simultaneously.
These are just a couple of the new features to be included in version 2.2.
Have you heard something like these feature requests:
“I take French lessons online. I meet with my tutor twice a week. But every Tuesday we spend some time refreshing what we’ve covered on Thursday. I’d pay extra if I could replay the recording of the previous session on my own time.”
“I have to record each conversation with a customer and store it for legal reasons.”
Until now, once an OpenTok-powered conversation ended, there was no way to go back and see what was said. In a lot of scenarios (including the ones above) you could add a lot of value to your product by recording the conversation and making it available on demand.
Today we’re announcing new Intelligent Quality Controls in the OpenTok platform. To catch everyone up, Intelligent Quality Controls are the features and enhancements we’re developing to make sure that each participant in a video call has the best possible experience.
Update (Nov 25): Developers, check out our new blog post that provides details on using dynamic frame rate controls.
You may recall that over the summer we launched traffic shaping for the audio-only fallback feature. This feature drops video in low bandwidth situations to prevent a participant with poor QOS from dragging down the video quality for everyone else. Essentially, we built the automatic (video) mute button for “that guy on his cell phone in a convertible!”