Slashdot Mirror


Ogg Vorbis / Theora Language Removed From HTML5 Spec

Rudd-O writes "It's official. Ogg technology has been removed from the HTML5 spec, after Ian caved in the face of pressure from Apple and Nokia. Unless massive pressure is exerted on the HTML5 spec editing process, the Web authoring world will continue to endure our modern proprietary Tower of Babel. Note that HTML5 in no way required Ogg (as denoted by the word 'should' instead of 'must' in the earlier draft). Adding this to the fact that there are widely available patent-free implementations of Ogg technology, there is really no excuse for Apple and Nokia to say that they couldn't in good faith implement HTML5 as previously formulated."

65 of 395 comments (clear)

  1. Ogg mad! by Anonymous Coward · · Score: 5, Funny

    Ogg the cavemen break Apple and Nokia heads with open source CD!

  2. Figures by strikeleader · · Score: 4, Insightful

    And once again the public loses

    1. Re:Figures by Anonymous+Brave+Guy · · Score: 3, Insightful

      I'm sorry, but how is it a loss for the public to remove any reference to specific media formats from a specification that should by its nature be format independent? Ogg had no more business being in an HTML spec than WMV, RA, or some Flash-based video player.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    2. Re:Figures by Ignorant+Aardvark · · Score: 3, Insightful

      I'm sorry, but how is it a loss for the public to remove any reference to specific media formats from a specification that should by its nature be format independent? Ogg had no more business being in an HTML spec than WMV, RA, or some Flash-based video player.

      Methinks you are being a bit myopic here. Where would we be today if the HTML spec didn't specify jpg, gif, and png as baseline standards for the image tag? Can you imagine a huge mishmash of competing proprietary image standards, many of which wouldn't even render in free software browsers like Firefox? That would be a nightmare, but unfortunately, that's what's currently happening with video. Much like the image standard in HTML means that any browser can display anything in an image tag, so too must the video standard in HTML guarantee that any browser can display anything in a video tag. That's what the proposed specification is about.

      The web isn't just about static text. It's about images too (and thankfully, the HTML specification handles them well). And what with the increasing prevalence of broadband connections, it's becoming more about videos each and every day. We need a standard that actually works for videos. Because what we currently have is broken. HTML is a standard; it only works when it specifies exactly which formats are to be used, and thus, what must be implemented by browsers. Ogg/Theora must stay in the HTML5 specification, or there will be no end in sight for the web's video woes.

    3. Re:Figures by Bogtha · · Score: 5, Insightful

      I'm not sure if you are trying to be ironic here or if you are actually serious.

      Where would we be today if the HTML spec didn't specify jpg, gif, and png as baseline standards for the image tag?

      No HTML specification does that. The farthest any HTML specification goes is mentioning that they are common formats.

      Can you imagine a huge mishmash of competing proprietary image standards, many of which wouldn't even render in free software browsers like Firefox?

      Yes, in fact that's precisely the state of the world today. For instance, Firefox doesn't support JPEG 2000.

      That would be a nightmare

      Not really, because all major browsers support JPEG and PNG, despite the fact that the HTML specifications haven't recommended them.

      HTML is a standard; it only works when it specifies exactly which formats are to be used

      It does no such thing. For instance, it doesn't require browsers to implement JavaScript, it provides scripting language-independent hooks that can be used to support JavaScript or any other scripting language. It doesn't require browsers to implement CSS, it provides stylesheet language-independent hooks that can be used to support CSS or any other stylesheet language. It doesn't require browsers to implement JPEG or PNG, it provides image format-independent hooks that can be used to support JPEG, PNG or any other image format. And the HTML 5 specification is taking the exact same approach by not requiring Theora or Vorbis, but providing codec-independent hooks that can be used to support Theora, Vorbis or any other codec.

      The choice of video and audio codecs is outside the scope of the HTML 5 specification. Attempting to more tightly couple independent formats is myopic.

      --
      Bogtha Bogtha Bogtha
    4. Re:Figures by DragonWriter · · Score: 2, Insightful

      It doesn't require browsers to implement JPEG or PNG, it provides image format-independent hooks that can be used to support JPEG, PNG or any other image format. And the HTML 5 specification is taking the exact same approach by not requiring Theora or Vorbis, but providing codec-independent hooks that can be used to support Theora, Vorbis or any other codec.


      Even before mention of Ogg formats was removed, HTML5 would not have required those formats. You correctly note that current the HTML 4.01 recommendation doesn't require JPEG, PNG, etc., but you fail to note that it does specifically mention three image formats, and they are "GIF, JPEG, and PNG".

      Of course, if you did mention that, it would be a lot harder to use the current recommendations treatment of images to argue that removing the mention of Ogg formats from the HTML5 draft is consistent with the way prior HTML standards have treated images.

    5. Re:Figures by Bogtha · · Score: 4, Informative

      You correctly note that current the HTML 4.01 recommendation doesn't require JPEG, PNG, etc., but you fail to note that it does specifically mention three image formats, and they are "GIF, JPEG, and PNG".

      Yes, it mentions them, it doesn't recommend them. Look at what it says:

      src = uri [CT] This attribute specifies the location of the image resource. Examples of widely recognized image formats include GIF, JPEG, and PNG.

      It mentions them as examples to illustrate how the <img> element type is used, not in order to promote them and certainly not to "specify them as baseline standards" as Ignorant Aardvark was claiming.

      And how in hell did I "fail to note" that it mentions them? I explicitly said it mentions them.

      Of course, if you did mention that, it would be a lot harder to use the current recommendations treatment of images to argue that removing the mention of Ogg formats from the HTML5 draft is consistent with the way prior HTML standards have treated images.

      That's simply not true. There is a world of difference between mentioning popular formats as examples and saying that vendors should implement them.

      --
      Bogtha Bogtha Bogtha
  3. An alternative... by drakaan · · Score: 5, Interesting

    Instead of specifying a specific format, just specify the salient details...how about "...MUST use a non-patent-encumbered format that is released under an OSI-approved license...". Well, not that, per-se, but you get my drift.

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    1. Re:An alternative... by drakaan · · Score: 2, Interesting

      Well, if the codec is unencumbered, then there will be wide availability. After that, it becomes a matter of popularity. Saying "Codec Hell" is like saying "Window Manager Hell", it's fun, but meaningless in the end. Sure, there are a lot of different WMs, but there are a handful that people use, and just as with video format, people usually pick a favorite and stick with it.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    2. Re:An alternative... by drakaan · · Score: 3, Interesting

      Does that mean that HTML5 should specify PNG exclusively for image content? This isn't so much about a specific standard as it is about *open* standards. Nokia and Apple are hand-wringing and whining because the standard specified a specific format other than quicktime (and whatever format Nokia has up it's sleeve). Provided Apple and Nokia are putting forward new codecs licensed under the same terms as Ogg (or at least in-line with the spec's recommendation), what's wrong with letting them then compete on their technical merits?

      I'm not saying I want windows media, quicktime, and realplayer to be considered, but if there was an incentive to honestly open those formats to implementation by anyone, for free, with no catch, I'd be fine with allowing them.

      It's not beating around the bush that's causing the document format controversy, it's exactly the same issue that's present here. There's no place where it says "hey, if you create a document, it has to be in a format that has these attributes". *Because* of this controversy, organizations, companies, and governments are actually looking at the issue of access and seeing that open standards matter.

      To me, this type of change serves to drag the issue that remains unobvious to most people straight into the light of day. If Nokia and Apple take issue with the changed language, then they have to discuss the differences in licensing between their preferred formats and Ogg before they can do anything else. That ain't a bad thing.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    3. Re:An alternative... by Whatanut · · Score: 5, Insightful

      So... are you a developer for inkscape or something? Beyond the first few sentences that just turned into an inkscape advertisement.

      --

      yvan eht nioj
    4. Re:An alternative... by cching · · Score: 2, Informative

      What are you seeing as the big reason you'd have to supply media in multiple formats? I have to provide multiple formats because it's hard for users to find the right codecs to be able to consume my media. *You* don't think it is a problem, but I'm telling you that in reality, it *is*. For instance, some media players don't support MPEG-4 but they do support .WMV. And it's just the opposite for other players. I don't know, I guess I thought everyone understood this. Audio is slightly better, but I still run into the same problems. There's a reason that sites like amazon.com provide two different audio formats so that people can preview the music. Welcome to 1998, it really hasn't gotten much better since then. I do believe that standards would make this better.
  4. Who the hell is Ian? by Anonymous Coward · · Score: 2, Insightful

    We don't all live in this world and know the players.

    1. Re:Who the hell is Ian? by ricebowl · · Score: 2, Funny

      We don't all live in this world

      You know, I've thought that for the longest time...

    2. Re:Who the hell is Ian? by Penfold1234 · · Score: 2, Informative

      I assume it's referring to Ian Hickson, who's a member of the HTML5 working group.
      If not, then I have no idea...

      The only reason that I am even in a position to guess this is because I happened to go to University with him, so I agree the summary could use some work.

  5. If HTML5 gets adopted by Anonymous Coward · · Score: 5, Interesting

    there are bigger problems than Ogg!

    For one, it will mean the death of any lightweight web browser. Web will become something like a TV where you are fed with content you cannot filter (because the TV is too complex to hack). Monopoly through complexity.

    A simple new format that is designed from the start for vector graphics and that doesn't try to be backwards compatible with HTML would be the best way for the new web.

    1. Re:If HTML5 gets adopted by Anonymous Coward · · Score: 5, Insightful

      Having the web be just like TV is exactly what large companies want. The marketting tards want you to see their company website exactly the way they think it's supposed to look. They certainly don't want people filtering content or anything like that. Why do you think Flash only websites are becoming so popular? The problem is mostly due to management and marketting types having no idea how the internet works.

      On the plus side, it might be a pretty good filter all by itself. The second you see a site using HTML5, you automatically know it's probably not worth browsing.

    2. Re:If HTML5 gets adopted by kabloom · · Score: 2, Insightful

      A simple new format that is designed from the start for vector graphics and that doesn't try to be backwards compatible with HTML would be the best way for the new web. That will only solve half the problem with the Web. Personally, I believe that browers today is incapable of enforcing the kind security policy required for e-commerce, since they are vulnerable to things like cross site request forgeries and other such things. Time to design a new open protocol.
  6. ...now that I read the changes... by drakaan · · Score: 5, Informative

    I see that what I just suggested is exactly the change they made. I'm fine with that...off to tag the front-page article with "badsummary"

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  7. Well, these companies show their true colors by the_humeister · · Score: 4, Insightful

    MSFT isn't the only one who pulls crap like this. AAPL and NOK would gladly do the same things if they can get away with it.

    1. Re:Well, these companies show their true colors by base3 · · Score: 5, Insightful

      I've always said that Apple is just like Microsoft, only not as good at it. Of course, saying so is a ticked to -1 as Apple apologists empty their clips of mod points into any post that doesn't hail Steve Jobs as the savior of computing. But I've got the karma :).

      --
      One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
    2. Re:Well, these companies show their true colors by ByOhTek · · Score: 3, Funny

      Of course, saying so is a ticked to -1 as Apple apologists empty their clips of mod points


      WTF. For them to be appologists, they have to have the ability to think something was wrong, and they are so in love with their lord an savior, happily and arrogantly trapped behind the reality distortion field...

      BURN KARMA BURN!
      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    3. Re:Well, these companies show their true colors by Sparks23 · · Score: 2, Interesting

      Without really knowing what happened behind closed doors there... I suspect the issue is less desktop browsers and more mobile browsers. Nokia (with the S60 browser) and Apple (with Safari Mobile) both use WebKit on their phones, thus being two of the only handset providers to need to deal with 'the real web' on small portable devices... as a developer, I can see trying to embed the OGG container format and the Vorbis codec into a mobile browser being a pain-in-the-ass. (And yes, even if 'optional,' I'm fairly sure they'd want to support it.)

      This is a little ironic, given we have two companies whose browser team (both use WebKit, after all) love to blog about 'why can't we have some solid standards,' and about how there is no one true standard for images, embedded documents, etc. I think Apple and Nokia are shooting themselves in the foot here rather than taking the opportunity to run with standardizing other things (image formats, /page encoding character-sets/, etc.).

      But I think this is less nefarious/evil and more just short-sighted focus on one problematic area of implementation rather than on the overall gains.

      --
      --Rachel
  8. Doesn't make sense... by binaryspiral · · Score: 5, Interesting

    If the format is free of patents, and is essentially open source (released under the BSD license)... how can Nokia shake its finger around and threaten people?

    This wouldn't be a story if Microsoft had done it, trying to force WMP codecs into the standard - I'm actually kind of surprised they hadn't yet... but Nokia? wtf

    1. Re:Doesn't make sense... by gnasher719 · · Score: 2, Informative

      FYI yes its patented but its under a 'free for all' licence. Anyone can use it for any purpose for free (both beer and freedom). Who knows if there are any other patents lurking? We know from the MP3 history: Yes, everyone knew there were tons of patents, but you could buy a license for all the patents for quiet a reasonable fee, which for example Microsoft did. Then suddenly someone comes up with a claim for a patent that is not covered by that pool and sues Microsoft for billions.

      Same thing could happen with Ogg as well. Make it part of the HTML5 standard, convince Apple, Nokia and Microsoft to use it, and four years from now when every browser in the world supports it, someone comes out with a patent claim and sues everyone. It doesn't happen right now because trying to enforce a patent on Ogg won't make you any money.
  9. Not a requirement by Bogtha · · Score: 5, Insightful

    Note that HTML5 in no way required Ogg

    So what's the point in having it in there then? The vendors who don't want to implement it won't, and the people wanting an open baseline won't get one. The recommendation did nothing for openness or interoperability, it just gave people an official excuse to bash vendors that won't implement it.

    All other things being equal, a smaller specification that everybody can agree on is better than one with unnecessary, contentious recommendations. There was never any need for this recommendation, it just bloated the already massive specification.

    --
    Bogtha Bogtha Bogtha
    1. Re:Not a requirement by Americano · · Score: 2, Insightful

      False Dilemma :
      "The informal fallacy of false dilemma--also known as false choice, false dichotomy, falsified dilemma, fallacy of the excluded middle, black and white thinking, false correlative, either/or fallacy, and bifurcation--involves a situation in which two alternative statements are held to be the only possible options, when in reality there exists one or more other options which have not been considered."
      Standards are attempts to make a set of behaviors explicit & well-defined -- they are the requirements document which developers work from when they attempt to implement a standards-compliant program. As such, they need to be very clear about what is and what is not allowed, and avoid making lots of limp-wristed "should" and "may" statements -- if you're not willing to say, "this is required," then why put it in the standard if standards implementers are free to disregard it as they see fit?

      You're right -- the entire standard is optional to begin with. So why include a bunch of optional recommendations that just allow standards implementers to claim compliance with the standard while ignoring the sections of the standard that are optional and hard to implement? Think about it:
      • If Apple can legitimately claim HTML5 compliance for Safari while not supporting Ogg Theora;
        AND
      • If Mozilla can legitimately claim HTML5 compliance for Firefox while supporting Ogg Theora;
      Then what's the point of "recommending" Ogg Theora in the standard to begin with? It's not required, so as someone writing code to be rendered in an HTML5-compliant browser, you can't assume it's supported.

      Reading Ian's remarks, and the new paragraph in the spec, it sounds like they recognize the need for some sort of baseline standard audio/video codec in HTML5, and I agree that that's beneficial, and a net good for the standard -- but if they're not willing to say it's required, then including it as "just a recommendation" is simply a way of ensuring that the current confusion and lack of standards continues, while loudly claiming that you've addressed the problem, and I think that would be a net "bad thing" for the standard.
  10. Web Standards by bunratty · · Score: 2, Insightful

    I don't see that the edit makes much of a difference. Even if HTML5 says that user agents SHOULD support Ogg, it doesn't mean they all will. And even though HTML 5 doesn't mention Ogg, it doesn't mean they all won't.

    As every web developer knows, what you can and cannot do on a web site has less to do with what the standards say, and more to do with what browsers decide to support. There are web standards that have been specified for years that developers still cannot use (for example, much of the CSS in the Acid2 test), and there are technologies that get widely used before being standardized (for example, XMLHttpRequest).

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  11. Wierd. by ak3ldama · · Score: 4, Informative

    From the page:

    It would be helpful for interoperability if all browsers could support the same codecs. However, there are no known codecs that satisfy all the current players: we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies. This is an ongoing issue and this section will be updated once more information is available.

    What part of initially suggesting Ogg Vorbis doesn't fit with the new quote? It just seems wierd. Like they could say what they mean, but not explicitly suggest Ogg.

    --
    "but money is the God of Algiers & Mahomet their prophet." - Rich. O'Bryen June 8th 1786
    1. Re:Wierd. by ubernostrum · · Score: 4, Interesting

      What part of initially suggesting Ogg Vorbis doesn't fit with the new quote?

      The submarine patent threat. Ogg claims to be unencumbered, but until somebody big starts using it and lawsuits start flying in the Eastern District of Texas, nobody actually knows whether it's unencumbered. And companies which are already carrying a significant risk of submarine patents from other more popular/profitable codecs don't have much incentive to assume even more risk for sake of a codec that's hardly used and doesn't present compelling technical advantages.

      Some people think this is FUD. I think those people don't pay attention to patent-related news in the US; the only safe position right now is to assume something is encumbered until someone else has spent millions of dollars litigating it to be sure, which is why you get development models like SQLite: SQLite refuses to accept or use any code based on algorithms or techniques that are less then 17 years old, so that they can prove they're using technologies which couldn't possibly be patent encumbered.. Patent reform would be a nice thing to have for cases like this...

  12. There really is no excuse? by Chas · · Score: 2, Funny

    Sure there is! Lots of them!

    Greed.

    Avarice.

    Stupidity.

    Need I go on?

    --


    Chas - The one, the only.
    THANK GOD!!!
  13. Playing devil's advocate by cowwoc2001 · · Score: 2, Insightful

    I have nothing against the Ogg Vorbis format, but how is it the business of an HTML spec as to what file format is used by external links? This is no better than the spec mandating we use PNG instead of JPG. Developers will use whatever makes sense to them and it isn't really the spec's business to mandate what is really outside of its scope.

  14. say ogg WAS official by circletimessquare · · Score: 4, Interesting

    why does anyone think that would actually carry weight? reference microsoft browsers and previous standards

    make ogg official, and business will ignore it, and marginalize the standard. do we really want the standards ignored?

    so allow the businesses their moronic formats, and use ogg anyways

    it's silly if anyone thinks the war against proprietary formats is going to be won by a standards body. at the very best, business will embrace standards because the standards body play footsie with business desires, which is what happened, which is good!

    at worst, the standards body ignores business on some ideological crusade, so businesses just ignore the standards as well, and we have a worse tower of babel on our hands

    folks: this is the best possible outcome, where best possible outcome = ugly begrudging accomodation of moronic business desires. you can't do any better than what happened, unfortunate, but true

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  15. Ummmm..... by Solder+Fumes · · Score: 2, Interesting
    Did anyone read the last discussion about this? I thought it was pretty well established that Ogg Vorbis/Theora has no business being defined as the standard for anything, for the following reasons:
    • It's comparable to H.261 in performance
    • No one actually knows what the patent status is
    • No one even uses Theora for anything
    • Other containers and encoding formats are better and more popular and open, like x264
    • Why do we need video requirements for text markup?
    1. Re:Ummmm..... by Sloppy · · Score: 2, Insightful

      No one actually knows what the patent status is

      No one actually knows what the patent status of any codec is. More generally, it is virtually impossible to write any computer program longer than "hello world" and be sure it doesn't infringe on someone's patent.

      What we do know, though, is an attempt has been made to find patents that Vorbis infringes, and that attempt came up with nothing. Furthermore, Vorbis has been deployed and used for many years now, and no one has sued. As for Theora, it is known to use some patents (with permission), and it's been out a few years too, without those patents being contested, or On2 getting sued. Yes, a submarine could still come up, but all codecs share that risk.

      That isn't to say Theora is a good codec (though Vorbis sure as hell is), but the patent argument doesn't work.

      Why do we need video requirements for text markup?

      We don't, but there should be standards for multimedia, since we already have stuff like IMG and EMBED and those things just aren't going to go away. Right now, we have an absolute travesty for video embedded on web pages (nearly a worst-case scenario), where multimedia is being played by Flash plugins! The user has absolutely no control over playback software and its capabilities.

      Imagine if embedded video were handled the way embedded images are, where the user agent developer could add features, remove annoyances, hand it off to the OS' data type, whatever. Oh, and imagine if user agent developers could fix security holes, instead of having to wait for Adobe. Flash must die, and multimedia standards for web-embedded content would be a great bag of nails for the accursed coffin.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:Ummmm..... by evilviper · · Score: 2, Informative

      It's comparable to H.261 in performance

      That's only according to some guy from Nokia, who clearly has a massive bias.

      No one actually knows what the patent status is

      On2 had sold VP3 licenses for years, as well as for newer versions (VP4/5/6/7) based on many of the same methods as VP3. Those codecs have long been licensed, and widely used by very large companies like AOL (Nullsoft TV, AIM Video), Macromedia, Adobe (Flash v7), BBC (QuickLink field broadcasts), eBay (Skype Video), and no doubt many many more. The fact that no patent trolls have come out of the woodwork yet is pretty damn strong evidence that Theora is in the clear.

      No one even uses Theora for anything

      That's pretty much how all video codecs start out... Theora is still in beta, yet there is quite a bit of content from sites such as http://v2v.cc/

      Why do we need video requirements for text markup?

      For the same reason we need image requirements for text markup. In fact HTML already has a specified video format: raw MJPEG, it just happens to suck.

      I long wished MPEG-1 had been specified for web video (to supersede MJPEG) when it's patents had first expired, but it never happened, no doubt because some many companies have vested interests in getting those patent license fees.

      Dolby Labs does the same thing whenever a video standard is being defined... they throw a good amount of money in bribes around, and make sure the standards (in all those countries that have software patents) include only Dolby, despite MP2/Musicam being as good, and trivially easy to include as an alternative. So while our European friends can put free MP2 audio on their DVDs, and in their DTV broadcasts, in the US we are absolutely required to have a Dolby Digital/AC3 audio track.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  16. Patent FUD at fault. by Anonymous Coward · · Score: 2, Informative

    The actual removal can be found here.

    "we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies."

    The sad thing is that Ogg/Theora is strong on all these points, and it's probably the only somewhat modern codec set that even comes close. Theora might not be state of the art, but it is orders of magnitude better 1980s tech that someone might propose as an alternative (and Vorbis clearly is a state of the art design).

    Meanwhile the MPEG LA licensed codecs that Apple and Nokia are advocating have already landed several *licensees* in court for patent litigation, with two major cases ongoing. In particular the MPEG LA license agreement is quite specific that the license does not provide all the patents needed to implement the covered codecs. Some of the lawsuits have even been from members of the pool (such as Lucent), so paying up provides you with little protection from attack from the pool members, no zero protection from patent attacks by third parties.

    Theora and Vorbis were designed to be free of serious patent problems. That doesn't mean that they are completely immune, *nothing can be* in our current patent climate. However, they should do better than their proprietary competitors... and the track record shows that.

  17. The actual mail on the HTML-wg mailing list... by Anonymous Coward · · Score: 5, Informative

    Just to point out what it currently happening, here is the mail from Ian Hickson from this morning:

    "I've temporarily removed the requirements on video codecs from the HTML5
    spec, since the current text isn't helping us come to a useful
    interoperable conclusion. When a codec is found that is mutually
    acceptable to all major parties I will update the spec to require that
    instead and then reply to all the pending feedback on video codecs.

        http://www.whatwg.org/issues/#graphics-video-codec
    "

    The title of the news is a bit misleading :) In other words "temporarily removed until a consensus has been found".

  18. Re:Microsoft, Google, Apple by odourpreventer · · Score: 4, Funny

    Google = Chaotic Neutral
    Apple = Lawful Evil
    Microsoft = Chaotic Evil

    Me = Nerd

  19. attention that mpeg4 guy by trybywrench · · Score: 4, Insightful

    In the last story about this there was a guy who made a really good comment about mpeg4 and how Ogg/Theora isn't actually that good for HTML5. He basically said that the video codec was patent encumbered but the company who owned it made it available to the public under a free nonrevocable license since it was DOA anyway when compared to mpeg4. see here:


    "Ogg's video codec is Theora, which was proprietary. On2 developed it as its closed competition to MPEG-4's H.263 (DivX) and H.264 (AVC) codecs, alongside other competing proprietary codecs from Real and Microsoft (WMV). The winner to shake out of all that competition has been the MPEG-4 standard, which includes both a container and different sets of codecs. MPEG-4 is open and supported by lots of companies, and is also supported by FOSS (x264 is among the best implementations)." - DECS


    I get the feeling that if people would actually sit down and look at the issue objectively then it would be obvious that Ogg/Theora being included in the HTML5 spec isn't that great of an idea. The problem is the Ogg crowd has a huge chip on their shoulder since no one has really given them the time of day. So, here's a chance for them to get some validation for all their hard work but they've been cut out yet again so everyone's all up in arms.

    --
    I came to the datacenter drunk with a fake ID, don't you want to be just like me?
    1. Re:attention that mpeg4 guy by squiggleslash · · Score: 3, Insightful

      MPEG4 is patent encumbered and does require license fees. While there may be patents for Ogg Theora, On2 has made it clear Theora is a genuinely open standard that doesn't require payment of royalties to them.

      MPEG4 is only open in certain senses. It is not usable from the point of view of a web standardization body, given the dependence the web has on the free software world.

      BTW, DECS runs the supremely awful "RoughlyDrafted" website, a kind of brain damaged Apple advocacy thing. I'd take anything he writes with a pinch of salt.

      --
      You are not alone. This is not normal. None of this is normal.
    2. Re:attention that mpeg4 guy by cheater512 · · Score: 2, Insightful

      I agree with your intentions but if Mozilla implemented MPEG 4 or x264 then they would immediately have a dozen lawsuits from different companies.

      Not exactly desirable. With Theora there isnt that problem.

  20. Patent expired techniques by starseeker · · Score: 2, Insightful

    Oddities of writing style aside (and possible DRM agenda nonwithstanding) I actually thought the idea suggested in the original Nokia paper to use older techniques that are or will very soon be based on expired patents was a pretty good one.

    Whatever we may want to think, it is true that someone COULD challenge Ogg Vorbis on patent grounds, valid or not. A technique 20 years old and based on expired patents is absolutely unambiguous - the patent office itself is the documentation that the technique is now unrestricted.

    For most of what is done on the web the older technologies would work just fine. They are also mainstream, which means they stand a better chance of being used. The HTML standards process is not strong enough to push forward Ogg Vorbis, IMO.

    Remember, this is big corporate lawyer turf here. Ogg Vorbis is thought to be free of patent claims but there is no way to prove that. Expired patents are the safest possible way to proceed.

    --
    "I object to doing things that computers can do." -- Olin Shivers, lispers.org
  21. Re:Pragmatism vs. Ideallism by Cyberax · · Score: 2, Insightful

    Ogg Theora sucks but Ogg Vorbis and Speex are, arguably, the best codecs for audio.

  22. Maybe it's just me.. by devjj · · Score: 2, Insightful

    I'd rather have a spec that clearly defines how content is embedded, rather than what content to embed. Specifying a particular format reduces freedom. There's nothing to say you can't use Ogg. The only benefit to having Ogg in the spec itself would be to get the format more well-known, but that should happen on its merits, not because a standards body decreed it so. What is unfortunate in this instance is just how much sway a single company or pair of companies can have over a spec as a whole, and how quickly they can make changes happen. It just smacks of impropriety. I don't think anyone's going to argue that H.264 is a bad codec, but isn't the point of a standard to ensure interoperability? Why do these companies have so much clout?

  23. This is why zeal matters by mlwmohawk · · Score: 3, Insightful

    I am so sick and tired of people saying silly things like "Its only an operating system," or "use what's best," or other justifications for taking crap that we MUST STAND UP AGAINST.

    Every little one of these things matters, they all add up like links in a chain. There are people actively trying to destroy freedom and they are doing it slowly with incremental steps. This is just another step. I'm sorry, if you can't be bothered to take an active participation in protesting and exploring alternate systems, then you are letting everyone down. You know the expression: "No one snow flake in an avalanche feels any responsibility."

    The *big* picture is democracy itself. Once the information is controlled, the people are controlled. Make no mistake, people are actively working against the free exchange of information. While most are just working for their own self interests, there are others capitalizing on these actions in more nefarious ways.

    I know you think this is tin foil hat stuff, but look around, look at what's happening. We have to work against these sorts of things because rust never sleeps.

  24. Huh? by IgnoramusMaximus · · Score: 4, Insightful

    I have news for you: HTML is a format!

    By being half-assed and not specifying a standard for a widely used aspect of the web browsing experience, what is in effect happening is a de-facto endorsement of all of those pet proprietary formats at the expense of clarity and allowing the various companies to rape the public with a million of buggy plug-ins, each with its own flavour of the week. The very anathema of a "standard".

    It does not matter if Ogg/Theora were not the most advanced and efficient of technologies as neither is the whole concept of HTML. What mattered was estabilishment of an open standard which would cut down on the chaos of inane plug-ins and made it impossible for companies like CNN to purposefully block all web browsers other then IE from accessing their video contents, as is the case now.

    1. Re:Huh? by Ignorant+Aardvark · · Score: 3, Insightful

      Have you quite finished? Geez, it's a wonder multimedia-based services like YouTube even work on... just about every browser on the planet.

      YouTube works? Are you joking? Firefox crashes on me every time I view a YouTube video thanks to the wonderfully crappy proprietary, closed source Flash plugin for Firefox on GNU/Linux. It doesn't work at all. Using Ogg/Theora in a video tag, on the other hand, would work perfectly.

      Closed source solutions like Flash aren't solutions at all. Flash isn't even a video format. It's an animated vector format that's been used as a hack to deliver raster video. It's far from the ideal solution; the only reason it was ever used is because it is relatively widespread. "Relatively." There's still a good number of us who are left out in the cold.

    2. Re:Huh? by IgnoramusMaximus · · Score: 4, Insightful

      Have you quite finished? Geez, it's a wonder multimedia-based services like YouTube even work on... just about every browser on the planet.

      No, they don't. Try a 64-bit Linux, any distro, amongst many other examples. And no, writing entire 32-bit emulator plugins so that the stupidity which is Flash can run in them does not constitute "working" anymore than running VMWare makes Autocad work on Linux.

      The Web-using public has proven itself quite capable of adopting new technologies that serve their purposes, and working on the basis of popular de facto standards. If any proprietary technology ceases to serve the needs of the Web-browsing public, that technology will most likely be replaced in fairly short order by another that does serve the public need. This sort of thing has been happening since the dawn of browsers and the old IE vs. Netscape browser wars.

      Bullshit. The "web-using public's" 95%+ membership is comprised of people who would upon seeing "this website needs the The Up-Your-Ass Shit-o-Matic Plugin to Enhance Your Experience" would go "Duh, I better click OK!".

      Quality or needs of the public have nothing to do with any of it. Needs of the various idiots attempting to control the public via means such as Flash-only sites have everything to do with it. That is why the public is not involved in protesting Ogg, corporations are.

      There are advantages to having a truly open standard, but for something that evolves as fast as the Web, we've seen time and again that de facto standards that are technically sensible and practically useful are way more valuable than any formal document produced by a standards body.

      More bullshit. If it weren't for open standards, the only "web" browser in existence would browse Microsoft "enhanced" HTML. The de-facto, secret, proprietary, patent-encumbered standards, with players available for only a small fraction of platforms are not "sensible" in any way, shape or form.

      This whole discussion sounds a lot like people who like a relatively unpopular format bitching because they were hoping their preference would be forced on the rest of the world based on politics rather than technical merit, and they lost the argument.

      Politics? Your entire argument can be summarized as "Everyone should use IE and commercial plugins on either Windows (or possibly, grudgingly, Mac)! Everyone who doesn't is a bitter, unpopular political loser!"

  25. FUD FUD FUD by a+known+emus · · Score: 5, Informative
    This is a point by point reply to your FUD.
    • Theora is almost an order of magnitude better performing that H.261 and this is a critical difference for web video.
    • No one actually knows what the patent status of any software is! ... In fact, several paid up licensees of mpeg codecs have been sued for patent infringement over these codecs *and lost*, so it's hard to argue that those codecs are better off.
    • It's true that Theora isn't very widely adopted, but it has been shipped by Linux distributions for years, so there has been plenty of opportunities for people to sue over patents. Theora is used by Wikipedia, one of the most viewed websites in the world. Of course, Vorbis is orders of magnitude better on this point.
    • What are you Nokia? An expensive and heavily patented codec like H.264 is not "open" in any meaningful sense. It's true that Ogg/Theora+Vorbis is not yet amazingly popular, but that is part of the point of standards. There is a chicken and egg, and first-mover takes all problem for file formats and standards help fix that problem.
    • Why does HTML have an image tag? What would the world be like if images on the web required various incompatible proprietary plugins? Why should video and audio be any different from still media?
    1. Re:FUD FUD FUD by Just+Some+Guy · · Score: 4, Informative

      And countering yours:

      • From it's inventor:

        Unlike Vorbis and Speex, legitimate best-in-class codecs, Theora's coding quality is obviously poor relative to contemporary competition. This poor performance stems both from implementation and design deficiencies. As a seperate problem, Theora is also poorly integrated with Ogg due to incomplete multiplexing software and documentation on the Ogg side. Without guidance from Xiph.Org, outside development and implementation of Theora-in-Ogg has been chaotic and of low quality.
      • It's safe to say that MPEG4 and it's codecs have been more thoroughly researched than Theora. Remember the FOSS mantra: "many eyes make all bugs shallow"? That applies to lots of things, such as many video producers' legal teams checking this stuff out.
      • I absolutely, positively promise you that Youtube serves more video than Wikipedia, and they don't stream Theora.
      • You're imagining that Theora is equivalent to H.264, etc. It's not. There's no first-mover advantage to it because it's already been overtaken by, well, pretty much everything.
      • There's no standard web image format. By convention, most people use GIF and JPG (with a few PNGs sprinkled about for good measure), but that's just the way it happened to work out. I'm not sure why people have this wrong impression, but it's simply not true. Don't believe me? Read the spec yourself. If that isn't clear enough, W3 explicitly states that

        The HTML specification does not prescribe or limit which graphics format you can use.

      I'm a huge FOSS buff, but that doesn't mean I have to blindly love everything pushed out the door as "freedom friendly". I don't have anything against Theora except that it's just not very competitive. I wouldn't want to see it as the official video file format any more than I'd want to see ASCII text as the official document file format; both have clear limitations when compared to their competitors.

      The W3 made the right choice. As much as I like the idea of Theora, I'm glad we don't have to be saddled with the reality of it.

      --
      Dewey, what part of this looks like authorities should be involved?
  26. Ogg/Theora only poor against impossible options. by a+known+emus · · Score: 4, Insightful

    It's true that H.264 is better than Theora. But H.264 has zero chance of being made the baseline because it is expensive as hell and certainly not free as the W3C requires.

    Theora is substantially better than any other codec which has a chance of being included. As such it's silly to say that Theora shouldn't be used because it isn't the best... thats a bit like saying "I won't drive any car but a Ferrari" when all you can afford is a used Ford Escort.

    Obviously most implementations will also include a better codec than Theora, but Theora is a generally respectable codec at web streaming bitrates and it will provide a viable option for those who can't or won't pay the licensing fees for better codecs. In other words, Theora will be a reasonable baseline which is all it's supposted to be in this context.

    Furthermore, the inclusion of Theora will also help keep the licensing costs down for better codecs. Everyone Wins, except companies that make money licensing codecs... and in the long run they'll probably win too, since web video that Just Works will increase the popularity of web video.

  27. Re:mod parent up. by Bogtha · · Score: 2, Informative

    What about standards for video and audio rendering? Why don't these exist?

    They do. However having standard codecs and attempting to tie together formats that are orthogonal in nature are two separate matters. The <video> element type works regardless of the video codec in use, so the HTML specification attaching itself to one particular codec is unnecessary.

    --
    Bogtha Bogtha Bogtha
  28. what a horrible summary by YesIAmAScript · · Score: 2, Interesting

    Wrong icon and everything!

    "Widely available patent-free implementations of Ogg".

    First, saying "Ogg" means Ogg Vorbis to most people. This is about Ogg Theora.
    Second, whether something is patent free is not determined by the implementation. You're thinking of copyright!

    Ogg Theora uses patented technology. We don't want to enter into a Rambus-type situation where once something becomes popular a company can come back and start dinging people for money.

    And the icon doesn't make sense. This isn't about trying to patent existing or trivial things, it's about whether a standard should make mandatory a patented codec that isn't even widely used.

    --
    http://lkml.org/lkml/2005/8/20/95
  29. Consensus will never be found by Wesley+Felter · · Score: 2, Insightful

    So Ogg will never make it back into the HTML5 spec.

  30. Mod parent up! by AusIV · · Score: 2, Insightful

    As much as I'd like to see OGG gain momentum over proprietary formats, I think specifying a format is beyond the scope of HTML. If being HTML compliant meant that you had to use Theora and Vorbis for video and audio respectively, I could see that somewhat stifling innovation. If someone comes up with a new concept for delivering web based video or audio more efficiently than can be done with OGG, they'd have to disregard HTML standards in order to implement it. This means that either the standard largely gets ignored, or people forgo progress in favor of the standard.

  31. Re:mod parent up. by Bogtha · · Score: 2, Insightful

    MPEG is commercial and contains patents

    MPEG is the name of a working group. Some of the formats they have standardised contain patented technology. It's not accurate to say "MPEG contains patents".

    so has the same issue as including any other patented technology

    In Hickson explained Apple's situation quite well:

    Certain companies (Nokia and Apple among them) have reported that they still fear that undisclosed patents may exist that cover the relevant codecs, as they might exist for other formats like MPEG4/H.264. The difference is that while Apple (for example) have already assumed the risk of submarine patents with H.264, they currently have taken no risks with respect to the aforementioned codecs, and they do not wish to take on that risk. Given the extremely large sums of money that are awarded for patent violations (cf. Microsoft's recent settlements), it is understandable that companies with the high profile of Apple and Nokia would not wish to take on such risks.

    While many codecs are patent-encumbered, it doesn't necessarily follow that it is equally risky to implement them for any particular organisation.

    HTML doesn't want to use patented tech

    HTML hates anthropomorphism.

    Nobody is saying that the HTML 5 specification should recommend a patented codec. They are saying that it shouldn't recommend any particular codec.

    gif was free until UNISYS bought Compuserv and started enforcing Lev-Zempel and jpeg was free until a patent troll bought a related patent.

    No, they were always patent-encumbered, it's just that people didn't know about it until UNISYS started cracking down on infringers.

    I can see Apple wanting to fight ogg-vorbis, as they have a heavy investment in AAC and Quicktime and I'm sure they would rather see that tech in.

    I'm sure they would, but this isn't about picking Quicktime over Ogg. You can't win this argument by saying how bad Quicktime, MPEG or anything else might be, because the alternative people are proposing is no recommendation, not a recommendation for competing formats.

    --
    Bogtha Bogtha Bogtha
  32. Re:mod parent up. by Bogtha · · Score: 2, Insightful

    But again, just like images, there should be "standard" content formats to fall back on for maximal compatibility.

    I don't know where this myth arose that previous versions of HTML specified "standard" image formats, but it's just not true. Read the specifications yourself.

    Not specifying any particular video codec for <video> is exactly the same as how images were handled. Including a recommendation for Theora is a change from how images were handled.

    --
    Bogtha Bogtha Bogtha
  33. OT: Possible Linux Firefox/Flash Crash Workaround by beej · · Score: 2, Informative

    Firefox crashes on me every time I view a YouTube video thanks to the wonderfully crappy proprietary, closed source Flash plugin for Firefox on GNU/Linux.
    Hey--I used to have a problem where Firefox (tried many versions) under Linux (Slackware 12) would hang consistently after viewing a flash movie (tried many plugin versions) then starting to view a second one. I suspected it had something to do with the audio, I found after tracing with gdb, and seeing how non-audio flash pieces didn't crash it.

    Turns out that if I start up xmms or audacious on some mp3, then hit pause (has to be pause--not stop) or just let it play, then I can view flash movies to my heart's content without a crash.

    It's a kludge, but maybe with a little luck it works for you.

  34. Re:mod parent up. by Sancho · · Score: 4, Informative

    100% correct.

    I liked the idea of OGG being recommended for HTML5, but realistically, there are a lot of problems.

    As a container, OGG is pretty heavyweight. It's not going to be good for mobile devices.
    All off the Vorbis and Theora decoders I've seen have been extremely resource-intensive. This may well be because more attention is devoted to other codecs like XVid, and so they are more highly optimized. Nevertheless, again, mobile devices will suffer.
    Quality-wise, Vorbis is pretty nice. Theora, however, is a generation behind, and rapidly losing ground. HTML5 isn't expected to be ratified for over a year. In that time, Theora's generation of codecs will be even older and less efficient to the then-current codecs. For a field as rapidly evolving as streaming video, it doesn't make all that much sense to include it. It would be like suggesting that Indeo be implemented for HTML4.

    The biggest benefit to recommending OGG in HTML5 is that it would get a free format out there, but at the cost of efficiency. While bandwidth continues to grow, and computers get faster and faster, waste is still a concern, and mobile devices are becoming more popular (you have to treat these as if they were 10 year old computers with equivalent bandwidth!) OGG misses the mark in most categories--too big and bulky for mobiles, too old for new computers. It's the worst of both worlds.

  35. Yeah, that's FUD by xiphmont · · Score: 4, Interesting

    Hi. I'm the 'inventor' (not really, On2 originally wrote vp3 and we're riffing from there. I'm the hacker working on it now).

    1) That is in comparison to h264. And I call it 'embarrassing' because Theora *could* easily be just as good, but it isn't right now. That document is a call to arms and because of it, a new encoder is rapidly taking shape. Its improvements are already making it back to mainline. We'll catch up rapidly.

    2) "It's safe to say that MPEG4 and it's codecs have been more thoroughly researched than Theora" Bullshit. MPEG is simultaneously inefficient and narrow in their focus. MPEG-4 / h.264 is a decades old chassis with a few recent research papers tacked on. _Several of the items I identified as 'embarrassing' and 'obsolete' ironically apply to MPEG-4 too_.

    3) "I absolutely, positively promise you that Youtube serves more video than Wikipedia, and they don't stream Theora." Irrelevant. This is an argument against Google (Altavista dwarfed them), Microsoft (IBM and even Apple dwarfed them), Toyota (GM dwarfed them), etc.

    "As much as I like the idea of Theora, I'm glad we don't have to be saddled with the reality of it."

    Why does everyone here think this is a battle of individuals? These are huge multinationals and your puny insignificant selves don't even appear on their radars. Sure, the public will indeedy benefit from a standard multimedia codec set with no proprietary/encumbered strings attached, but that is entirely irrelevant in the process of making money. They're *for profit corporations* doing what for-profit corporations do. Making money. And that is entirely orthogonal to morals, public good, or even competent engineering. They don't have any interest whatsoever in what you think.

    Although we're a non-profit (and exist on behalf of the common good), our argument in this battle happens to concern rallying all the sub-$100M companies that will be frozen out by the very biggest players getting their way. When big companies win, little companies generally lose. Although the little compaines greatly out-mass the big companies, they tend to be fragmented. If we can get them all together to fight for a uniform technology recommendation, way more people win.

    But you might want to run for cover, 'cause Godzilla has his squishin' boots on.

    1. Re:Yeah, that's FUD by xiphmont · · Score: 2, Informative

      "That didn't come across so well in the presentation. That is the qualification wasn't apparent - it sounded like you were saying it was bad, period."

      That document was an internal identification of weak areas. It was intended to be 100% critical. We don't need to keep telling ourselves within Xiph and RedHat etc what's good about it.

      "But the legal teams of every major corporation that wants to use it [MPEG]? I imagine Sony's given it a look or two along the way. Just as an example."

      Sony is a bad example as they've attempted to undermine MPEG with a number of spectacularly ineffective market fragmentation tactics. However, the major supporters of MPEG tend to be MPEG themselves. Those who use MPEG want to avoid Microsoft. Real is widely perceived to be dying. We're considered a risk, mainly because MPEG says so. There are no other options left.

      "Honestly, I wish you well - we're on the same side!"

      np. I just don't deal in weasel-words is all...

      "but I respectfully disagree that Theora's ready to be standardized right now today."

      Not true. It's been mature/ready for a very long time. VP3 is actually slightly older than Vorbis. It fills its niche perfectly ; its theoretical performance, which we're closing in on, is very good compared to how much more 'modern' (but much heavier) codecs perform today, and it does it at a fraction of the complexity. It's perfect for lightweight implementations and ideal for the tag.

  36. Re:The two commercial interests should be sued by onefriedrice · · Score: 2, Insightful

    You seem to be living in a dreamland of some sort. I'll try to help you out.

    > It goes beyond "FUD" to simply label some technology as proprietary when it is not.

    I'm not sure exactly what you're referring to, but many people (perhaps you too) assume that Ogg Theora is patent-free, so let's go over this again: Ogg Theora (specifically the Theora part) is _not_ patent-free for the bazillionth time.

    > What Apple and Nokia have done is damage to the future development of the public internet through blatant lies.

    Actually, what they have done is prevent a specific video codec from becoming a requirement in a markup language standard, thus maintaining free competition for all codecs and allowing them to compete on their own merits. Whatever their motives are, this seems like a good idea to me.

    > I'm not sure how it would be defined legally, but fraud is a word that comes to mind.

    Fraud? Unlikely. It seems you should get a clue before you post nonsense that people might believe. It seems many Ogg users are disgruntled that their pet codec won't get a free pass. Vent your frustrations on a pillow. It helps. The current HTML standard has no image or media requirements and the internet works just fine. Video codec requirements have no place in a markup language specification. It would be just as bad if Apple/Nokia successfully push their own pet codecs into the standard (which hasn't happened yet), but as it is now there is no use throwing a tissy fit over Ogg Theora being rejected where it also doesn't belong.

    --
    This author takes full ownership and responsibility for the unpopular opinions outlined above.
  37. Re:mod parent up. by Windom+Earle · · Score: 2, Insightful

    because the alternative people are proposing is no recommendation, not a recommendation for competing formats.

    'people' is a funny way of referencing several rather loud business organizations. You make it sound like 'the people have been heard on the subject' or something.

    Further, you're correct that Apple and Nokia want no standard. They'd rather have the freedom to troll around in the chaos.

    It's disconcerting how many people have barely hidden partisan points of view favoring commercial outfits in these discussions. It's as if shilling was an acceptable part of geek/nerd culture. However, it is not.

  38. Re:Ogg/Theora only poor against impossible options by evilviper · · Score: 2, Informative

    The only real candidate that I'm aware of is H.261, which takes roughly 10x the bandwidth of Theora to deliver anything close to the same quality at typical web streaming sizes.

    First off, MPEG-1 is no longer patent restricted, and is newer and better than h.261.

    Second, 10X is clearly a made-up number. Through the past 20+ years of lossy video compression, there hasn't been an order of magnitude improvement in compression at all. And even if there had been such an improvement, Theora certainly wouldn't be the codec in a position to do it, as it's pretty poor quality. If you're really seeing that huge of a difference, you're doing something HORRIBLY wrong.

    I have tried h.261 even though support for it is pretty flaky, and I use MPEG-1 EXTENSIVELY today (on SVCDs and DVDs, in lieu of MPEG-2). I've got a video encoding to MPEG-1 right now... I would put libavcodec's MPEG-1 up against Theora any day. If nothing else, the quality is quite close, and MPEG-1 requires a tiny fraction of the CPU power to encoder or decode.
    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant