Tag: VP8

What to see @ IBC 2011 : a selection of products for Streaming Workflows

If you got a plane for Amsterdam in September, there’s a chance that it’s not (only) to make you bulldog walking under the red lights : you will probably be undermining your new pair of shoes in the alleys of the RAI, seeking the freshness of streaming video innovations.

Each year the trip is too short – and the feet do hurt – especially if you didn’t carefully select your target booths in advance in order to see the more interesting technology breakthroughs. While making this preparation exercise, I thought that I could share my choices, in order to save your time and shoes a bit, and to hear back your tips as comments. So here are some suggestions of visits to arrange if your job is to build streaming-media-oriented-production-workflows like I do.



WebM Streaming [Streaming Video Technologies Panorama, part 3]

WebM is surely one of the hotest streaming topics right now, because it’s one of the two final HTML5 video standards with H.264. When Google bought On2 in 2009 and open-sourced its latest VP8 codec one year later, two promises were made : providing a codec which quality can compete with H.264 , and providing it in a royalty-free way. On the quality point, the general opinion is that the VP8 codec is slightly less performing than H.264 – but it can be an acceptable trade-off regarding the royalties point.

Precisely, the royalty-free point is the one which raises the more questions now, as MPEG-LA is said to have a lineup of 12 patent owners ready to claim their rights on intellectual property, as VP8 would use compression techniques taken from H.264. Seeing their fight against Google being a success would cause a major setback in HTML5 standardization efforts around open source solutions – WebM then being another coding technology subject to royalties after H.264. Nevertheless, the patent war has not started yet and WebM is still a good alternative to H.264, on the paper. And that’s why we are curious to know how we can implement it in our existing or upcoming workflows.