Skip to main content

Home/ Open Web/ Group items tagged open codecs

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

Google to open source vp8 video codec - The Inquirer - 0 views

www.theinquirer.net/...google-source-vp8-video-codec

google VP8 open codecs

shared by Paul Merrell on 17 Apr 10 - Cached
  • By making VP8 open source Google will provide a high-quality and open alternative to H.264 and other existing codecs. When VP8 was first launched its inventors at On2 claimed it could provide "50 percent bandwidth savings compared to leading H.264 implementations." The move has the backing of the Free Software Foundation (FSF) as a way of killing Flash and avoiding potential lock-in to patented technology.
Paul Merrell

Open letter to Google: free VP8, and use it on YouTube - Free Software Foundation - 0 views

www.fsf.org/...oogle-free-on2-vp8-for-youtube

Google FSF Flash DRM VP8 open codecs

shared by Paul Merrell on 20 Feb 10 - Cached
  • Dear Google, With your purchase of On2, you now own both the world's largest video site (YouTube) and all the patents behind a new high performance video codec -- VP8. Just think what you can achieve by releasing the VP8 codec under an irrevocable royalty-free license and pushing it out to users on YouTube? You can end the web's dependence on patent-encumbered video formats and proprietary software (Flash).
  • This ability to offer a free format on YouTube, however, is only a tiny fraction of your real leverage. The real party starts when you begin to encourage users' browsers to support free formats. There are lots of ways to do this. Our favorite would be for YouTube to switch from Flash to free formats and HTML, offering users with obsolete browsers a plugin or a new browser (free software, of course). Apple has had the mettle to ditch Flash on the iPhone and the iPad -- albeit for suspect reasons and using abhorrent methods (DRM) -- and this has pushed web developers to make Flash-free alternatives of their pages. You could do the same with YouTube, for better reasons, and it would be a death-blow to Flash's dominance in web video.
  • If you care about free software and the free web (a movement and medium to which you owe your success) you must take bold action to replace Flash with free standards and free formats. Patented video codecs have already done untold harm to the web and its users, and this will continue until we stop it. Because patent-encumbered formats were costly to incorporate into browsers, a bloated, ill-suited piece of proprietary software (Flash) became the de facto standard for online video. Until we move to free formats, the threat of patent lawsuits and licensing fees hangs over every software developer, video creator, hardware maker, web site and corporation -- including you.
Gary Edwards

Google Chrome 5 WebKit - Firefox - Opera Comparisons - BusinessWeek - 0 views

www.businessweek.com/...google-chrome-5.html

Chrome Chrome-5 HTML5 HTML5-CSS3-JavaScript

shared by Gary Edwards on 23 Jun 10 - Cached
  • Gary Edwards on 23 Jun 10
     
    Chrome runs as close as any browser can to the bleeding edge of Web standards. Though it uses the same open source WebKit rendering engine as Safari, it doesn't reliably support the controversial, proprietary CSS3 transformation and animation tricks that Apple's built into Safari. However, like every browser I tested, it earned a perfect score in a compatibility test for CSS3 selectors, and it joined Safari and Opera with a flawless score of 100 in the Acid3 web standards benchmark. Chrome 5 also supports both Apple's H.264 codec and Mozilla's preferred open source Ogg Theora technology for plugin-free HTML5 video, and it beautifully played back HTML5 demo videos from YouTube and Brightcove. In XHTML and CSS tests, Chrome was surprisingly slower than Safari, despite their shared rendering engine -- but the race was close. Safari rendered a local XHTML test page in 0.58 seconds to Chrome's 0.78 seconds, and a local CSS test page in 33 milliseconds to Chrome's 51 milliseconds. Note that Chrome still rendered XHTML more than twice as fast as Opera (1.67 seconds) and left Firefox (12.42 seconds--no, that's not a typo) eating its dust. In CSS, it also beat the pants off Opera (193 milliseconds) and Firefox (342 milliseconds). But Chrome shines brightest when handling JavaScript. Its V8 engine zipped through the SunSpider Javascript benchmark in 448.6 milliseconds, narrowly beating Opera's 485.8 milliseconds, and absolutely plastering Firefox's 1,161.4 milliseconds. However, Safari 5's time of 376.3 miliseconds in the SunSpider test beat Chrome 5 handily.
Paul Merrell

Exploring HTML 5's Audio/Video Multimedia Support - 0 views

www.devx.com/43324

HTML 5 audio video multimedia

shared by Paul Merrell on 21 Nov 09 - Cached
  • Because HTML 4.0 essentially was a "frozen" version, the specific mechanism for displaying content has been very much format dependent (e.g., Apple QuickTime Movies and Flash video) and usually relies upon tags with varying parameters for passing the relevant information to the server. As a result, video and audio embedding on web pages has become something of a black art . Its perhaps not surprising then that the <audio> and <video> tags were among the first features to be added to the HTML 5 specification, and these seem to be the first elements of the HTML 5 specification that browser vendors implemented. These particular elements are intended to enable the browser to work with both types of media in an easy-to-use manner. An included support API gives users finer-grained control.
  • Theoretically, the <video> and <audio> elements should be able to handle most of the codecs currently in use. In practice, however, the browsers that do currently support these elements do so only for the open source Ogg Vorbis and Theora standards.
  • Paul Merrell on 21 Nov 09
     
    Kurt Cagle digs into audio and video support in HTML 5. As always, his view is revealing.
1 - 4 of 4
Showing 20▼ items per page