Technically WebRTC and SyntaxNet have nothing in common. What they do have in common is that Google again makes it easy to add capabilities, once in the hands of the rich and experts, as a feature into applications. Once this is possible, Natural Language Understanding (NLU) can be added also into WebRTC applications. How can WebRTC applications benefit from it?
SyntaxNet and WebRTC, It’s The Same Story All Over Again
Google is again taking a technology that was until now in the hands of the rich and experts making it a feature in any application. SyntaxNet will do the same to the complex technology of NLU. With SyntaxNet becoming a free to use open source, Google is doing to NLU what it did in 2011 to communications. Both WebRTC and NLU are technologies. They can be combined together
Clearing The Fog From The Apple WebRTC Relationship
While people have questioned the likelihood of Apple adding WebRTC anytime soon it is now clear to all that the WebRTC train has left the Apple planning station and is now parking at development. From the simple statement on Apple’s Webkit status page saying it is “In Development” it is still hard to understand the details. Our live Webinar & Q&A will answer some of them.
Mitel-Polycom Deal: Stems From Power or Despair?
Mitel needed much more feet in the ground and Polycom was the right answer to this need. Playing it right, Mitel will be able to capitalize on this strong market presence of Polycom in the enterprise market.
The Polycom Mitel deal is a result of the need of 2 companies to improve their market position in face of competition coming from collaboration services.
Topic of The Month: Do We Need Standards for WebRTC?
Learning from the SIP standard, implementations by vendors are in many cases diverted from the pure standard to proprietary versions of SIP thus requiring mediation between vendor environments. Which areas of WebRTC should be covered by the standards and which areas should be left for the vendors to decide on? What level of interoperability and compatibility do we want to have?
The End of Transcoding WebRTC Video Sessions
Google published the release notes of Chrome 50. It now supports H.264 (behind a flag). Google adds H.264 to Chrome. This was an expected addition to Chrome given the WebRTC Mandatory to Implement video codec decision at the IETF that both VP8 and H.264 should be supported by browsers. Does this put an end to the need for WebRTC video transcoding and to server side decode and encode?
- « Previous Page
- 1
- …
- 5
- 6
- 7
- 8
- 9
- …
- 19
- Next Page »