At Tokbox, we believe in providing a high quality video experience by constantly upgrading our server infrastructure. In that interest, Tokbox built it’s lightweight, scalable, raw socket based messaging framework called Rumor.
One might wonder why OpenTok needs its own messaging infrastructure, being a video streaming API. The concept of an OpenTok session is similar to that of people in a room (session) talking to each other (publisher and subscribers). When someone new enters the room, those already there acknowledge their presence. Similarly, when a new client comes into an OpenTok session, the current participants are unaware of that client’s presence until they’re notified by the server that someone else has joined. Along the same lines, any actions performed by that client (such as publishing their camera) need to be relayed via the server to all the other participants on that session. Not only is it important to be assured everyone gets these messages, but it also needs to happen in a timely manner. This is where our scalable messaging architecture, Rumor, comes into place.
Update: March 13, 2014 – Please note that this blog post references the archiving functionality in our OpenTok 1.0 platform. This feature is no longer being supported. Learn more about archiving using our OpenTok 2.0 platform.
The archiving API allows developers to record video streams in an OpenTok session. These archives can be played back, or you can download the individual streams.
It turns out that downloading the individual streams does not make sharing very easy. If you recorded a conversation between two people for example you will end up with two FLV files. It would be much nicer if the two video files could be combined into one, so the resulting single video can easily be shared and played back.
This is where the stitching API comes in to play. Stitching allows you to combine an archive with up to four individual streams into a single MP4 file that can be played back in the HTML5 video player of your choice. Stitching individual videos is hard, but the stitching engine we built will time align all the individual streams, and mix the audio properly.
Today we released an early-access build of OpenTok in our labs which leverages a brand new controller stack along with WebRTC support for media transport. This is important for two main reasons.
First, our early access build fully supports an OpenTok peer-peer session using WebRTC under the covers This demonstrates an important principle we strive to provide—a consistent programming interface for application developers where the platform chooses the best underlying transport possible.
The second reason is the labs version of OpenTok on WebRTC demonstrates a fully non-Flash, HTML5 version of OpenTok.
At TokBox, we spend a lot of time keeping up with what’s going on in the world of face-to-face video, because we’re always looking for the best ways to help move the OpenTok platform forward.
Today, we’re very happy to launch OpenTok support for WebRTC through an early-access build generally available to our developer community. While WebRTC is still a ways away from being ready for end users, last week Google took a big step forward towards their vision of what WebRTC could be with their stable release of Chrome 21. That makes this an opportune time to show you what we’ve been working on behind the scenes.
Over the past weekend, July 28-29, we sponsored Hack for Change. How can you use technology to help and improve the lives of the people around you? Or better yet, how can you use video technology to make a change?
On the beautiful saturday morning, Change.org opened their Headquarters to developers, designers, and hustlers with a common goal: to build something over the weekend that can help improve the community. In the spacious office with an unlimited supply of snacks, food, energy drinks, beer, and soft drinks, hackers comfortably mingled and got to know each other.
It’s time to take control of your work. Ever notice yourself doing repetitive tasks and wished there was a way to automate? Wish there was an easier way to communicate and collaborate with co-workers?
Let’s do something about it.
On August 11, there will be a hackathon. In two days, you can be the change you wish to see in your workplace by putting together a mobile or web application that your users can use to increase their productivity and happiness at work.
Come in with your computer and your ideas, and learn how technology can help you accomplish your tasks. There will be representatives from different companies to help you and give you prizes for your efforts to improve the workplace.
TokBox friends, today is your lucky day because we’re sending one deserving startup team to TechCrunch Disrupt in San Francisco to demo their OpenTok-powered goods between September 8-12, 2012.
Startup Alley, TC Disrupt’s demo area, is set aside just for newly launched startups. Participants get 2 tickets to the full conference and one complimentary day to demo your startup for a grand total of $0 (we’ll foot the $1,995 bill). The only requirements to apply to our contest?
Your companies must be less than two years old
You have raised less than $2 million dollars in funding
Last but not least, your app must be powered by the OpenTok API
Aurelio Tinio wins TokBox’s prize (PlayStation 3) for the best use of OpenTok API. He integrated Video Chat into straymapper.com, so that pet owners who lost pets can ‘Call in’ to the animal shelter to see if his/her pet has been found! OpenTok integration in Stray Mapper is still in development and waiting for Approval.
ioHack was held with Google Technology User’s Group (GTUG) at Mashery office in San Francisco. It was a great turnout, had around 80 cool developers who built awesome applications.
At TokBox we can almost feel the excitement that developers are feeling for this year’s Google I/O conference, afterall our office is just a few blocks away from the Moscone Center. This afternoon we got to see Google tell developers about their Hangouts Platform and we were pretty excited to see what they had to offer.
It’s no secret that OpenTok and Hangouts share a lot of the same functionality, but we thought it would be really helpful for developers in our community if we pointed out some place where they differ. Afterall, for developers it should always be about using the best tool for the job.