Linked by Thom Holwerda on Mon 25th Mar 2013 21:09 UTC
Legal Late last week, Nokia dropped what many consider to be a bomb on the WebM project: a list of patents that VP8 supposedly infringes in the form of an IETF IPR declaration. The list has made the rounds around the web, often reported as proof that VP8 infringes upon Nokia's patents. All this stuff rang a bell. Haven't we been here before? Yup, we have, with another open source codec called Opus. Qualcomm and Huawei made the same claims as Nokia did, but they turned out to be complete bogus. As it turns out, this is standard practice in the dirty business of the patent licensing industry.
Thread beginning with comment 557025
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[18]: Big picture...
by lemur2 on Fri 29th Mar 2013 05:50 UTC in reply to "RE[17]: Big picture..."
Member since:

I'm not sure where you're getting your 1/3 number, can you provide data for that?

However, you can make up the quality difference in that one third of cases where h.264 is better by opting for a higher profile when encoding VP8.

Ok, you pick the highest profile from each of VP8 and x264 and you find x264 gives you better quality: how do you now make up for the quality difference?

Several times I said that this applied "to the quality of video as used over the web". This is more or less "default profile", as very little web video is encoded at high profiles. When you are looking at a video of a newscaster on some web news page, or looking at standard resolutions on youtube, you are simply not looking at the highest profile.

When you are constrained to use only one profile for each codec (even though profiles are not equivalent), then one can always find some cases where VP8 cannot match h.264. Then again, for another profile and another use case, the reverse can also apply ... one cannot get h.264 to match VP8 in some profiles.


Reply Parent Score: 2

RE[19]: Big picture...
by saynte on Fri 29th Mar 2013 06:33 in reply to "RE[18]: Big picture..."
saynte Member since:

Several times I said that this applied "to the quality of video as used over the web". This is more or less "default profile"

Well, which one is it now, only the profile "used on the web", or "you can always pick a higher profile" ?

How do you know what's used on the web?

Youtube recommends H264 high profile to be used, and I would assume they have decent recommendations:

My 2 year old phone can decode H.264 high profile, I don't think its unreasonable to use it as the representation of highest quality, that's what it is there for after all.

Reply Parent Score: 2