Unfortunately, the patent licensing situation for H.265 has recently taken a turn for the worse. Two distinct patent licensing pools have formed so far, and many license holders are not represented in either. There is just one license pool for H.264. The total costs to license H.265 from these two pools is up to sixteen times more expensive than H.264, per unit. H.264 had an upper bound on yearly licensing costs, whereas H.265 has no such upper limit.
These licensing terms preclude usage of H.265 in any kind of open source or freely distributed software application, such as web browsers. They also preclude its usage in freemium products – like WebEx or Cisco Spark – which have versions that users can use for free. Thus, while H.265 is still a good fit for hardware products like our telepresence room systems, it is not something that can serve as a universal video codec across hardware and software. Thus, we believe the industry needs a high quality, next-generation codec that can be used everywhere.
To further those ends, we began a project to create a new video codec which would meet these needs. We call this project Thor. The effort is being staffed by some of the world’s most foremost codec experts, including the legendary Gisle Bjøntegaard and Arild Fuldseth, both of whom have been heavy contributors to prior video codecs. We also hired patent lawyers and consultants familiar with this technology area. We created a new codec development process which would allow us to work through the long list of patents in this space, and continually evolve our codec to work around or avoid those patents. Our efforts are far from complete, but we felt it was time to open this up to the world.
As a result, we released project Thor to the community two weeks ago. We open sourced the code, which you can find here: http://thor-codec.org. We also contributed Thor as an input to the Internet Engineering Task Force (IETF), which has begun a standards activity to develop a next-gen royalty free video codec in its NetVC workgroup. Mozilla has also been active in that group, and they have been working on technology as well (called Daala) towards the same goal. As more technology gets contributed to this cause, the greater its chance of success.
We will continue to develop Thor over the coming months, constantly evolving the codec as our patent analysis continues. We invite others to work with us – to help develop the codec, to participate in the patent analysis, or to contribute their own Intellectual Property Rights on a royalty free basis.
I have an ongoing issue with webex teams and MRA/SSO -SAML and wondering if anybody else experiences the same thing or has succesfully set it upCUCM, Unity Connection, Expressway E & C's + webex have all been setup to use SAML SSO with ADFS with the s...
I have an ongoing issue with webex teams and MRA/SSO -SAML and wondering if anybody else experiences the same thing or has successfully set it up CUCM, Unity Connection, Expressway E & C's + webex have all been setup to use SAML SSO with ADFS wit...
I have a Cisco 8961 running sip8961.9-4-2SR4-1 firmware. On my config file I have Bluetooth and the USB ports enabled. When I plug in a USB device it says that the port is disabled by the administrator. When I try to find Bluetooth in the setting I c...
I have a Cisco 2911 router with the UC license running IOS c2900-universalk9-mz.SPA.157-3.M.bin abd a SM-ES2-24-P switch installed into it with 5 IP phones connected to the switch. Please note that this is a Service Module switch and not an external switc...
We have registered Webex Team (Windows )with CUCM.My Queries are following:1.Shall CUCM corporate directory work on Webex Teams,just like it works on Cisco Jabber.2.How can we retrieve voicemail on Webex Teams ,just like we do on Cisco Jabber.