MPEG LA Declares H.264 Standard Permanently Royalty-Free


Recommended Posts

MPEG LA Declares H.264 Standard Permanently Royalty-Free

164049-mpeg_la_logo.jpg

MPEG LA, the group that oversees licensing for a number of Internet media standards, today announced that Internet broadcast content using the H.264 video coding standard will remain royalty-free for the entire life of the license, quashing fears that the standard could suddenly become subject to royalty payments in 2016 after the current licensing term expires and is required to be renewed.

MPEG LA announced today that its AVC Patent Portfolio License will continue not to charge royalties for Internet Video that is free to end users (known as "Internet Broadcast AVC Video") during the entire life of this License. MPEG LA previously announced it would not charge royalties for such video through December 31, 2015, and today's announcement makes clear that royalties will continue not to be charged for such video beyond that time.

H.264 is the video content standard that has been embraced by a broad array of content providers including Apple, which owns several of the patents included in the technology's portfolio. Today's announcement also paves the way for H.264 to become the standard video format for HTML5, which had seen some contributors, such as Mozilla and Opera, supporting Ogg Theora as a royalty-free video standard.

Earlier this year, Google announced its own video standard, WebM, claiming that it would be a royalty-free alternative to H.264. Questions were raised, however, about whether WebM truly could be royalty-free, with MPEG LA even going as far as to suggest that it was looking into putting together a patent pool to assert the rights of intellectual property holders associated with the WebM/VP8 standard.

Source: Mac Rumors

Just found out that this means its free for end-users ONLY. Mozilla will still have to pay the MPEG-LA $5m/yr to include h264 in firefox. Quite a chunk of money, i hope they do this, maybe they could ask google, microsoft and apple to donate 1/3rd each :)

Here is the confirmation that this is true and not just a rumour that h264 will be free forever: http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/231/n-10-08-26.pdf

Just found out that this means its free for end-users ONLY. Mozilla will still have to pay the MPEG-LA $5m/yr to include h264 in firefox. Quite a chunk of money, i hope they do this, maybe they could ask google, microsoft and apple to donate 1/3rd each :)

Here is the confirmation that this is true and not just a rumour that h264 will be free forever: http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/231/n-10-08-26.pdf

If the browser makers have to pay anything I think we call this a right off.

Just found out that this means its free for end-users ONLY. Mozilla will still have to pay the MPEG-LA $5m/yr to include h264 in firefox. Quite a chunk of money, i hope they do this, maybe they could ask google, microsoft and apple to donate 1/3rd each :)

Here is the confirmation that this is true and not just a rumour that h264 will be free forever: http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/231/n-10-08-26.pdf

What??? Can't the MPEG LA add some sort of "if primary use is a web browser, don't have to pay" clause. Or even reduced fee?

Don't they understand this'll mean their format will be picked up across the web?

Why, i'm sure mozilla can easily get $5m extra from donations if they start a donation campaign or they could just choose to spend money on that instead of other areas.

If Opera and Mozilla can pay for these then youtube can abandon encoded all it's videos in WebM, that format could be abandoned, they could instead make a WebM2 to be of better quality than h264 and hope that becomes a standard. I would LOVE to use youtube without flash, its so jerky and uses so much cpu even on core2 cpu's.

Lets hope Google, Opera and Mozilla make official statements about this within the next 48hrs about their intentions of supporting it in firefox, opera and the intentions for youtube.

What??? Can't the MPEG LA add some sort of "if primary use is a web browser, don't have to pay" clause. Or even reduced fee?

Don't they understand this'll mean their format will be picked up across the web?

they certainly could be seeing as they they just released that press release clearly they don't intend to do that or they would have done it at the same time. The MPEG-LA is there to make money, they would like the $5m/yr from opera and mozilla and it would become a web standard and so pay sites using h264 will add support and will have to pay fees to mpeg-la which would be VERY lucrative for them. I think they are gambling on the fact that opera and mozilla will just pay up, if they don't they will probably let them have it for free in 6 months maybe.

Just found out that this means its free for end-users ONLY. Mozilla will still have to pay the MPEG-LA $5m/yr to include h264 in firefox. Quite a chunk of money, i hope they do this, maybe they could ask google, microsoft and apple to donate 1/3rd each :)

Here is the confirmation that this is true and not just a rumour that h264 will be free forever: http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/231/n-10-08-26.pdf

