It looks like WebRTC is actually gaining traction with our customers. Very briefly, they see it as a more reliable alternative to UDP for transferring video over the Internet. I thought that it would be a good idea to share with you what we are working on in a separate post.
What we are working on now
We've implemented a new signaling server (Signalmaster). This is a much more mature solution than what we've had previously. It is written in Node.js and can actually be deployed in production environments. It has allowed us to add the following features:
- Support for SSL-protected data exchange with the signaling sever (we've adapted the BoringSSL lib from the WebRTC project).
- An option to log in to the signaling server with a password.
- Proper support for rooms in the signaling server.
Also, we are about to complete the integration with the SimpleWebRTC project, which is an easy-to-use framework that helps build things like video conferencing apps (Talky.io is a cool example). If your project is built with SimpleWebRTC, it will be very easy to integrate with our SDKs.
Finally, we will monitor the connection with the signaling server and will reconnect automatically when needed.
These features are already available in the current release of MPlatform SDK (MFormats SDK to follow). Click here for more details.
Our plans for the next iteration
- Add a way to choose one of the native WebRTC codecs: VP8, VP9 or H.264 (now VP8 is used).
- Implement a custom data channel and use it to transfer XML metadata.
- Add support for interlaced video encoding (50i, 60i).
Plans for the future
- Add timecode support and timecode mapping for metadata.
- Add third-party codecs support (NVENC, Quick Sync).
- Add multichannel audio transfer via data channel (in sync with video).
Thinking about trying WebRTC? Let us know if you have any questions. There's also some technical information already available here.