"Patents are about _details_ so the mere fact that something does something like something else, isn’t necessarily something at all.
As we’ve pointed out before, many codec patents are exceptionally easy to work around: They specify every little detail because it makes it _much_ easier to get through the examination but doesn’t harm the patent’s ability to read on the final standard because the standard specifics exactly the patented behaviour.
D_S, for all his undeniable H.264 experience isn’t an expert on patents or even the H.264 patents. We can assume that in cases where VP8 looks similar to H.264 those would have been exactly the cases where care was taken to differ in the right places. I’d expect the primary risks for VP8 to be anywhere _but_ there."
more at http://blog.gingertech.net/2010/05/20/vp8-adobe-is-the-key-t...
The whole VP8/webm situation reminds me of when Microsoft tried to do the right thing and open-license VC1, but got clobbered by patent holders and had to reverse themselves.
http://x264dev.multimedia.cx/archives/589
Update: Tandberg claims they came up with the algorithm independently: to be fair, I can actually believe this to some extent, as I think the algorithm is way too obvious to be patented. Of course, they also claim that the algorithm isn’t actually identical, since they don’t want to lose their patent application.
I still don’t trust them, but it’s possible it’s merely bad research (and thus being unaware of prior art) as opposed to anything malicious. Furthermore, word from within their office suggests they’re quite possibly being honest: supposedly the development team does not read x264 code at all. So this might just all be very bad luck.
Regardless, the patent is still complete tripe, and should never have been filed.
Jason Garett-Glaser put together a great comparison of h.264 vs VP8/WebM. Check it out here: http://x264dev.multimedia.cx/archives/377
His summary: the spec is really terrible, the performance leaves a lot to be desired (though, there is a lot of room for optimization), and it 'copies too much from H.264 for comfort'.