This is an interesting read: http://obamapacman.com/2010/02/the-5-million-dollar-h-264-expensive-license-myth/

Certainly better than the previous uncertainty about what could happen in the future, although still doesn't change how things are now, which is what WebM was meant to address.

Great read! Myth debunked.

Did you read the comments to the article on that link? It's the debunking of the myth that gets debunked :p

Great read! Myth debunked.

What "myth" was debunked? There was so much Engrish in that article, I had a tough time understanding its purpose. The concern about h.264 is that the patent group, like most patent groups, is predatory.

Furthermore, the title of this article (and the one it linked to) is frankly incorrect. It only applies to web video. And though that's a big segment, it hardly makes the h.264 standard royalty-free to implement. It just means those greedy ******* won't go after Johnny Q Blogger for embedding a YouTube link on his personal page.

And let's be realistic: the ONLY reason this is happening is because of WebM. If there remained concern that the h.264 patent sharks would go for pay-day in 2016, the entire web would've switched to WebM. And why do some people keep saying the h.264 is "closed-source?" That doesn't make any sense.

Did you read the comments to the article on that link? It's the debunking of the myth that gets debunked :p

I see your point, but technically, Mozilla doesn't have to pay a cent. Firefox can use the decoders built in to Windows and OS X. Linux gets screwed over, but when doesn't Linux get screwed over? I understand this is all out of principle, but seriously, unless FOSS concedes a bit, Flash is going to be the overall winner.

Why, i'm sure mozilla can easily get $5m extra from donations if they start a donation campaign or they could just choose to spend money on that instead of other areas.

Or they could just use OS's codecs. Mac and Windows have build in h264 support. Although I would prefer like MPC:HC h264 codec though.

If Opera and Mozilla can pay for these then youtube can abandon encoded all it's videos in WebM,

YouTube can't do that, that will remove a massive amount of its users due to incompatibility issues.

that format could be abandoned, they could instead make a WebM2 to be of better quality than h264

That is a really tiny visual difference and only applies to the base profile h264.

Eventually YouTube and such sites will want to stream videos in High Quality (20Mbit +), followed by 3D.

WebM fails miserably in this area.

its so jerky and uses so much cpu even on core2 cpu's.

Flash works fairly good with modern computers.

This is because modern computers have modern graphics cards which support h264.

I suggest getting the cheapest 8-series Nvidia GPU to solve your playback issues.

Sure flash does suck -> My CPU can work up to 80% with Flash Video, compared to ~30% with MPCHC playing some 1080p file. That is why h264 HTML5 should the future.

Lets hope Google, Opera and Mozilla make official statements about this within the next 48hrs about their intentions of supporting it in firefox, opera and the intentions for youtube.

I would prepare for the great IE9 migration instead.

AMAZING news, i hope firefox and opera add h264 support now :) Now we can really kill off flash for web video :)

Flash video is H.264 these days, the Flash player even takes advantage of hardware H.264 decoding support.

I see your point, but technically, Mozilla doesn't have to pay a cent. Firefox can use the decoders built in to Windows and OS X. Linux gets screwed over, but when doesn't Linux get screwed over? I understand this is all out of principle, but seriously, unless FOSS concedes a bit, Flash is going to be the overall winner.

Windows 7 and OS X you mean, while MS will soon bring the H.264 decoder to Vista in an update, the fact remains that currently only one version of Windows out of the 3 supported ones actually supports H.264 out of the box.

Windows 7 and OS X you mean, while MS will soon bring the H.264 decoder to Vista in an update, the fact remains that currently only one version of Windows out of the 3 supported ones actually supports H.264 out of the box.

Fair enough, but it's trivial to do a video tag with a Flash fallback (though you still have to use that god-awful object tag markup). The re-encoding into different formats is the time-consuming and painful part. If we can agree on one video format, then displaying HTML5 video to browsers that support it and then using a Flash player for other browsers isn't too bad of a deal to me.

Now, I suppose Firefox and Opera could just be two of the browsers that get a Flash player served to them.

They tried to standardise on one format, but the H.264 backers didn't support it.

While the format's still locked up behind patent pools and multi-million dollar yearly licensing fees, it can't be included in any web standard or by open source browsers (Neither open source versions of Chrome or WebKit support H.264)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!