Despite the fact that filters are used a lot in non-WebRTC video applications like Photo Booth and SnapChat, we haven’t seen many WebRTC applications using these types of filters. This is probably because it hasn’t really been possible… until now.
It has always been possible to apply filters to video streams locally using the OpenTok platform by rendering the video into a Canvas element. The problem with this approach has always been that the person on the other end does not see the filter unless you apply the same filter on both the publisher and subscriber video. This would mean significant CPU load if you are subscribing to multiple participants. It also means that you don’t get to see the filters in the Archives.
In today’s increasingly fragmented digital world, the way fans consume and engage with sports content has fundamentally changed. While teams may still win the hearts of loyal fans, sporting organizations and broadcasters aren’t capturing their attention like they once did.
To win the hearts, minds and eyes of the new generation of sports fans – who are always online, on mobile and on social – broadcasters are leveraging live video to create all new interactive and participatory fan engagement experiences.
As global access to the internet continues to grow we find ourselves in an increasingly connected world. Never in our collective history have so many people had the ability to access so much information about what is going on in the world around them. This has led to an unprecedented rise in engagement with current events, especially amongst the young people whose voracious appetite to rant, debate and ‘be heard’ has fueled the emergence of so many social media platforms.
I was talking with our old friend Philipp Hancke and discussing how it could be possible that 12% of the WebRTC calls were failing. This number came as a surprise to us as, based on our reports, the number of failures is significantly lower when it comes to OpenTok calls, even though the exact numbers depend on the specific use case you have.
So, we decided to grab some data and try to prove that WebRTC, at least in our platform, is doing a much better job.
When evaluating a new product or service, we know how important it is to be able to test out the technology first. Stakeholders in different areas of the business, both developers and non developers, need to see and understand how the technology works.
We’ve noticed that for customers evaluating the OpenTok platform, without using the API, it can be challenging to visualise your use case. Even when a developer works through our Quick Start Guide, there can be a need for additional implementation to build a custom proof of concept. All of this translates into time invested during the business’ evaluation phase of the product; worse yet, it can lead to an incomplete or inaccurate evaluation.