Featured Articles

5th Generation Broadwell 14nm family comes in three lines

5th Generation Broadwell 14nm family comes in three lines

Intel's 5th Core processor family, codenamed Broadwell, will launch in three lines for the mobile segment. We are talking about upcoming…

More...
Broadwell Chromebooks coming in late Q1 2015

Broadwell Chromebooks coming in late Q1 2015

Google's Chromebook OS should be updating automatically every six weeks, but Intel doesn't come close with its hardware refresh schedule.

More...
New round of Nexus phone rumour kicks off

New round of Nexus phone rumour kicks off

Rumours involving upcoming Nexus devices are nothing uncommon, but this year there is a fair bit of confusion, especially on the…

More...
Nvidia officially launches the 8-inch Shield Tablet

Nvidia officially launches the 8-inch Shield Tablet

As expected and reported earlier, Nvidia has now officially announced its newest Shield device, the new 8-inch Shield Tablet. While the…

More...
Aerocool Dead Silence reviewed

Aerocool Dead Silence reviewed

Aerocool is well known for its gamer cases with aggressive styling. However, the Dead Silence chassis offers consumers a new choice,…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Tuesday, 25 January 2011 10:27

Google wants reference for VP8

Written by Nick Farell
google

Submits algorithm to the IETF
Google has asked the Internet Engineering Task Force (IETF) to have a look at  the bitstream specification for its VP8 video compression algorithm. Google said that the move was not a move towards standardization but had the aim of creating a definitive reference for the technology.

IETF publishes Request For Comment (RFC) memoranda, used to describe various technologies used on the Internet. The draft does not describe the codec and it admits that there might be differences between the draft and the reference source code published by Google.

This would make it difficult to get the everything nicely standardised, but would mean that the search engine outfit wants a  better specification that allows implementers to support VP8 without having to make reference to thousands of lines of source code. However it does show that Google is putting a lot of weight behind V8.


Nick Farell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments