Slashdot Mirror


Wikipedia's Assault On Patent-Encumbered Codecs

An anonymous reader writes "The Open Video Alliance is launching a campaign today called Let's Get Video on Wikipedia, asking people to create and post videos to Wikipedia articles. (Good, encyclopedia-style videos only!) Because all video must be in patent-free codecs (theora for now), this will make Wikipedia by far the most likely site for an average internet user to have a truly free and open video experience. The campaign seeks to 'strike a blow for freedom' against a wave of h.264 adoption in otherwise open HTML5 video implementations."

428 comments

  1. HTML5 Video by sopssa · · Score: 4, Insightful

    It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

    However it's nice to see Open Video Alliance trying to partner with Wikipedia. In addition to being technically better, that's another aspect you need to take care of. You need to make sure websites, TV, phone, computer and so on manufacturers support your technology. You have to work with them to get it supported - not just put it out there and hope it catches up because its "open", because that's not going to happen. Personally I would also hate to see technically inferior solution being used, as it would eat huge amount of bandwidth. Theora just isn't on the same table with H.264 for Internet video. Theora is based on VP5 from On2 and now that Google acquired them, they're going at VP8.

    As far as having a single standard for HTML5 video goes, Theora lost. H.264 is and has been already everywhere and on every device. I also suspect majority of sites will use H.264, as that's what is being used with Flash already.

    However, what I see happening (and hope) is HTML5 Video tag being released without requiring support for a single codec, just like img tag is. Then browsers can either implement their own support, use third party tool like gstreamer (like Opera does) or just depend on OS (what I suspect IE and Safari will do). Firefox is still having their ideological problems, but I'm pretty sure they will start using gstreamer too.

    What I'm more worried about is that I cannot watch Wikipedia videos with any other device than my PC. Want to see a video clip of a place you're traveling on your phone? Not possible. Want to see videos from Wikipedia with your PS3/360? Not possible. It will create some serious problems, and I don't think Wikipedia is big enough to push the change alone.

    1. Re:HTML5 Video by Anonymous Coward · · Score: 3, Insightful

      Open video bitstream formats, like Theora, are simply not capable of being better than H.264 (yet). The best bet in that regard is Dirac by the BBC, but even that does not fare too well against H.264 as encoded by x264.

      However, open video formats simply do not need to be better than the proprietary formats, they simply need to be "good-enough" and be ubiquitous on the web, and pretty soon all browsers (except IE, probably) will support them out of the box. Wikipedia going with theora is a good move in that direction.

    2. Re:HTML5 Video by linhares · · Score: 2, Interesting

      It's all nice and all, but if open video technology really wants to win, they have to be technically better.

      New here?

    3. Re:HTML5 Video by FlyingBishop · · Score: 1

      As far as having a single standard for HTML5 video goes, Theora lost.

      As far as I can see there's only one website I care about that relies on HTML5 video, and it uses Theora.

      Actually, I'd challenge you to point to any website that only offers H.264 served via the video tag. Yeah, they're all running Flash (which is closer to H.264) but saying that Theora has 'lost' when hardly anyone supports H.264 is just bullshit.

    4. Re:HTML5 Video by kickme_hax0r · · Score: 2, Informative
    5. Re:HTML5 Video by Lunix+Nutcase · · Score: 2, Informative

      Yeah, they're all running Flash (which is closer to H.264)

      What do you mean "closer to"? Flash has been using H.264 in MP4 for quite some time now.

    6. Re:HTML5 Video by Xtifr · · Score: 5, Insightful

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      Why? Closed formats don't seem to operate under that constraint. In fact, technical qualities seem to be a non-issue as far as success goes in general. The backing of big players seems to be what counts, and that's exactly what we have here. Whether Wikipedia + Firefox + RedHat + other open players is big enough remains to be seen (and I admit I have my doubts), but if "technically better" becomes an issue, I think it'll be the first time ever.

      What I'm more worried about is that I cannot watch Wikipedia videos with any other device than my PC

      Ah, now your real concern appears, I suspect. If Theora starts to get momentum, it'll appear on phones and similar devices quickly enough. My phone already supports Ogg Vorbis. (It may even support Theora; I haven't tried.) If yours doesn't, then perhaps you went with the wrong vendor. I didn't look for Vorbis support for my phone, but I did look for openness; if that wasn't a factor in your choice of phone, then my sympathy for you is nil. Especially if you want to connect with Wikipedia, whose commitment to openness is legendary.

      If you want Wikipedia to go with your proprietary, encumbered format(s), your best be is to lobby the patent holders to donate the patents to the public domain. Good luck with that. :)

    7. Re:HTML5 Video by sopssa · · Score: 1

      As much as I hate it, Direc is also inferior to H.264. Not only technically, but support of it sucks and it has seeking problems (at least with the currently available players, where it sometimes takes many seconds after a seek to playback again).

      What is most interesting though is what Google will do with On2 - they're the only ones that could completely change the game.

    8. Re:HTML5 Video by Dan667 · · Score: 1

      better technology is not the measure if it will succeed. All you have to do is to look at the wreckage of all the better standards that fell by the way side over the years to understand that.

    9. Re:HTML5 Video by sopssa · · Score: 1

      YouTube uses only H.264 with HTML5 video tag, and Flash directly uses H.264 as it's HD codec. I really doubt YouTube will change from H.264 anyway, as it's currently serving both Flash and HTML5 users and is easier on bandwidth.

    10. Re:HTML5 Video by Anonymous Coward · · Score: 5, Interesting

      What I'm more worried about is that I cannot watch Wikipedia videos with any other device than my PC. Want to see a video clip of a place you're traveling on your phone? Not possible. Want to see videos from Wikipedia with your PS3/360? Not possible. It will create some serious problems, and I don't think Wikipedia is big enough to push the change alone.

      In general I find the "must have hardware support now" argument a bit short sighted. By that reasoning there would never be any change in video codecs. In any case, the PS3 and 360 even combined represent a very small percentage of internet connected devices. And the 360's larger problem is not having a web browser so Wikipedia video would be streamed from your PC anyway and if needs must you can transcode on the fly.

      As mobile phones go, my Nokia N900 plays Theora. It also runs Firefox. Fennec is on Maemo 5 (the N900's OS) and will soon be available for Android, Windows Mobile, and future MeeGo devices. Millions of devices in the field already have the capability to play Ogg Theora and it will only become more trivial to do so with Firefox releases for those platforms.

    11. Re:HTML5 Video by Yvan256 · · Score: 1

      I wouldn't call YouTube "hardly anyone".

    12. Re:HTML5 Video by Lunix+Nutcase · · Score: 4, Insightful

      But why should the average user be quite in some stupid ideological fight when they are never going to be paying for the H.264 royalties that Microsoft, Apple and Google will be shelling out to include H.264 support in their browser?

    13. Re:HTML5 Video by sopssa · · Score: 1

      You would be surprised how many actually use their PS3 to watch videos online. It's far from very small percentage (and I understand why, it's really convenient).

    14. Re:HTML5 Video by DragonWriter · · Score: 4, Insightful

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      For any definition of "technically better" where this is not a vacuous tautology (that is, any definition other than "technically better means whatever ends up winning"), this isn't true: solutions that aren't "technically better" by almost any definition you choose will win all the time, because the business model behind selling them allows them to be sold cheaper (even if they aren't any cheaper to produce), because they are imposed by market-dominant players, or for all kinds of other reasons beside technical superiority.

      Compatibilty of patent-unencumbered formats with a venue like Wikipedia would be exactly that kind of non-technical factor. (As would, on the other side, the competitive advantage that those who co-own the patents see in the dominance of patent-encumbered formats that they are part of the controlling syndicate for.)

    15. Re:HTML5 Video by Anonymous Coward · · Score: 0

      You have to be one hell of an ideologue to not recognize how much better IE5 was than Netscape 4. Technical superiority isn't all it takes, once you're on top you can stay there by other means, but it's near-vital making your run up.

    16. Re:HTML5 Video by AliasMarlowe · · Score: 3, Insightful

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      Try telling that to Microsoft!
      Recall that Windows did not become the de facto standard OS by being better - it was definitely not better than the alternatives in the period in which it became dominant. So there is another way: gain sufficient market share through fair means or foul, and you can win. Whether wikipedia would count as critical mass or not is an open question, but if they were sufficiently bloodyminded, then whichever codec they chose to standardize on would ipso facto become a necessary codec, even if it were not used widely elsewhere.

      --
      Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    17. Re:HTML5 Video by Anonymous Coward · · Score: 1, Informative

      What? Flash Video is a CONTAINER format, not a video format. Most sites that use flv containers do so with h.264 video streams.

      Everything supports h.264 video. All of the modern mp3 players, phones and video game consoles do. Most software media players and video editors also support h.264 right out of the box.

      To be honest, it doesn't sound like you know what you are talking about.

    18. Re:HTML5 Video by MobyDisk · · Score: 1

      Is there any way to specify multiple formats? Ex: that points to H.264, but falls back to H.264 if that isn't supported?

    19. Re:HTML5 Video by sopssa · · Score: 1

      I do agree with the first point. It takes both backing of big players (hence support, as I addressed in the first post) and being technically capable.

      As far as technical qualities come, closed formats do have competition there too. DivX (and it's open companion XviD) really did challenge MPEG-2. They were technically better and did gain momentum at least on the internet and even beyond that.

      But as this is about online video, it makes more sense to have the more-bandwidth-friendly H.264 than more-cpu-friendly Theora.

    20. Re:HTML5 Video by wealthychef · · Score: 4, Insightful

      The cost is still paid by the average user, it's just tacked onto the cost of the O/S or whatever you buy from Apple, MS, etc. As for "why", various consumers value different things. Some value cheap, some value fast, some value open source, some value high quality, etc. Ideally, customers who want choice can get it with a plugin, and the rest will get it easily without a plugin. But there will always be this creative edge. Most people will just say with safe, reasonably fast and easy.

      --
      Currently hooked on AMP
    21. Re:HTML5 Video by _KiTA_ · · Score: 0, Troll

      Open video bitstream formats, like Theora, are simply not capable of being better than H.264 (yet). The best bet in that regard is Dirac by the BBC, but even that does not fare too well against H.264 as encoded by x264.

      However, open video formats simply do not need to be better than the proprietary formats, they simply need to be "good-enough" and be ubiquitous on the web, and pretty soon all browsers (except IE, probably) will support them out of the box. Wikipedia going with theora is a good move in that direction.

      Except H.264 isn't better. It's slow, unwieldy, CPU intensive, and tends to fall over and shit itself with even the tiniest bit of corruption. There's a reason I avoid the H264 files on animesuki nowadays and go for the (technically lower quality) XVID files -- at least XVID works.

      This is a moot point anyway. It's just compression, how hard could it be? Lets get a sourceforge project going to make something better.

    22. Re:HTML5 Video by LWATCDR · · Score: 1

      Even that is questionable. No reason why the browsers can not just use the OS's installed codec system. In Windows DirectShow/X/Video or what ever they call it. Gstreamer in Linux, and Quicktime on the Mac.
      The browser will not have to pay diddley

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    23. Re:HTML5 Video by Anonymous Coward · · Score: 0

      As far as having a single standard for HTML5 video goes, Theora lost. H.264 is and has been already everywhere and on every device. I also suspect majority of sites will use H.264, as that's what is being used with Flash already.

      It's not about Theora versus H.264. It's about open, royalty-free video versus closed, proprietary video. The formats and protocols the web is built on are open and royalty-free. With HTML5 there's no need for video to be any different. The arguments against Theora based on quality and bandwidth have been debunked time and time again. If YouTube switched to Theora tomorrow for new uploads, no one would notice the difference on the basis of quality or bandwidth.

    24. Re:HTML5 Video by Anonymous Coward · · Score: 3, Insightful

      If they don't offer hardware acceleration in a mobile device, your begging for a huge battery drain. The point isn't only that they can play them, but that they are well supported by the device and that the impact isn't overly detrimental.

    25. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Wikipedia is much smaller than Apple (Safari, iPhone, iPod touch, iPad in a few weeks) + Google (Chrome, YouTube) + Microsoft (Windows, Xbox360, Zune). So, H.264 has already won over Theora. The Vorbis team woke up way too late to even have a fighting chance.

      And even though Google now owns VP8, the total users for Microsoft and Apple is still bigger than Google. If Google wants to replace H.264 with VP8, they have quite a fight on their hands too.

      As for the comparison to the img tag, it's different. JPEG and GIF are two formats targeted at different graphical content. The UniSys debacle saw PNG emerge as a replacement for GIF but at the same time added new features that GIF couldn't do: lossless 24-bit and a real alpha channel. Microsoft took forever to implement PNG correctly and it slowed down the adoption of PNG. But today all modern browsers support JPEG, GIF and PNG properly.

      What does Theora do that H.264 can't, aside from taking more bandwidth to get the same visual quality? Nothing.

      What if both H.264 and Theora become HTML5 video standards? You really think websites will start producing and storing video files in both formats? It takes time to encode a video and the resulting files aren't small by any means.

    26. Re:HTML5 Video by tagno25 · · Score: 1

      it is a very small percentage of the internet users (1%)

    27. Re:HTML5 Video by angelwolf71885 · · Score: 0

      Firefox supports ONLY Theora so yah Theora has already won the fight

    28. Re:HTML5 Video by slimjim8094 · · Score: 4, Interesting

      To be fair, the format is entirely open, but patent encumbered. Nobody would argue that MP3 is a closed format, for example.

      IOW the only challenges are legal challenges (regarding software patents and royalties). They're not proprietary at all.

      --
      I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
    29. Re:HTML5 Video by sopssa · · Score: 3, Informative

      The cost is still paid by the average user, it's just tacked onto the cost of the O/S or whatever you buy from Apple, MS, etc

      Assuming the latest amount of 1.9 billion internet users (and not even accounting those not using internet), the $5 million cap per license, and Windows market share of 98%:

      $0.002 per user.

      I just don't see so many people caring.

    30. Re:HTML5 Video by camcorder · · Score: 1

      Both Apple and Microsoft have patents in MPEG-LA AVC patent pool, so they don't pay royalties.

    31. Re:HTML5 Video by obarthelemy · · Score: 1

      I'm not so sure. Maybe "good enough" would be good enough ? Quality is just one feature. Free-ness and Open-ness are 2 other, quite important ones. I'm fairly sure most videos on the web and on PCs in general are not artistic in nature. Slightly lower quality for no cost and freedom to do whatever you want with them may still be a winning proposition.

      The main issue is network effects: supporting 1 video format is a no-brainer, supporting 2 of them...

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    32. Re:HTML5 Video by magus_melchior · · Score: 1

      1. "Significant percentage of PS3 users" != "significant percentage of internet-connected device users". Even if all of the PS3 users in the world use their console to watch online videos, they're still dwarfed by the number of people using PCs for the same purpose.

      2. You're missing the point that you can't judge a contender for a standard based on how many people use it. If that were the case, then the W3C would standardize on IE6 behavior for HTML5, CSS3, and Javascript, and ECMA/ISO would standardize on Microsoft Office (non-Open XML) documents. There's also the fact that, should the W3C choose Theora, Dirac, or something else other than H.264, there's nothing stopping Sony from patching PS3s to support the new standard. To suggest otherwise is, as GP mentioned, short-sighted.

      3. You mentioned elsewhere that if the W3C kept it codec-neutral, that would be fine. I would agree, except that we'd be back in the days of "this site requires IE 8.x or higher", and that would, in practice, run counter to the W3C's goal of a single standard for all browsers and sites.

      --
      "We are Microsoft. You shall be assimilated. Competition is futile."
    33. Re:HTML5 Video by Lunix+Nutcase · · Score: 1, Flamebait

      The cost is still paid by the average user, it's just tacked onto the cost of the O/S or whatever you buy from Apple, MS, etc.

      So they pay a fraction of a penny more? Oh noes! That's gonna break the bank!

    34. Re:HTML5 Video by Yvan256 · · Score: 1

      Hell, tell me where to send my 0.01$ to end all this non-sense and force HTML5 video to standardize on H.264

      They'll even make five times the profit by doing so.

    35. Re:HTML5 Video by Anonymous Coward · · Score: 0

      DivX (and it's open companion XviD) really did challenge MPEG-2.

      unsurprising, seeing as how XviD and DivX were implementations of MPEG-4 Part 2, the successor to MPEG-2...

    36. Re:HTML5 Video by Lunix+Nutcase · · Score: 1

      Both Apple and Microsoft have patents in MPEG-LA AVC patent pool, so they don't pay royalties.

      Being in the patent pool doesn't give you free access to all the other patents in the pool. They pay royalties just like anyone else though the bulk of the cost is usually covered by cross-licensing of patents.

    37. Re:HTML5 Video by Cryacin · · Score: 1

      Depends, are you the guy signing the cheque?

      --
      Science advances one funeral at a time- Max Planck
    38. Re:HTML5 Video by moderatorrater · · Score: 3, Insightful

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      Why? Closed formats don't seem to operate under that constraint.

      Because closed formats have a company or companies willing to push it for reasons other than technical superiority. Open source relies on a lot of people getting excited about something and pushing it in a more organic way, and for that to happen in a big way then the thing they're pushing has to be technically superior. Linux has gained momentum in its areas by being superior for developers and sysadmins who know what they're doing. Firefox gained momentum the same way. I can't think of an open source product that gained mainstream popularity without being technically superior.

      I didn't look for Vorbis support for my phone, but I did look for openness; if that wasn't a factor in your choice of phone, then my sympathy for you is nil

      So, only people who spend their valuable time and money getting an open phone instead of the iPhone are worthy of consideration in this debate? Like it or not, the iPhone's dominance isn't because of any media blitz or cult of Apple, it's because it came out in a market where it was by far the best choice and is still superior to any other smartphone I've seen.

      So, if you want to prioritize openness in your purchasing, that's fine. But this is about Wikipedia trying to influence the culture as a whole and the emerging standard, and to suggest that this process ignore the vast majority of people is at best naive and at worst extremely damaging to your own position.

    39. Re:HTML5 Video by Lunix+Nutcase · · Score: 1

      It's slow, unwieldy, CPU intensive

      One can play 720@24p videos on an old AMD XP series chip with ffmpeg and it's not even really the fastest H.264 decoder around.

      and tends to fall over and shit itself with even the tiniest bit of corruption.

      And your answer to this is something like XviD which is far worse at bitstream corruption? HAHAHAHAHAHAHAHAHA.

      This is a moot point anyway. It's just compression, how hard could it be? Lets get a sourceforge project going to make something better.

      Oh yes, it's just soooo simple. Sure, if you ignore all the complex things that go into actually building a audio/video codec with good compression efficiency. Is this ignoring the fact that it took codecs like DivX, XviD, x264 years and years to reach their current states of quality and efficiency?

    40. Re:HTML5 Video by Xtifr · · Score: 1

      As far as technical qualities go, MP3 is still king of audio, despite being the worst supported format out there, proprietary or otherwise. Also, VHS beat Betamax. If history teaches us anything, it's that technical qualities are, at best, a very minor factor in success.

      it makes more sense to have the more-bandwidth-friendly H.264

      Not for Wikipedia. Their license won't allow it, so for Wikipedia, the choices are between Theora, maybe Dirac, and no video at all.

    41. Re:HTML5 Video by icebraining · · Score: 2, Informative

      Gstreamer in Linux

      Illegal in the US...

    42. Re:HTML5 Video by sopssa · · Score: 1

      Yeah, that's what I meant.

    43. Re:HTML5 Video by Anonymous Coward · · Score: 1

      Right, because a software update can create a hardware Theora decoder *rolls his eyes*.

      A lot of people just don't get the problem and constraints on mobile devices here - it isn't just that the codec is technically inferior, meaning that it requires more processing and decoding than h.264, it is the availability of hardware decoders. H.264, even though it takes less power to decode, is ALREADY hard to do in software, most portable devices and even some non-portable rely on a hardware co-processor that just decodes h.264. AppleTV does this. As someone who has worked on video codecs and in writing video decoding and playback systems, I can tell you, the availability of hardware decoders cannot be understated.

      H.264 decoders are already everywhere, and so it isn't as simple as: Oh, well, we just send a software update and we can do decoding of Theora on it! For most equipment, this isn't possible, it would require a new revision of the hardware, and all previous revisions wouldn't have access to the Theora content. There's your problem. H.264 is already everywhere in hardware decoders, so do you think the industry is going to abandon a huge userbase on the HOPE that they'll make it up with new devices?

      Yeah, me neither.

    44. Re:HTML5 Video by Anonymous Coward · · Score: 0

      If Theora starts to get momentum, it'll appear on phones and similar devices quickly enough

      Don't bet on it. H.264 is implemented in hardware, apple and other dodad manufacturers are buying off the shelf logic when they make their gizmos. Most of these devices do not offer third party media players, probably CPU draining the battery being the major issue. All the major players went with H.264 because they can hand the decoding off to onboard processing. Unless a chip manufacturer adds your choice of codec, it simply will not appear in the mainstream devices. Don't expect apple and microsoft to go for anything open, the closed culture keeps free away. We have a start to freedom (within reason) with all the android devices coming out, alas, nokia's N900 and predecessors are going to be limited to geeks that know what they want and are prepared to stand by what they say.

    45. Re:HTML5 Video by sopssa · · Score: 1

      I don't think we'd be back to the "this site requires IE 8.x or higher" days. That really is something from early 2000 and accompanied problems that carried for recent years. But it has been changing now and IE9 looks to be supporting all the new things like Firefox/Opera/Chrome/Safari.

      Personally I think codec-neutral way is the best way. Because you know, otherwise it's going to be H.264.

    46. Re:HTML5 Video by gparent · · Score: 1

      QWERTY was technically better considering it didn't jam your typewriter.

    47. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Yes. See Mozilla's developer centre wiki page on using audio and video in Firefox.

    48. Re:HTML5 Video by sopssa · · Score: 1

      Recall that Windows did not become the de facto standard OS by being better - it was definitely not better than the alternatives in the period in which it became dominant.

      Are you comparing to '94 Linux? There's no way an casual user would got by with it. Linux is even still semi-hard for casual users, and it would had been hell back then. Windows however, even if it lacked what we now a days have, was superior. You really have to compare it to that days computers - they weren't nice.

    49. Re:HTML5 Video by jmorris42 · · Score: 1

      > You would be surprised how many actually use their PS3 to watch videos online.

      So? Sony could add support in a week worst case; the PS3 certainly has enough CPU+SPU grunt to handle pretty much any codec you care to throw at it. Chicken and the egg here, Sony won't do it without demand and there won't be demand without must have content. Wikipedia is trying to crack that problem. If Google would help with YouTube we could bury h264 this year and never be troubled with those patent trolls again.

      And I freely admit Theora is sub standard, but it is a desperate fight to keep the Internet free of the patent trolls and Theora happens to be 'the only ship in the sector' right now. If we can get it through certain people's thick skulls that a patent encumbered format isn't acceptable we will eventually get a good one that is free. A lot of people want to use video over the Internet and the providers have big enough bandwidth bills they will be motivated to find bandwidth efficiencies.

      --
      Democrat delenda est
    50. Re:HTML5 Video by Anonymous Coward · · Score: 0

      I'm fairly sure most videos on the web and on PCs in general are porn.

      FTFY. HTH. HAND.

    51. Re:HTML5 Video by icebraining · · Score: 1

      They're not, especially as most Wikipedia content is text and images, not videos.

    52. Re:HTML5 Video by Xtifr · · Score: 3, Informative

      To be fair, the format is entirely open, but patent encumbered.

      A bit of an oxymoron there, but I know what you mean. The technical specifications are open; use is not. The latter may not be a factor for the typical home user whose license fee was bundled in with their hardware or OS, but it's going to be a factor for Wikipedia.

    53. Re:HTML5 Video by VGPowerlord · · Score: 1

      2. You're missing the point that you can't judge a contender for a standard based on how many people use it. If that were the case, then the W3C would standardize on IE6 behavior for HTML5, CSS3, and Javascript, and ECMA/ISO would standardize on Microsoft Office (non-Open XML) documents. There's also the fact that, should the W3C choose Theora, Dirac, or something else other than H.264, there's nothing stopping Sony from patching PS3s to support the new standard. To suggest otherwise is, as GP mentioned, short-sighted.

      Safari, Chrome, and Opera already have support for H.264. Internet Explorer 9 will have support for H.264.

      Firefox is the only major browser that has no plans to support H.264, and H.264 is the de facto standard, particularly since Google also controls the content-side through Youtube.

      At this point, Firefox can't beat them... will it join them?

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    54. Re:HTML5 Video by sopssa · · Score: 1

      You're forgetting that using Theora instead of H.264 costs big websites like YouTube, MetaCafe and so on serious money on bandwidth bills. Theora doesn't deliver the same quality with same bitrate, and hence requires more bandwidth. With the size of those sites, we are talking about a few hundred million dollars extra a year - just because of using an another video codec.

    55. Re:HTML5 Video by icebraining · · Score: 1

      Yes, instead of specifying the video in the 'src' attribute of the 'video' tag, you include one or more 'source' elements as children of 'video': http://dev.w3.org/html5/spec/Overview.html#the-source-element

    56. Re:HTML5 Video by Xtifr · · Score: 1

      Because closed formats have a company or companies willing to push it for reasons other than technical superiority.

      And I listed several companies that will push Theora (or Dirac). Open source hasn't been just-for-hobbyists for a long time now.

      So, only people who spend their valuable time and money getting an open phone instead of the iPhone are worthy of consideration in this debate?

      As far as Wikipedia is concerned, yes. They already limit audio uploads to formats your iPhone won't support; why would you think they'd act differently for video?

    57. Re:HTML5 Video by Hymer · · Score: 1

      I would ask you to consult the constitution of the United States of America which clearly states that free (as in free speech) is always better.
      By that definition any free (as in free speech) alternative is better than a non-free alternative, just because it is free.

    58. Re:HTML5 Video by maxume · · Score: 1

      I would argue that being good enough and widely deployed are the two biggest factors in a successful format, H264 has both of those, right now.

      (It might be nice that your phone supports Vorbis, but that's probably because the chip maker folded that support into everything, not because the phone manufacturer was worried that the dozens of Vorbis enthusiasts would be more interested in their product)

      --
      Nerd rage is the funniest rage.
    59. Re:HTML5 Video by linhares · · Score: 1

      QWERTY was technically better considering it didn't jam your typewriter.

      True. Yet, my point still stands. QWERTY is sub-optimal for today; and there's low probability that it will be obsolete anytime soon. --> Historical, accidental, political, and economic reasons play a huge part in setting up which technology will become de facto standards. And while I'm getting the heat here in this thread, I think that that expression that theora (or other open video standard) will win if it's technically better is seriously naive. There's much more to that than technical excellence.

    60. Re:HTML5 Video by Rockoon · · Score: 4, Interesting

      Why? Closed formats don't seem to operate under that constraint. In fact, technical qualities seem to be a non-issue as far as success goes in general.

      "Its the money, stupid!"

      No, not kickbacks, or payola, or licensing fees.

      Lets start at the top. Content providers have been banging their head into the bandwidth wall for a decade, starting when the notion of streaming high quality video really took off. Their cost, primarily, is bandwidth. Their product, primarily, is eyeballs. Their revenue, primarily, is advertisers.

      To make this work, they need to offer competitive quality in order to maximize the number of eyeballs, and they need to do it with the least bandwidth in order to offer competitive pricing to advertisers.

      H.264 was a big improvement over the previous generation of codecs, which finally allowed what might finally be viable online video streaming businesses.

      In this case, technically better still matters... its just about the only thing that matters. These businesses don't have the margin to fuck around. If they drop the ball then they lose their shot at #1.

      --
      "His name was James Damore."
    61. Re:HTML5 Video by Maxo-Texas · · Score: 1

      You're right. VHS has no shot against Beta.

      Oh wait.. .a lot of people started using it (It was cheaper and mini-series were 6 hours long) and even tho it was much worse than Beta, it won the format wars.

      Open video just has to not suck and be used in a lot of places. The fact that it should be cheaper will be another bonus.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    62. Re:HTML5 Video by Anomalyst · · Score: 1

      we are talking about a few hundred million dollars

      Assuming your extrapolated estimate is even in the ballpark, it sounds like a great motivation to contribute to the enhancement of the codec(s).

      --
      There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
    63. Re:HTML5 Video by Antiocheian · · Score: 1

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      I of course there is. Being good enough plus freedom is a better choice to being the best minus freedom.

    64. Re:HTML5 Video by Xtifr · · Score: 2

      if that wasn't a factor in your choice of phone, then my sympathy for you is nil.

      Thats okay, I feel sympathy for the fact that you won't be able to watch as much stuff as I will since you have a codec that while open, is largely irrelevant as far as content is concerned

      So, by your "logic", if my phone supports Vorbis, it can't possibly support other codecs? I assure you that's not the case.

      Beyond you seem to have built a beautiful straw man, but since it bears no resemblance to me or my opinions, I see little point in arguing. But I will point out that Wikipedia only allows Ogg Vorbis and Midi for audio uploads, so your assertion that their requirement for open formats is new is utterly baseless.

    65. Re:HTML5 Video by DarkOx · · Score: 1

      Windows gained its momentum prior to '93. There was that period of 1990-3 where lots of people were getting home computers who simply never had them in the 8 and 16 bit era. The C=, Ti, and Tandy machines were clearly on they way out of the home and SMB markets. As far as a stand alone microcomputer went your selection was SGI workstation, Apple, IBM, or an IBM PC Clone. Microsoft was able to give you a GUI on top and easy to get a handle on D-O-S. It was not the best but it was the cheapest that met the "good enough hurdle." That is what started the ball rolling.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    66. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Except that I watch hulu and youtube in firefox just fine, and they both use h.264.

    67. Re:HTML5 Video by tdelaney · · Score: 1

      Using CoreAVC (with CUDA for supported files) or ffdshow-tryouts (ffmpeg-mt) I haven't seen a single corrupted h.264 video recently. With CoreAVC (using CUDA), DxVA (for a much smaller group of supported files) or VDPAU, even Blu-Ray bitrate play back with absolutely minimal CPU usage (and with CoreAVC I can do post-processing afterwards). 720p versions of anime with softsubs in a Matroska container are vastly superior to similarly-sized XviD (usually 480p, sometimes 576p) with hardsubs in AVI.

      CoreAVC versions prior to 2.0 had problems with some x264 settings (e.g. weightp=2) but those seem to be resolved.

      I'm eager to see what Google does with On2, but for now h.264 is the "best" codec out there. There are definitely still uses for XviD (e.g. a lot of DVD players can play back XviD in AVI, but not h.264 or can't handle Matroska) but increasingly it is becoming an obsolete format.

    68. Re:HTML5 Video by Xtifr · · Score: 1

      As far as technical qualities go, MP3 is still king of audio, despite being the worst supported format out there, proprietary or otherwise.

      What?

      MP3 is the de-facto standard. OGG is bad supported, open, but still better. But it never got the momentum MP3 had.

      Er, sorry, that was very badly phrased. I meant to say that MP3 is the worst (from a technical standpoint) of the widely supported formats, but still the defacto-standard ("king"). "Worst (of the) supported formats", not "worst-supported format.

    69. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      Last I checked, it was not illegal to purchase a properly licensed GStreamer H.264 codec, and use that. The cheapest bundle including H.264 from Fluendo would cost you 28 euro.

    70. Re:HTML5 Video by formal_entity · · Score: 1

      Opera is the most ported application in history and it has _native_ support for Theora on all it's platforms/products; Opera Mobile, Opera Mini etc. Don't worry; it _WILL_ be possible to view open video content on all mobile devices.

    71. Re:HTML5 Video by TrancePhreak · · Score: 1

      Lots of the devices that support h264 do it in hardware. Something we are unlikely to see out of Theora.

      --

      -]Phreak Out[-
    72. Re:HTML5 Video by Anonymous Coward · · Score: 0

      I would ask you to consult the constitution of the United States of America

      What does Bush's toilet paper brand have to do with anything?

    73. Re:HTML5 Video by vijayiyer · · Score: 1

      He didn't say that Theora will win if it's technically better, only that it would lose if it weren't. There's a big difference, and I'm inclined to agree.
      People care even less about the ideology openness than technical merits, especially among people who aren't technical to begin with.

    74. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Safari, Chrome, and Opera already have support for H.264. Internet Explorer 9 will have support for H.264.

      Opera doesn't support H.264. It uses Ogg Theora. Chrome also supports Ogg Theora. Safari uses QuickTime for video playback, so if you install the XiphQT QuickTime components it also supports Ogg Theora. Internet Explorer 9 is probably using DirectShow for video playback, so if you install the Theora DirectShow filters Ogg Theora would likely work.

    75. Re:HTML5 Video by Korin43 · · Score: 3, Interesting

      This would seem like the obvious choice, and it's actually how Safari works (using Quicktime). There are patches for Firefox, but Mozilla refuses to use them because they want to make this a "Theora or nothing" battle, even though they'll never win. Chrome supports Theora and h264, so it hardly matters what their backend is. I think there are patches to webkit to let it use gstreamer as well though. I assume IE9 will use DirectWhatever.
      The problem is that Quicktime and DirectShow don't support theora or vorbis by default, so hopefully Mozilla/Wikipedia/anyone else who cares can get them popular enough that Microsoft and Apple have to finally support some free codecs.

    76. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Don't worry. His fault, not yours. As you clarified yourself, you didn't call it the worst-supported format but the worst supported format.

    77. Re:HTML5 Video by h4rr4r · · Score: 1

      No, they pay a lot more. The reality is I cannot get a legal h264 codec for my OS for a fraction of a cent. This is just another barrier to entry that the entrenched players are trying to raise.

    78. Re:HTML5 Video by Dr.+Spork · · Score: 1

      You are exactly right in every point you make, and I'm proud to see this sort of pushback on Slashdot, especially as the first comment on that propaganda-laden summary. I only hope that Firefox developers read this and allow Firefox to use a machine's native codecs to decode HTML5 video. Though this is legally and technically possible, they refuse to do it for ideological reasons.

    79. Re:HTML5 Video by h4rr4r · · Score: 2, Informative

      Which is not FREE software, is it?

    80. Re:HTML5 Video by PopeRatzo · · Score: 1

      but if open video technology really wants to win, they have to be technically better. There is no other way.

      There have been lots of technologies that "won" without being "technically better".

      --
      You are welcome on my lawn.
    81. Re:HTML5 Video by Dr.+Spork · · Score: 1

      Exactly. This seems like a no-brainer. Mozilla explicitly said that this is possible but they'll refuse to do it, because they're fighting a holy war and the users who own a H264 codec and just want the videos to work can fuck off.

    82. Re:HTML5 Video by sopssa · · Score: 1

      Opera also uses gstreamer, so you can get H.264 support too.

    83. Re:HTML5 Video by evilviper · · Score: 1

      Recall that Windows did not become the de facto standard OS by being better

      Sure it did. Backwards compatibility made it better. Running on cheap PC hardware made it better. Having a larger installed base made it better.

      Just because it was inferior in ways that matter to you, rather than the ways that matter to everyone else, doesn't mean it wasn't technically better in several way.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    84. Re:HTML5 Video by shutdown+-p+now · · Score: 4, Informative

      No-one said that it is.

      The point is that browser remains FOSS. If user is a FOSS purist, he doesn't install the "evil" codecs, and doesn't go to websites which only provide H.264 streams. If user is a pragmatic Linux user, he either buys the codec (freeness of browser not affected), or ignores the law and installs it from "non-US" repositories (legality of browser is not affected).

      Most people, of course, just use a mainstream desktop OS, where this all is provided out of the box (and they've paid for it when they purchased their PC/Mac with that OS preinstalled).

    85. Re:HTML5 Video by evilviper · · Score: 1

      Compatibilty of patent-unencumbered formats with a venue like Wikipedia would be exactly that kind of non-technical factor

      Precisely why the H.264 licensors opted to make H.264 gratis for non-paywalled web content, and again decided to extend that several years into the future... It would cost Wikipedia nothing to use H.264 into the foreseeable future.

      Not to mention that WP is such a dog on resources, they probably wouldn't notice that H.264 license fee, even if they did have to pay it in the distant future... After all, the whole pricing scheme is generally aimed at companies who can justify paying $100 for a codec only if it's going to save them at least $1,000 in bandwidth, and WP uses plenty of bandwidth, and Theora only makes that worse...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    86. Re:HTML5 Video by ClosedSource · · Score: 1

      You might note that the first Amendment applies to real people, not anthropomorphic lines of code.

    87. Re:HTML5 Video by h4rr4r · · Score: 1

      In reality I think morally the latter choice is far better. It is better to break an unjust law than to pay for closed source software.

    88. Re:HTML5 Video by Anonymous Coward · · Score: 0

      You must be one poor ass motherfucker to not be able to afford that.

    89. Re:HTML5 Video by Schraegstrichpunkt · · Score: 1

      It's all nice and all, but if $FOO really wants to win, they have to be technically better. There is no other way.

      Counterexamples:

      • PC vs. Mac vs. Amiga
      • Win32 vs. POSIX
      • Intel vs. M68k
      • VHS vs. Betamax
      • MP3 vs. Vorbis
      • X.509 vs. PKI
      • PEM vs. OpenPGP
      • DES vs. IDEA
      • EAX vs. OCB
      • SHA256 vs. MD5
      • Universal v.Reimerdes

      Sometimes the technically-superior option wins, sometimes it does not. Law, marketing, economics and other "soft" factors are sometimes more relevant than the particular technology.

      Personally, I want an open infrastructure to win so that the technically-superior applications developed in the future can win, rather than getting killed by patents or whatnot.

    90. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      The point is that the choice should be mine as a user, and should not be forced onto me by Mozilla by restricting my options. If I feel like paying for an "evil" codec, I should be able to do so. If I feel like ignoring the law that I perceive to be unjust - or if I live in a country where it's not illegal - I should be able to obtain the "evil" codec for free, and use it.

      That's why Firefox should stop their politicking, and support at least GStreamer on all platforms, like Opera does now. Better yet, support DirectShow on Windows, and QuickTime on OS X. Though I'll be happy with just GStreamer (especially since this has already been coded and available as a patch, and isn't in Firefox desktop builds only because of their political POV-pushing).

    91. Re:HTML5 Video by GooberToo · · Score: 1

      technology really wants to win, they have to be technically better. There is no other way.

      How'd that betamax work for you?

      Superior solutions don't always win. This is true for a long list of potential reasons. Simply put, Theorea isn't necessarily down and out - yet. A lot of people want Theorea or some other free contender to take over the pilot's seat in the standards. Even if its able to grab a co-pilot seat, most would consider that a win.

    92. Re:HTML5 Video by Hooya · · Score: 1

      You might also note that the supreme court decided that it also applies to non real people: corporations.

    93. Re:HTML5 Video by Schraegstrichpunkt · · Score: 1

      Are you comparing to '94 Linux?

      Amiga? Macintosh? OS/2?

      Where were you in '94?

    94. Re:HTML5 Video by qbast · · Score: 3, Informative

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      No, actually as long as Theora is not significantly worse than h.264 it does not really matter.

      However it's nice to see Open Video Alliance trying to partner with Wikipedia. In addition to being technically better, that's another aspect you need to take care of. You need to make sure websites, TV, phone, computer and so on manufacturers support your technology. You have to work with them to get it supported - not just put it out there and hope it catches up because its "open", because that's not going to happen.

      Yeah, just look how popular Vorbis Ogg is in portable music players.

      Personally I would also hate to see technically inferior solution being used, as it would eat huge amount of bandwidth. Theora just isn't on the same table with H.264 for Internet video. Theora is based on VP5 from On2 and now that Google acquired them, they're going at VP8.

      Actually it is based on VP3 and it is way behind h.264 - it does not even support B-frames! Also being at least one generation behind, Theora is dead end - all that is being done at this point is tweaking the encoder.

      What I'm more worried about is that I cannot watch Wikipedia videos with any other device than my PC. Want to see a video clip of a place you're traveling on your phone? Not possible. Want to see videos from Wikipedia with your PS3/360? Not possible.

      Well then, make sure you complain to manufacturers of these devices. If enough people care, they will add Theora support.

      It will create some serious problems, and I don't think Wikipedia is big enough to push the change alone.

      Actually I think Wikipedia is about the only site that can push the change. It is biggest and most popular encyclopedia on the net, has no real competition and would be extremely hard to recreate. There is already bunch of Youtube-like sites, so even if YT switched to some unpopular format, lots of people would just go elsewhere. In case of Wikipedia there is nowhere else to go.

    95. Re:HTML5 Video by h4rr4r · · Score: 1

      I can afford it fine, why would you assume that this is the issue?

    96. Re:HTML5 Video by RAMMS+EIN · · Score: 1

      ``It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.''

      I don't think it helps. Vorbis was better than MP3 for years, but never managed to dethrone it.

      Rather, I think what a format needs to succeed is enough backing. Proprietary formats always have some organization pushing them. What they do is go out and convince as many people and organizations to start using the format. If they succeed, people will have invested so much in the format that they won't abandon it. At that point, providing support for the format becomes a selling point, so you will see hardware and software vendors adding support to their products and listing it on the front of the box they put around their products.

      The same thing works for open formats.

      The problem is: large, powerful, and wealthy organizations that would be good backers for a format usually decide not to back an open format, because a proprietary format, especially one they own, gives them more control, and thus more opportunity to make money. Hence you see Apple pushing AAC with their own, proprietary DRM, Microsoft pushing WMA with their own proprietary DRM, but neither providing support for Vorbis in their products.

      The same is happening in the video codec world. It's not about quality, it's about control. People are rallying behind Theora because it's free, and large organizations have been pushing H.264 because it's not free. Of course, H.264 has been pushed for a while, and quite successfully, so there is already widespread support for it.

      The way I see it is that the world is large enough for more than one codec. If people want to use a proprietary codec, I am fine with that. On the other hand, I want people to be aware of the legal obstacles surrounding proprietary codecs, and related things, such as protocols and file formats. Standardizing on free codecs, protocols, and file systems means that everyone gets the opportunity to participate. Standardizing on proprietary codes, file systems, and file systems means you are reducing the choices available to those who would interact with your system. You would be creating lock-in and/or putting a legal and/or financial burden on people. How burdensome this is varies from case to case, but it's important to recognize the effect, and organizations ought to consider if they can responsibly impose such limits. I think it's wrong for governments to publish materials in proprietary formats, for example.

      With all that in mind, I am glad that people and organizations are campaigning for freedom. I bear H.264 no ill will, but until it becomes free (as in freedom), I hope organizations will offer media in free formats as well as or instead of H.264.

      --
      Please correct me if I got my facts wrong.
    97. Re:HTML5 Video by westlake · · Score: 1

      However, open video formats simply do not need to be better than the proprietary formats, they simply need to be "good-enough" and be ubiquitous on the web, and pretty soon all browsers (except IE, probably) will support them out of the box

      The geek is obsessed with the browser.

      But applications like Skype can be launched outside the browswer. Netflix streams HD directly to your big screen TV. Hardware-accelerated H.264 is no farther away than your cell phone.

    98. Re:HTML5 Video by icebraining · · Score: 2, Insightful

      How is Mozilla forcing you? No one forces you to use default Firefox. If it's available as a patch, compile Firefox yourself and there you have it. Even if it wasn't, you could make it yourself or pay someone to do it.

      But no, you want to force Mozilla to give you what you want. Well, too bad. One of Mozilla's goals is to defend the right to browse with a complete free stack.

    99. Re:HTML5 Video by AnotherUsername · · Score: 1

      Not really. If the day comes that I can't watch videos in firefox, I will simply switch to a different browser. 99% of the Internet using population would do the same. Once firefox's developers start seeing their users leave en masse, they will scramble to include support for other codecs. Unfortunately, by then it may be too late.

      --
      I don't like Linux. This doesn't make me a troll.
    100. Re:HTML5 Video by Lunix+Nutcase · · Score: 1

      No, they pay a lot more.

      How so? The H.264 royalties are capped at $5 million dollars. Spread out over all their yearly customers they'd only have to charge people a fraction of a penny to cover the costs.

      The reality is I cannot get a legal h264 codec for my OS for a fraction of a cent.

      Except that Microsoft has been providing a legal H.264 codec in it's OS for years now. I don't remember seeing the price of the OS skyrocket.

    101. Re:HTML5 Video by Anonymous Coward · · Score: 0

      He didn't say that Theora will win if it's technically better, only that it would lose if it weren't. There's a big difference, and I'm inclined to agree.

      Hardly. If you assume that things must lose because they are technically inferior, you must conclude that the technically superior option will win.

    102. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      But no, you want to force Mozilla to give you what you want.

      I don't. I'm not asking them to ship H.264. I'm asking them to support an open framework so that I can make the choice.

      Isn't FOSS supposed to be all about giving more choices to the user (sometimes, at the expense of the freedom of developer)? Or is it applicable only when user chooses "correctly", and should be retracted whenever there is a likelihood that the majority of users will choose "incorrectly"?

      If they want me to make a choice by using a different browser, then I will be happy to do so, of course.

      One of Mozilla's goals is to defend the right to browse with a complete free stack.

      I don't see how the right to browse thusly is in any way infringed by supporting an open codec framework. The requirement to browse that way is weakened, yes.

      And this is even leaving aside the fact that using system codecs is a Good Thing for purely technical reasons, regardless of this whole H.264 vs Theora mess - for the same reason why sharing libraries (as it is done in Linux distros) is better than local-copy-for-every-app as as typical in Windows as OS X.

    103. Re:HTML5 Video by aix+tom · · Score: 1

      Well said. The main thing to keep in mind when choosing software (especially for businesses, but also for me privately) is :

      1) What does it cost me?
      2) Does it solve my problem? What do I gain?

      There are a lot of areas where GPL software solves my problem and there I will happily use it. (I would for example never run a Windows box at home any more, since it's just too much trouble for too much money). But when I see that I would need additional resources to use a OSS solution, which would cost me more than commercial software that does the same thing better, easier and cheaper in the long run, I have no problems choosing the commercial version.

    104. Re:HTML5 Video by h4rr4r · · Score: 1

      You pay in other ways as well, restricted freedom, barriers to entry that prevent competition, etc.

      I said nothing about windows. I stated I cannot get a legal codec for fractions of a cent. Please feel free to point one out that is available at that price.

    105. Re:HTML5 Video by WWWWolf · · Score: 1

      It's all nice and all, but if open video technology really wants to win, they have to be technically better.

      <alittlebitofsarcasm>

      Good, good, dear developers. Keep the "technological superiority" debate up. Never listen to the occasional grumble from the users who would, you know, be able to actually do something. Like watch videos online. Maybe tonight.

      Don't worry! As a merry Firefox user, I'm sure I can find plenty of videos to watch in Wikimedia and, um, the Internet Archive for the most part. I'm sure you can soon come up with the standard that allows us to watch YouTube in all of its high-def glory without Flash.

      </alittlebitofsarcasm>

      Want to see a video clip of a place you're traveling on your phone? Not possible.

      <moresarcasm>

      Ah! To play videos on mobile phones. Truly, a fine application for H.264; a place where precision and fidelity are of utmost importance, a niche where Theora couldn't possibly compete. Verily! Wanderest thou now in the land of mobile phones, a veritable bastion of high-def videos, gigantic bitrates and Dolby-certified surround sound. Do not queue for content; queue for content to the extreme by literally queuing for the content. Mobile weather forecast: This winter will be colder than the last year, because hot air from marketing is meeting the cold reality even faster than before. The spring will still suck.

      </moresarcasm>

      *sigh* Sorry, I'm from Finland, we've already had more than enough time to get cynical about mobile applications. =)

      Want to see videos from Wikipedia with your PS3/360? Not possible.

      No, but since there's no web browser for 360, the point is moot if we're discussing HTML 5, is it not? And I've yet to figure out how to play H.264 videos on it. (I've heard it's supposed to play H.264, but it sure seems picky about the file format. It plays XviD videos fine, though.) And my Wii is barely able to play lowest-resolution FLVs from YouTube anyway, so meh.

    106. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Or just use a codec that already works... that's even cheaper than hiring codec developers.

    107. Re:HTML5 Video by mcneely.mike · · Score: 1

      It's all nice and all, but if open video technology really wants to win, they have to be technically better. There is no other way.

      Did Microsoft get to where it is today by delivering something that was technically better than the other offerings?

      If we jump on board at wikipedia, then jump on board at other sites, we can make it happen....numbers is what counts. More companies are seeing open source being adopted and they see it (gnu/linux) is technically better, but it will still be numbers that will make them sit up and jump on board.
      People still use windows because of numbers ("Everyone uses it"), not because it is technically better.
      Think big and the change will come.

      --
      soylentnews.org Go there to enjoy the people!
    108. Re:HTML5 Video by RAMMS+EIN · · Score: 1

      ``The point is that the choice should be mine as a user, and should not be forced onto me by Mozilla by restricting my options.''

      Right. And the good news is that, because Firefox is free software, Mozilla cannot restrict your options there. They can decide not to provide you with the capabilities you want out of the box, but they can't prevent you from adding those capabilities.

      --
      Please correct me if I got my facts wrong.
    109. Re:HTML5 Video by VoltageX · · Score: 1

      Did you actually try Fennec on the N900? It's horrific.

      --
      "Anonymous could not immediately be reached for further comment." - International Business Times
    110. Re:HTML5 Video by Pentium100 · · Score: 1

      You pay in other ways as well, restricted freedom, barriers to entry that prevent competition, etc.

      Yea, like for example, my phone won't be able to play the videos, or my bluray player. No hardware chips that can decode it, no GPU acceleration. That's why we need h264 - it's more widely supported.

    111. Re:HTML5 Video by VGPowerlord · · Score: 1

      Internet Explorer 9 is probably using DirectShow for video playback,

      No, Microsoft is trying to use IE9 as a wedge to get people to buy Windows 7, so it uses Direct2D (introduced in Vista SP2).

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    112. Re:HTML5 Video by LWATCDR · · Score: 2, Insightful

      Politics aside By going with the OS codec subsystem offers other benefits.
      Suppose the Vorbis folks produce an updated version you can just download the codec and install it and not have to wait for Mozilla to update Firefox. Same for security updates.
      Or let's say some website decides to use Dirac? Add the Codec and your good to go.
      Using a codec system is more flexible and can be more secure.
      At this point the decision is purely political statement at the cost of flexibility and usability which I feel is ALWAYS a bad way to make design choices.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    113. Re:HTML5 Video by Shikaku · · Score: 1

      Fork it. Veofox or Videofox, just keep it up to date with the firefox security updates.

    114. Re:HTML5 Video by jonwil · · Score: 1

      The problem is, any video codec that actually looks like being competitive with modern video codecs like H.264 or VC-1 is going to be assaulted by patent claims from all directions. Even if such claims are not legitimate, the costs of fighting patent claims are so big that companies are going to be reluctant to use the codec. (after all, if a codec that is as good as H.264 and VC-1 but without the need to buy a patent license exists, why would you use H.264 or VC-1 if you dont have a need to be compatible with something else that uses those codecs)

      Even Theora is likely being given the once over by lawyers at companies with video codec patents looking for possible attacks they can use if it ever gains mainstream support from someone worth suing.

    115. Re:HTML5 Video by Pentium100 · · Score: 0, Offtopic

      sharing libraries (as it is done in Linux distros) is better than local-copy-for-every-app as as typical in Windows as OS X.

      This is the part about linux that I hate the most.

      If I have a PC that is not connected to the internet and want to install some program, if that PC is running Windows, I can buy or download the program, write it to a CD or DVD, carry the disc to the computer without connection, put the disc in and install the program. I may be asked to also install .NET, DirectX or some other big part. I can install them, actually, I probably should install them, they are available for download, I can get them, write them to a CD...

      This would at most cause me two trips (I arrive with the CD and find out that I need .NET, time to go back and download .NET).

      On Linux it's different. I can download the program (be it as a source or .rpm or whatever), write it to a CD, go to the PC without internet connection, try to install it and find out that it needs lib01. Go back, get lib01, try to install it, find out that it needs lib02 and continue until finding out that lib37-127.0.0.1 conflicts with pretty much every program on that PC.

      tools like apt-get and yum reduce this problem, assuming you have internet connection, and the program is in the repository.

    116. Re:HTML5 Video by hedwards · · Score: 1

      That's true, but that's also assuming that you're using something that is supported. Windows definitely doesn't have a marketshare of 98%. It's hard to say what it is exactly, but it's probably closer to 92%. OSX itself is in the area of 6% of the total.

      Linky for the estimate: http://en.wikipedia.org/wiki/OS_market_share

    117. Re:HTML5 Video by Pentium100 · · Score: 1

      Though I'll be happy with just GStreamer (especially since this has already been coded and available as a patch, and isn't in Firefox desktop builds only because of their political POV-pushing).

      Can you provide a link?

      I'd love to make a h264 compatible firefox version, assuming I'll be able to get the compilers and everything working. As I understand almost nothing about C++ this will be interesting.

    118. Re:HTML5 Video by LWATCDR · · Score: 1

      Well I in the EU I believe it is but most people will be using it on Linux and most Linux users will have no problem using the Restricted sources and being Rebels.
      Of course if you are Mac or Windows you are already not using a 100 percent free stack. And to be honest Unless you are using LinuxBios even with Linux you not using a 100% free stack. So it is all a matter of degrees. The result if this doesn't change is that many people that currently use a FOSS browser will stop using it and go with a closed source browser like IE, Opera, Safari, and or Chrome.... Even on Linux so the result looks likely to be a more closed browsing stack.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    119. Re:HTML5 Video by ClosedSource · · Score: 1

      In any case, Code is not a corporation.

      Nevertheless, it's not the first time the court has screwed up. Their latest decision with respect to the military draft was that it wasn't "involuntary servitude".

    120. Re:HTML5 Video by Pentium100 · · Score: 1

      Hardly. If you assume that things must lose because they are technically inferior, you must conclude that the technically superior option will win.

      If both h264 and Theora codecs were created yesterday the technically superior codec may win, but it also may not, becasue the other codec if "free" or because of the marketing. Betamax was a higher quality format, but VHS still won the format war, but both formats were introduced at around the same time.

      Now, however, we have h264, which is a defacto standard. It is used in digital TV (in some countries, in others it's mpeg2), cell phones can play it (I don't know if newer cellphones can also record it, mine records in divx), bluray players can play it, flash can play it, a lot of video websites have their videos in this format.

      To replace all this, the new codec has to be technically superior and by a large margin. For example, h264 is replacing divx/xvid, but still has not managed to do so, despite it being a superior format.

      But now it comes down to "yea, let's buy new cellphones, bluray players and make youtube and others to transcode their videos, all this so that a few* people could be satisfied by not having to get a patented codec".

      *few = those, who:
      1.Have Windows version older than 7 or other OS.
      and
      2.Do not have the codec already (don't watch any h264 encoded videos).
      and
      3.Live in a country that recognizes the patents on h264.
      and
      4.Care about not violating the patent law of their country.

      Well, they can continue to use flash.

    121. Re:HTML5 Video by _KiTA_ · · Score: 1

      and tends to fall over and shit itself with even the tiniest bit of corruption.

      And your answer to this is something like XviD which is far worse at bitstream corruption? HAHAHAHAHAHAHAHAHA.

      "Blah blah, Xvid which is far worse at technobabble". AVI+XVid works. Most of the time MKV+x264 doesn't. Xvid subs appear, any corruption is fixed after the next keyframe, and the audio syncs up properly. 264 doesn't, it fails on all those counts at random.

      That's the long and the short of it. One works and is reliable. The other is not.

      This is a moot point anyway. It's just compression, how hard could it be? Lets get a sourceforge project going to make something better.

      Oh yes, it's just soooo simple. Sure, if you ignore all the complex things that go into actually building a audio/video codec with good compression efficiency. Is this ignoring the fact that it took codecs like DivX, XviD, x264 years and years to reach their current states of quality and efficiency?

      I believe in the bazaar model -- with enough eyes, EVERYTHING is a simple problem.

      Simply put, we as a community could make something better than x264. Compression, decompression aside, the fact that it'd be free software would make it better -- eventually.

    122. Re:HTML5 Video by Annymouse+Cowherd · · Score: 1

      The MPEG is charging no royalties on web based video.

    123. Re:HTML5 Video by Pentium100 · · Score: 1

      MP3 was the best format available at the time. When it became mainstream, it became very hard to replace it, because doing so would require replacing all of the mp3 players that did not support the new format (AAC or whatever). Also, to most people mp3 is good enough, so we have a lowest common denominator - mp3. I can publish the audio in mp3 and almost guarantee that everybody will be able to play it, or I publish it in Vorbis or flac and provide the mp3 version for those that do not support the better format.

      Now let's say that AAC was invented before MP3. Who in their right mind would replace their AACPlayer with a MP3Player to support the new format, when it's worse than the current one?

      VHS beat Betamax because of convenience (longer tapes) and because both formats were introduced at around the same time. If Betamax was introduced, for example, 5-7 years before VHS, it would have already become a de-facto standard and VHS wouldn't have been able to compete as it did, since people would think "well, VHS tapes are cheaper, but I have to buy a new VCR, which is expensive, I can buy a lot of tapes for the price. I would then have to have two VCRs - one to play my old tapes and one for new tapes".

      The same is with h264 vs Theora. To support Theora, I would have to buy a new cellphone, others would have to buy new bluray players (I don't have a bluray player). And on top of that, the format is inferior. I can see the reason for upgrading from xvid to h264 (better quality+smaller files), but h264 to Theora? Worse quality, less supported and only really useful to a few people, who are not me.

    124. Re:HTML5 Video by IainCartwright · · Score: 1

      This is not correct. Direct2D is a 2d graphics API that will be used in IE9 for rendering graphics and text (via DirectWrite). DirectShow (which i understand has optional theora support) will be used for video rendering.

    125. Re:HTML5 Video by Anonymous Coward · · Score: 0

      The current experimental version of the Theora encoder produces video files that can be played using current Theora players. The quality is appreciably BETTER than h264.

      http://www.osnews.com/permalink?413958

      When this gets released, Theora will overtake h264. According to your theory at that point everyone would sensibly switch to Theora.

    126. Re:HTML5 Video by hairyfeet · · Score: 1

      I'm sorry, but I have to disagree. With H.264 I can take this circa '05 Sempron I use as a Netbox (1.8GHz, 1.5Gb of RAM) and play high def videos simply by adding a cheap 4350 into the AGP slot, thanks to hardware acceleration. from what I've seen so far there isn't anybody seriously working on Theora acceleration even for the "big three" AMD, Intel, Nvidia, even though two of those (AMD and Intel) have released their specs and that of course doesn't count all the cell phones, PMPs, etc that have come out or are coming out with H.264 support.

      The problem is it appears Theora developers are acting like the only thing out there is desktop PCs, when the "throw more cycles at it!" era is past. More and more of my customers are switching to low cost netbooks and nettops and low wattage CPUs (the 65w AMDs are selling quite nicely) because they have realized bigger often isn't better, especially with regards to their monthly electric bill.

      If Theora would have came out in 98 it would have had a real shot, but hardware acceleration isn't just the wave of the future, but of the present as well. Even the lowest cost desktops I'm selling have support for H.26x, WMV 7-9, DivX/Xvid MP4, and MPG 2 out of the box, and believe me even on a quad core like mine you can really tell the difference, more so on these lower end machines that are so popular right now. Video plays smoother, the PC is more responsive, in short the experience is just nicer with hardware acceleration.

      For Theora to have any kind of chance it is gonna need hardware acceleration so all these low cost devices can play the content. Without it I'm guessing more folks will just avoid the sites with Theora, they won't be able to tell you why but they WILL notice when videos at site A (Theora) play like shit while site B (H.264) play just fine. But so far I haven't seen anyone even offer beta drivers for hardware acceleration of Theora content.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    127. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Where can you get h.264 for windows? I tried opening an h.264 encoded wmv file the other day in Windows Media Player and it didn't open or download a codec or anything. The documentation for installing h.264 interpreter seemed complicated for a normal windows user. Any links would be helpful.

      I mean, I bet VLC would work. But why can't I get windows media player to work? I disagree that h.264 is everywhere.

    128. Re:HTML5 Video by LingNoi · · Score: 1

      How is that any different from your having to download .NET example?

      It's funny when it comes to windows you just hand wave all the issues away but when it comes to a different OS suddenly it's a problem for you.

      Double standards.

    129. Re:HTML5 Video by Pentium100 · · Score: 1

      It is biggest and most popular encyclopedia on the net, has no real competition and would be extremely hard to recreate.

      All content on Wikipedia is available for free to distribute, so one could make a copy and transcode the video files to h264 and audio files to mp3 or AAC.

      It would be even easier to recreate than youtube, since with youtube, you are not allowed to copy the videos to your new site.

    130. Re:HTML5 Video by Pentium100 · · Score: 1

      Did Microsoft get to where it is today by delivering something that was technically better than the other offerings?

      Yes, Microsoft delivered a Windows component that could be bundled with applications and allow them to run on DOS, therefore a lot of Windows applications were created and this made the Windows OS better. Remember Microsofts "Embrace, Extend, Extinguish" - to Extend you have to make it better than the competition so that you can then make it incompatible and Extinguish the competition, because the users chose you.

    131. Re:HTML5 Video by MtViewGuy · · Score: 1

      Nice try, but H.264 is such a widely used standard (it's the most prominent video codec for Blu-ray discs and YouTube is moving heavily into this format) that Ogg Theora will end up being a niche standard like the MKV format.

    132. Re:HTML5 Video by kramerd · · Score: 1

      ...What internet users are not using the internet?

      Isn't internet use part of the definition of internet user?

    133. Re:HTML5 Video by coolsnowmen · · Score: 1

      Yeah, I agree, parent's problem isn't the video itself, it is some link in his decoding chain.

    134. Re:HTML5 Video by Anonymous Coward · · Score: 0

      WTF. Flash didn't get any h264 support until flash 9, long after online video was popular. If you want to support anything older you're stuck in H.263 or VP6 both of which produce worse results than the current Theora, and a significant majority of flash video out there is still in these older formats, including the default stuff that youtube serves.

    135. Re:HTML5 Video by dangitman · · Score: 2, Insightful

      Nobody would argue that MP3 is a closed format, for example.

      I would. MP3 is a proprietary format.

      --
      ... and then they built the supercollider.
    136. Re:HTML5 Video by arose · · Score: 1

      Right, because a software update can create a hardware Theora decoder *rolls his eyes*.

      You must think you made a good argument... The reality is that the decoding doesn't happen in hardware, processor intensive parts of the decoding are accelerated in hardware, said operations are common across many codecs. Experimental hardware accelerated decoding for Theora has been done with existing hardware. It's not a roll-eyes-at problem, it's a manpower problem.

      A lot of people just don't get the problem and constraints on mobile devices here - it isn't just that the codec is technically inferior, meaning that it requires more processing and decoding than h.264, it is the availability of hardware decoders.

      Bullshit, you are just talking out of your ass. The often cited technical inferiority of Theora has nothing to do with higher processing requirements, its the lower complexity that hinders the encoding quality. Theora is considerably lighter then H.264, where, even with hardware acceleration, you have to fuck with low complexity profiles.

      For most equipment, this isn't possible, it would require a new revision of the hardware, and all previous revisions wouldn't have access to the Theora content.

      So which devices have H.264 decoding done in dedicated chips as opposed to using DSPs for acceleration?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    137. Re:HTML5 Video by dangitman · · Score: 1

      So, by your "logic", if my phone supports Vorbis, it can't possibly support other codecs? I assure you that's not the case.

      So, what's the point then? If you are all about open standards, then why would you want a device to support closed standards? Where's the incentive for content providers to use open standards if you have support for their existing closed standard, anyway?

      --
      ... and then they built the supercollider.
    138. Re:HTML5 Video by Pentium100 · · Score: 1

      How is that any different from your having to download .NET example?

      .NET and similar frameworks on Windows are few enough that I could download them and write them to a CD before going to the PC without connection.

      Also, a lot of programs state that they need .NET or DirectX and some programs even come with the required software already on install disc (for example, games usually come with the required version of DirectX).

      For example, when I install Windows on a computer, I also install .NET, video codecs and the newest version of DirectX available.

      I can't download and install every single lib on Linux, also, I won't know that lib12 needs lib13 until I install it.

      And that is the difference. If Linux only had 50 optional libs, I could download them all and write them to a CD so I could use them.

    139. Re:HTML5 Video by Anonymous Coward · · Score: 0

      according to http://www.osnews.com/story/23018/Ogg_Objections_Problems_with_the_Container_Format and http://hardwarebug.org/2010/03/03/ogg-objections/, there are problems with theora / ogg that make it ‘bad for any purpose’. granted that the author could have a professional interest in downplaying merits of concurrent formats, his arguments still look detailed and informed. at the end of the day, we still have by far too many codecs for sound and video, and to many data standards are simply too complex, and more convolved than necessary.

    140. Re:HTML5 Video by Compaqt · · Score: 1

      What phones support Ogg Theora?

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    141. Re:HTML5 Video by Compaqt · · Score: 1

      Only for now.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    142. Re:HTML5 Video by michaelhood · · Score: 1

      Hell, tell me where to send my 0.01$ to end all this non-sense and force HTML5 video to standardize on H.264

      They'll even make five times the profit by doing so.

      Indeed, I'd be happy to donate EVERY Slashdot user's share if it stops all this bickering.

    143. Re:HTML5 Video by Compaqt · · Score: 1

      Exactly what is the difference in bandwidth for H.264 vs. Theora?

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    144. Re:HTML5 Video by LingNoi · · Score: 1

      .NET and similar frameworks on Windows are few enough that I could download them and write them to a CD before going to the PC without connection.

      There's nothing stopping you from doing the same with Linux either. Most programs don't have a huge list of dependencies.

      I can't download and install every single lib on Linux, also, I won't know that lib12 needs lib13 until I install it.

      You don't need to install every package on linux. Also there is nothing stopping you from going to some place like http://packages.ubuntu.com/ and finding out which packages you need to download.

      If it's not in the main repo you can just double click on the file and look at the list there.

      If Linux only had 50 optional libs, I could download them all and write them to a CD so I could use them.

      If linux only had 50 optional libs it would be as bad as the train wreak that windows is in. Downloading DirectX (104.0 MB) and .NET (another 235 MB according to the full install on the bottom of this page) just to run your program. Are you kidding me?!

      It is MUCH better to just download the 5 dependency libs at 2 to 5 Meg each all of which track updates through one update manager.

      Either way while you're still waiting for your 300 Megs of bloat to finish downloading I would have already downloaded the what I needed, burned it to the disk and be finished.

    145. Re:HTML5 Video by dakameleon · · Score: 1

      ... for now; the next renewal is due in 2016 or some such, at which point they have the option to enforce charges.

      --
      Man who leaps off cliff jumps to conclusion.
    146. Re:HTML5 Video by dangitman · · Score: 1

      I don't think we'd be back to the "this site requires IE 8.x or higher" days. That really is something from early 2000

      How is that possible? Internet Explorer 8 was released in March 2009, nearly a decade after the year 2000.

      --
      ... and then they built the supercollider.
    147. Re:HTML5 Video by dangitman · · Score: 1

      Is there any way to specify multiple formats? Ex: that points to H.264, but falls back to H.264 if that isn't supported?

      If H.264 isn't supported, then how could it fall back on H.264 as a supported option?

      --
      ... and then they built the supercollider.
    148. Re:HTML5 Video by wealthychef · · Score: 1

      Well if it's that small a fraction, then Apple and MS probably don't care either. In fact, it looks like "patent encumbrance" is grossly overstated here.

      --
      Currently hooked on AMP
    149. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Get the Combined Community Codec Pack.

    150. Re:HTML5 Video by Pentium100 · · Score: 1

      Either way while you're still waiting for your 300 Megs of bloat to finish downloading I would have already downloaded the what I needed, burned it to the disk and be finished.

      Most programs don't have a huge list of dependencies.

      Too bad that the list is not published anywhere (at least some Windows program says that it needs .NET).

      And while you are trying to find out exactly which 5 libs at 2 to 5 Meg each are needed, I would have already installed both .NET and DirectX from a CD I made some time ago and use on every PC that does not have them. If I am installing software from a CD, like a game, it most likely will already have .NET and/or DirectX on the same disc, so I won't even need the separate one.

      If I could get all Linux dependency libs on one CD or DVD, I could just use that disc if I needed to, no more hunting.

      Also, both DirectX and .NET are updated trough Windows Update.

      Also there is nothing stopping you from going to some place like http://packages.ubuntu.com/ and finding out which packages you need to download.

      let's see...

      search: "dash" (one thing I was looking for recently).

      Depends on: libc6, debianutils (I don't know what packages are already on that PC).
      libc6 depends on: findutils, libc-bin, libgcc1, tzdata
      findutils depends on: libc6 (which one I install first?)
      libgcc depends on: gcc-4.4-base, libc6
      and so on...

      Why can't I download the full program? You know, aside from .NET and DirectX, all programs ship with all of their parts, I don't need to hunt every .dll file to install the program. Sometimes linux programs are provided as -static, which I assume includes all of their parts, I always grab this if it is available. But not everyone provides this option. Why?

    151. Re:HTML5 Video by muyshiny · · Score: 4, Insightful

      that's bold of you user #31 million some.

      but seriously, it's important and i don't know if you're trolling or what, perhaps i'm that idealistic? please help me understand why having formats and software free of legal entanglement and reducing humanity's dependency on a few, often secretive, organisations is not worth the minimal effort that this volunteer-run collective is taking to contribute to a shared ideology?

      we joke and belittle 'slashdot' culture but a lot of this here shit is real sir and i think we do ourselves a disservice. and if you're sincere then damn, go read wikileaks for a bit and see if you can't get a sense of perspective. these are the tools with which we increasingly control our personal identities and the global economy of both ideas and goods. anyone who can understand why it's important to keep that as neutral and transparent as possible really ought to step up wherever they can because... it really is.

    152. Re:HTML5 Video by LingNoi · · Score: 1

      And while you are trying to find out exactly which 5 libs at 2 to 5 Meg each are needed, I would have already installed both .NET and DirectX from a CD I made some time ago

      See, this is what I was talking about in the first place. You hand wave over issues for your favourite OS and draw an unfair conclusion.

    153. Re:HTML5 Video by arose · · Score: 1

      One could argue thats why we need wider support for Theora, DSP and GPU acceleration isn't handed down like the ten commandments, with a little extra manpower Theora could have both.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    154. Re:HTML5 Video by arose · · Score: 1

      I'm not asking them to ship H.264. I'm asking them to support an open framework so that I can make the choice.

      That is an implementation detail (even if it has legal consequences), you still want them to do X instead of Y.

      Isn't FOSS supposed to be all about giving more choices to the user (sometimes, at the expense of the freedom of developer)?

      Yes, in the sense that you have the source code and modify it to your hearts content. No, in the sense that the developers might not spend their energy on creating, maintaining and debugging your pet feature.

      And this is even leaving aside the fact that using system codecs is a Good Thing for purely technical reasons [..]

      Portability and ease of maintenance are technical reasons to use cross platform libraries, none of the cross platform browsers use OS provided codecs in Firefox uses libtheora, Chrome uses ffmpeg, Opera uses gstreamer, even Safari carries QT over to Windows. It's just that Firefox decided not to use a multi-backend library, probably because there it doesn't make much sense do so when you can only distribute (as in include with the browser) one backend that is suitable for internet video.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    155. Re:HTML5 Video by arose · · Score: 1

      There are patches for Firefox, but Mozilla refuses to use them because they want to make this a "Theora or nothing" battle, even though they'll never win.

      The problem is that Quicktime and DirectShow don't support theora or vorbis by default, so hopefully Mozilla/Wikipedia/anyone else who cares can get them popular enough that Microsoft and Apple have to finally support some free codecs.

      They can't win, but hopefully they can?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    156. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      I don't know what distro you're having problem with, but last time I had to deal with a PC which wasn't online to begin with (which was ages ago, by the way), I quickly found out that Gentoo package manager allowed me to dump a list of all packages it would need to download (including all dependencies).

    157. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      Here is the Bugzilla ticket that has the patch, and tracks its inclusion (into Fennec).

    158. Re:HTML5 Video by Pentium100 · · Score: 1

      See, this is what I was talking about in the first place. You hand wave over issues for your favourite OS and draw an unfair conclusion.

      I don't hand wave over the issues. Yes, I would prefer if .NET was a part of the default Windows install, but it's not. At least I can download it and record it to a CD so I can use the CD if I need it in the future. Every program that needs .NET will works with the version I have on the CD.

      I can't do that with Linux. I can't go to linux.com and download "Libraries that are not part of a default install.tar.gz" record it to a CD and use the CD like I would use the CD with .NET. I first need to find out what libraries the program needs, then download them. It means that I will have to do this for every program that I install. The libraries that I installed for program X will probably not work with program Y.

      Also, on Linux, you can have library conflicts, while DirectX and .NET can be together in the same PC. Windows used to have .dll conflicts (Program X needs a.dll v1.2, program Y needs a.dll v1.1 and both versions are incompatible, but both have to be in the same place), but on Windows XP this was solved.

      Other than .NET, DX and Java, programs include the .dll files they need in their install packages. If I have all 3 installed (which can be done right after installing Windows, I don't need a program to tell me that it needs .NET to be able to install it), I can download any Windows program and be 99.99% certain that it will work. Wireshark comes with WinPCap included, for example, I don't need to download it separately.

    159. Re:HTML5 Video by Pentium100 · · Score: 1

      Last time I had this fun was with Mandriva (don't remember the version), but the computer was connected to the internet. While I was googling every package that it told me to, I thought that if this computer did not have an internet connection it would get very boring very fast. Oh, by the way, the last on the chain was some other version of glibc which hated everything else on that computer, so I couldn't install the program. On Windows (>=XP), the different version would be placed alongside with the one that's already there and programs could specify which one they want.

    160. Re:HTML5 Video by arose · · Score: 1

      What does Theora do that H.264 can't, aside from taking more bandwidth to get the same visual quality? Nothing.

      That is not strictly true. It has one bitstream that all compatible decoders can understand. With H.264 you have to worry about profiles, and in practice that means that you might as well consider the baseline profile to be H.264 and forget about any advanced capabilities, interesting approach to a "standard".

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    161. Re:HTML5 Video by arose · · Score: 1

      Is that why YouTube encodes with shitty settings? I do believe they value CPU more then bandwith, otherwise they'd take advantage of the often cited superiority of H.264, instead of encoding at the same "horrible" quality that Theora provides.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    162. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      Portability and ease of maintenance are technical reasons to use cross platform libraries, none of the cross platform browsers use OS provided codecs

      Uhh, what do you think GStreamer is on most Linux distros??

      And, like I said, I would be quite happy with just GStreamer on all platforms (it has stable Win32 and OS X ports) - which is precisely what Opera does, in fact. Someone else can write a gstreamer plugin that wraps native codecs after that. And the patch for GStreamer support in Firefox is not only already there, but they have in fact included it into the base repository - it's just that it's disabled for desktop builds (so your argument that "it's still code that needs to be developed, maintained and debugged" won't fly, sorry - they already decided they will support it).

    163. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      Sounds like you were really doing it wrong. Did you try to just use rpm directly? That thing doesn't unwrap the entire dependency chain - it only tells you what this particular package wants. Tracking that all manually is definitely going to hurt.

      On Mandriva, I think the one that would track dependencies fully is urpmi. A quick Google seems to say that urpmq -d -m would give you the list of all .rpm files that you need to install a particular package, with all dependencies. And urpmq -d -m --sources would just spit out a list of URLs that must be downloaded (which can be fed to most advanced downloader software on Windows, or wget on Linux).

    164. Re:HTML5 Video by X0563511 · · Score: 1

      Nothing stops you (or anyone else) from building an application statically, or including said .so files with it.

      You see SDL commonly included with commercial Linux games, for example.

      We just don't do it as often (for various reasons)

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    165. Re:HTML5 Video by Pentium100 · · Score: 1

      Yes, I did try to use rpm directly. I tried to make a Canon multifunction device work on 64bit Linux. The binary version was 32bit only, so I tried to compile the source package. I later gave up and connected the device to an older PC that has an even older Mandrake (still called Mandrake) version, but was 32bit and supported the binary drivers.

    166. Re:HTML5 Video by Pentium100 · · Score: 1

      Nothing stops you (or anyone else) from building an application statically, or including said .so files with it.

      Well, if I already had to hunt down all dependencies, then there is no need to somehow integrate them to the main app (would I need to know the programming language that was used to make the app to be able to integrate the dependencies?).

    167. Re:HTML5 Video by LingNoi · · Score: 1

      At least I can download it and record it to a CD so I can use the CD if I need it in the future.

      You're going around in circles. I already addressed this point. You can do this on linux as well as OSX.

      However that's not what you said, is it?

      I would have already installed both .NET and DirectX from a CD I made some time ago

      You were comparing downloading the packages and putting them on a CD with Linux to the CD already magically being burned on windows.

      Your poor comparisons like this, your general lack of linux knowledge and your unwillingness to accept facts when people correct you just shows how invalid the points you're making are.

    168. Re:HTML5 Video by Pentium100 · · Score: 1

      You can do this on linux as well as OSX.

      .NET: http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe
      DirectX: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0cef8180-e94a-4f56-b157-5ab8109cb4f5
      Java: http://java.com/en/download/index.jsp

      Where is the package of the Linux libraries that I can put on the CD? Or do I need to download them one by one?

    169. Re:HTML5 Video by mr_walrus · · Score: 1

      Betamax lost because it was an inferior format.
      no, not inferior on the tv screen, inferior usability outside of the tv.

      the initial machines that supported Beta were top-loading only, while
      VHS had front-loading.

      back in the era of stacking a/v components on top of each other inside
      cabinets, "top loading" anything is a huge cost of inconvenience.

      Beta lost for good reason. by the time Beta got front loading, VHS
      had a huge head start.

      i think i also recall Beta had shorter recording-time cartridges
      than VHS too.

      it was all about 'usability'. Beta *was* an inferior format at
      the critical point of introduction and acceptance by the market place.

    170. Re:HTML5 Video by Eivind · · Score: 1

      True. "works for me, and is good enough" trumps "theorethically marginally better, but requires you to toss away all your current players" every time.

      There's a point where improvements in quality CAN trump an established player. People -did- care about casette-cd or vinyl-cd advantages. Sound-quality was part of that, but I think random-access and ease-of-use might have been equally important.

      Most people who listen to music has changed from CD to mp3 too, and the argument wasn't better sound-quality (most mp3s are created from the CD anyway, so it can at best sound indistinguishable, in practice it's often worse), but again increased convenience. 2000 songs in an ipod, categorized by genre, artist, release-year or what-have-you is more convenient than lugging around 200 CDs.

      But swap mp3 for some other format that can produce equally good sound, at say 75% the filesize, and all you get is a collective yawn. My music-collection takes up 2% of my hard-disc as it is, who CARES if it's 2% or 1.5% ? And it's not as if harddisch-sizes have stopped growing.

      Transfer-speeds ? Listen, I can already download a good-quality mp3 at 100 times realtime, i.e. around 30 songs a minute. Who -cares- if it'd be 150 times realtime with this other format ? It just doesn't matter.

      And the patents ? They'll expire. They're not a -practical- problem for any home-user, both decoders and encoders are freely and plentifully available for all operating-systems, and work fine in practice.

    171. Re:HTML5 Video by jim_v2000 · · Score: 1

      "for that to happen in a big way then the thing they're pushing has to be technically superior."

      Or they could be ideologues and what they're pushing might just be the only option.

      --
      Don't take life so seriously. No one makes it out alive.
    172. Re:HTML5 Video by icebraining · · Score: 1

      I don't see how the right to browse thusly is in any way infringed by supporting an open codec framework.

      The framework may be open, but the codec itself is closed.

      I don't. I'm not asking them to ship H.264. I'm asking them to support an open framework so that I can make the choice.

      You're still want them to do what you want. They don't want to do that, and are in their right. (Well, some of them at least, it's probably going to be included in future versions.)

    173. Re:HTML5 Video by ubersoldat2k7 · · Score: 1

      For Debian/Ubuntu: http://aptoncd.sourceforge.net/ There, now stop whining about what is probably one of the best features of modern distributions. And the brand Linux doesn't have anything to do with this.

    174. Re:HTML5 Video by TheTurtlesMoves · · Score: 1

      Lets not forget its more than a license fee away from being allowed to use it. There is also the contract they make you sign to get that license. And that may include DRM type thing to be honored/supported. It also includes a clause that it only covers the patents from MPEG-LA, and that any 3rd party patents that are perhaps infringed is your problem.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    175. Re:HTML5 Video by TheTurtlesMoves · · Score: 1

      Licenses still need to be paid for encoders and decoders. Mplayer and their ilk are illegal in the US. And when the "free" time runs out........

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    176. Re:HTML5 Video by TheTurtlesMoves · · Score: 1

      Sorry for the double post. But there is are other issues here as well. MPEG-LA can change their minds and change the license terms. These licensing terms them selfs can be at odds with "free" and require DRM be implemented etc.

      Just because its "free" today does not mean its free tomorrow.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    177. Re:HTML5 Video by TheTurtlesMoves · · Score: 1

      ..Though this is legally..possible

      In some countries this would not be legal. I paid money to get a professional opinion on the matter.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    178. Re:HTML5 Video by marmoset · · Score: 1

      sharing libraries (as it is done in Linux distros) is better than local-copy-for-every-app as as typical in Windows as OS X.

      Considering the relative size and cost of modern mass storage, I greatly prefer the OS X bundle system over fighting "DLL hell" for the sake of saving a few megabytes of disk space.

      YMMV.

    179. Re:HTML5 Video by mcneely.mike · · Score: 1

      But, IBM's OS/2 (warp) was technically superior to windows.... who uses OS/2 today?
      Windows won out due to marketing and IBM being slow out of the gate in understanding their competition's way of waging war.
      DR/dos lost out even though it was technically better than MS/dos due to Microsoft sales people telling business' that it wasn't.

      --
      soylentnews.org Go there to enjoy the people!
    180. Re:HTML5 Video by OS24Ever · · Score: 1

      How about you solve some other real problems first before getting all rabble rabble about a video codec?

      That's the real issue as to why people don't care. You're not going to fire up your average internet user about the evils of that h.264 code shackled by patents. To them, the shackling is non-existent because they don't get a monthly bill for it. Claiming it's part of the OS and the the OS they got with their computer would have made it magically cheaper unless you're talking hundreds of dollars no one is going to care.

      The only thing the mozilla group's stand about not supporting h.264 does for me is mean I skip using the browser because it's just stupid. It's one thing to not have the codec 'built in' but if my computer already has a legally licensed h.264 decoder your piddly ass browser stopping me from using it because you want to 'make a stand' is retarded.

      I've long felt that silly things like this is what holds open source software back from mainstream assistance. It's just a personal view and you can disagree all you like and try to educate me to your view, but in the end, it's not worth the effort put into it because there are better things to worry about.

      'humanity's dependency on a few, often secretive, organisations'? Please, eye roll smiley face here. That's the most ridiculous thing ever. YOUR H.264 CODEC IS MADE BY THE ILLUMINATI!!11!! it just looks crazy and people will ignore it and yet another thing goes down the tubes.

       

      --

      As a rock-in-roll Physicist once said, No matter where you go, there you are.

    181. Re:HTML5 Video by Pentium100 · · Score: 1

      Thank you. Assuming I can get apt-get working on that PC (why can't linux apps come with easy configuration, like windows apps?), I'll be able to have a DVD with all of the optional libs on it.

    182. Re:HTML5 Video by Lunix+Nutcase · · Score: 1

      You pay in other ways as well, restricted freedom, barriers to entry that prevent competition, etc.

      How exactly am I "more" free if a youtube video is encoded in theora over H.264? And I don't give a shit about barrier to entry. But even if you are worried about such things, royalties don't even come into play until you're shipping a pretty high volume of H.264 encoders/decoders or if you run a website you'd have to have pretty significant traffic. If you are reaching the point where you'd have to start paying the royalties you probably have enough money to cover them.

      I stated I cannot get a legal codec for fractions of a cent.

      Sure you can. Download the free and legal, DivX H.264 decoder.

    183. Re:HTML5 Video by arose · · Score: 1

      Uhh, what do you think GStreamer is on most Linux distros??

      Yet another library. It does not have the status of DirectShow or QT, if that's what you are alluding to.

      Maintenance and debugging holds, sorry. I'm sure they have a bunch of experimental features floating in the trunk, so? And some third party gstreamer plugins that are wrapping yet other things? I do not want that in standard builds. Not because of ideological, but because there is more then enough blame flying around because Adobe can't get their shit together, yet more behind the scene crashes and what not? Stability matters.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    184. Re:HTML5 Video by MobyDisk · · Score: 1

      Dang it, man! I meant "fall back to Theora"

    185. Re:HTML5 Video by rockNme2349 · · Score: 1

      So .002 cents?

      --
      Sewage Treatment Facilities - "Our duty is clear."
    186. Re:HTML5 Video by Daniel+Phillips · · Score: 1

      if open video technology really wants to win, they have to be technically better. There is no other way.

      I disagree. General availability easily trumps a few DB of bandwidth savings when it comes to free content. And thanks to Wikipedia, no doubt can remain about the power of free, user generated content. Good enough rules in this domain and Theora is certainly good enough.

      --
      Have you got your LWN subscription yet?
    187. Re:HTML5 Video by moosesocks · · Score: 1

      Yep. Given the cost of bandwidth, the cost savings associated with using a more efficient codec could be substantial, even in light of the $5 million max. H.264 licensing fee.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    188. Re:HTML5 Video by Draek · · Score: 1

      Case in point, JPEG. There's been a plethora of better formats for all intents and purposes throughout the years, yet the only one that has managed to get a foothold in the web market is PNG, and more as a replacement for the patent-riddled GIF instead.

      Standards have never been about "the best", they've always been about what's "good enough" and easy enough to implement everywhere, h.264 fails horribly at the latter by requiring royalties from both decoders and encoders, and necessitating the use of dedicated hardware decoders to achieve acceptable performance under any device smaller than a typical desktop.

      --
      No problem is insoluble in all conceivable circumstances.
    189. Re:HTML5 Video by Draek · · Score: 2, Insightful

      Linux has gained momentum in its areas by being superior for developers and sysadmins who know what they're doing. Firefox gained momentum the same way. I can't think of an open source product that gained mainstream popularity without being technically superior.

      It depends on how you define "popularity" and "superior", but FreeBSD vs Linux (the BSD lawsuit was a factor, but that became moot before Linux hit even 1.0), KHTML vs Gecko, OpenOffice vs LaTeX (or Abiword/Gnumeric). Some would also argue for Bash vs $FAVORITE_SHELL_HERE as well but I haven't tried any of them to judge personally.

      So, only people who spend their valuable time and money getting an open phone instead of the iPhone are worthy of consideration in this debate? Like it or not, the iPhone's dominance isn't because of any media blitz or cult of Apple, it's because it came out in a market where it was by far the best choice and is still superior to any other smartphone I've seen.

      Really? if it can't support Wikipedia, then I guess it wasn't the best choice after all. All devices have problems, it just so happens that you chose one that had "closedness" and "dominated by a NIH-riddled corporation" as theirs.

      So, if you want to prioritize openness in your purchasing, that's fine. But this is about Wikipedia trying to influence the culture as a whole and the emerging standard, and to suggest that this process ignore the vast majority of people is at best naive and at worst extremely damaging to your own position.

      What the *fuck* are youn talking about? if this is "trying to influence the culture as a whole", then what is Apple's refusal to support Theora in Safari, outright rape of the pillars of our society? don't be so melodramatic, this is simply the logical consequence of Wikipedia's policies regarding free access to its information. Requiring payment of royalties to a third-party corporation for each uploaded video (as h.264 will become once the "free" period expires) would be very much a 180 degree turn from that. Audio in Wikipedia is already in Ogg Vorbis instead of the more popular-among-the-masses MP3 or the more popular-among-the-nerds AAC, requiring Theora was only expected.

      In fact, you may notice that this project isn't about making Wikipedia require Theora, they already do, all this projects aims at is to upload *more* videos, to make Wikipedia's video content more pervasive and, as such, regular people would be more likely to complain when their phone manufacturer refuses to support it and they're suddenly left with a text-only website.

      --
      No problem is insoluble in all conceivable circumstances.
    190. Re:HTML5 Video by RogerWilco · · Score: 1

      Or buy a distribution that gets you (nearly) everything on a couple of handy DVDs. That's what I used to do before I had a fast internet connection: Buy SuSE every now and then, I think they still sell those.

      --
      RogerWilco the Adventurous Janitor
    191. Re:HTML5 Video by Draek · · Score: 1

      Because they can be sure the open standard will be supported *everywhere*, whereas the closed ones may or may not be present depending on the particular manufacturer, model, time of release, and perhaps even the carrier it is connected to.

      Well, or it would be so if Apple hadn't thrown a tantrum when the W3C wanted to declare Theora the baseline standard. As it stands, now *all* codecs are in that situation and the only thing you can rely on is that the parser won't throw a fit over the tag itself, for all the good that does to you.

      --
      No problem is insoluble in all conceivable circumstances.
    192. Re:HTML5 Video by RogerWilco · · Score: 1

      I don't believe in the Bazaar model. I think most of the current successful FOSS projects don't use it.

      And then there are very few FOSS projects that come close in quality to their closed source counterparts.

      And there huge application areas where there are no FOSS options available because it's not a field that the typical FOSS programmer is interested in.

      --
      RogerWilco the Adventurous Janitor
    193. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Yeah, and there's a cost to Linux users:

      Crappy, buggy, slow, memory hogging F/OSS video implementations.

      The world has an economy, it runs on money, it must account for some difference to a free product. And to Linux, the difference is capability.

    194. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      You're still want them to do what you want. They don't want to do that, and are in their right.

      No-one is arguing against that. However, given the moral high horse of FOSS that Mozilla rides, I think it is an inconsistent position. Not that the hardcode FOSS camp has ever been known for consistency in that department, but Mozilla was more pragmatical... so far.

      Well, if they want Chrome to eat their lunch, so be it.

    195. Re:HTML5 Video by Anonymous Coward · · Score: 0

      "Theora starts to get momentum, it'll appear on phones and similar devices quickly enough"

      Problem is technology is about moving forward.

      I don't want to wait until 2012 to get a free version of what I was using back in 2006. It's sort of like waiting for Toyota to develop that 2004 V8 truck that was pretty much does the same stuff as the one I had from Ford back in 1999 (and really it took them awhile to start making V8 trucks). It's competition yes, and is good in the long run, but not something to based your principles on and deny.

    196. Re:HTML5 Video by RogerWilco · · Score: 1

      Agreed. This is one of the few things that would make me use Chrome or Safari instead.

      --
      RogerWilco the Adventurous Janitor
    197. Re:HTML5 Video by sglewis100 · · Score: 1

      It's slow, unwieldy, CPU intensive

      One can play 720@24p videos on an old AMD XP series chip with ffmpeg and it's not even really the fastest H.264 decoder around.

      I have a $199 Acer Revo running a 1.6GHz single core Atom hooked up via HDMI to my TV. It streams 1080p over 802.11n from a server upstairs, h.264 encoded via XBMC on Linux booted off a USB flash drive. So, I have far from the fastest machine, far from the fastest networking and far from having paid $1 for any h.264 decoding and it works just fine. Slow, unwieldy and CPU intensive it is not.

    198. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      Yet another library. It does not have the status of DirectShow or QT, if that's what you are alluding to.

      It does for any Gnome-centric distro - like, say, Ubuntu.

      It doesn't really make sense to talk about "vanilla Linux" as an OS here, because, in the end, that's just the kernel, and a bunch of really basic tools. There's no meaningful parallels to make to Windows or OS X here. You have to take kernel+DE, and at that point - yes, GStreamer is an "OS service" as far as application developers are concerned.

      Maintenance and debugging holds, sorry. I'm sure they have a bunch of experimental features floating in the trunk, so?

      We're not talking about trunk or experimental builds. We're talking about shipping code. GStreamer support is enabled in Fennec already. They haven't shipped a stable release with it yet, so far as I know, but if it's in Fennec alphas (and will ship in next release), there's no reason for it not to be in Firefox alphas.

    199. Re:HTML5 Video by Rockoon · · Score: 1

      WTF. Flash didn't get any h264 support until flash 9, long after online video was popular.

      The moment H.264 was a viable delivery method, everyone began switching, because if they didnt switch but their competitors did.. they would be fucked hard by offering less quality at higher costs. The landscape is littered with failed video sites.

      Even now, sites like Hulu are struggling to be profitable. Downgrading codecs would kill them almost instantly.

      --
      "His name was James Damore."
    200. Re:HTML5 Video by Matthieu+Araman · · Score: 1

      You can install locally a linux dvdrom (or repository copy)
      that would make your install working without having Internet.

      BTW, on Windows, I remenber having Office and Windows asking for network installation disk. If you didn't copy the installation disk locally, you've got the same kind of problem. (this is why most people select install everything to avoid being popuped while typing something into word because the software suddenly tries to install a language pack which you don't use...)

      You obtain a lesser memory print on Linux by sharing libraries, which is more difficult on Windows, especially for non microsoft software.

    201. Re:HTML5 Video by Pentium100 · · Score: 1

      Buy SuSE every now and then, I think they still sell those.

      Then I can buy Windows. We use Linux in the office only because it is free (as in $0). If Linux was priced around the same as Windows or only slightly cheaper then we would use Windows, and we wouldn't need Ultimate edition.

    202. Re:HTML5 Video by Matthieu+Araman · · Score: 1

      Yes, you can offer multiple format. You nevertheless need to have both file ready on the server side...

    203. Re:HTML5 Video by evilviper · · Score: 1

      No, they can't, in fact. It would no longer be RAND. Not to mention it would render all exisiting chips and device worthless, which would cost them dearly. It's a ridiculous attempt to justify a nonsensical stance.

      Patent licenses for codecs in the US is something of an issue, but there are numerous options there, even if not ideal, and everyone outside the US should not be penalized...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    204. Re:HTML5 Video by Matthieu+Araman · · Score: 1

      Google (so youtube) recently bought the codec company, which codec they used.
      so they are in a position which allow them to open up this codec (or a new codec ?), which would make one more open codec available.

    205. Re:HTML5 Video by Pentium100 · · Score: 1

      BTW, on Windows, I remenber having Office and Windows asking for network installation disk.

      At least on Office 2003, if you install from a CD, the setup copies the install files to the hard drive, you can uncheck the checkbox and save some space though.

      "Lesser memory print" - is this RAM or HDD? If RAM then doesn't Windows only load one copy of one particular .dll version for all apps to use? If HDD then I'd rather lose a gigabyte of space than have to hunt for the libraries.

      When you install a Windows app that needs some .dll it installs the .dll (which is included in the setup.exe). If Windows already has the exact same .dll then an additional copy is not installed, if Windows has an an incompatible version of the .dll then the additional copy is installed and apps can choose which one they use.

      On Linux it seems that only one copy of a lib can exist, so if two apps want two different incompatible versions of the same lib you can only use one app at a time. Also, apps do not include their dependencies in their install.rpm or whatever, meaning that the app is incomplete.

    206. Re:HTML5 Video by Korin43 · · Score: 1

      What Mozilla wants is for h264 to not be used in the video tag (theora or nothing). They've already failed at that and they're not going to change people's minds. The thing they might be able to win at is getting other browsers to support theora and vorbis (and h264).

    207. Re:HTML5 Video by LWATCDR · · Score: 1

      "The problem is that Quicktime and DirectShow don't support theora or vorbis by default, so hopefully Mozilla/Wikipedia/anyone else who cares can get them popular enough that Microsoft and Apple have to finally support some free codecs."
      They don't need to. Directshow and Quicktime are expendable. Microsoft doesn't need to support Theora.
      Mozilla could just include these codecs in their installs.
      http://www.xiph.org/dshow/
      And for Mac
      http://www.xiph.org/quicktime/
      So it is an none problem
      Next issue?

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    208. Re:HTML5 Video by muyshiny · · Score: 1

      video codec is spit in the ocean, agreed. the libraries are out there, anyone can encode/decode. the problem i was trying to address is the one you exhibit: the attitude that it's silly/futile/a waste trying to keep the platforms used for global information interchange as open and flexible as possible.

      your strawman concept of 'illuminati' and 'crazy' as a response to my preference for openness is especially typical and grating. yes, clearly anyone concerned about the elite is crazy. uh huh. because there's no such thing as abuse of power and we have a long history of egalitarian rule and authoritarian regimes are a thing of the past and will never happen to us anymore because we're free, free, freeeee... and rich. and always will be?

      just wow.

      okay, how about this: think of the societies that exist and have existed. think about which ones you'd prefer as a model for humanity's future and what you might do to promote the kinds of things that requires.

      me, i happen to enjoy my individual freedom. i think having, effectively, everyone as part of the media and being able to put things out there for a global audience with little in the way helps protect that. it's like the aclu but even better! especially since the media has ipo'd and forgotten its job. any little effort in support of free/open/transparent/decentralised/lower barriers to entrepreneurship and competition... to me those are tiny steps towards maybe getting to hold onto this bizarre cultural anomaly for another decade or two. maybe even a whole century if we're lucky. so i applaud the people that do it. cheer for them even.

      it doesn't matter if you use exclusively closed software and always get the longest contract from your mobile provider. we don't care. but don't belittle the efforts of the people that have got your back, they need all the good pr they can get---as you sort of point out?

    209. Re:HTML5 Video by FrankieBaby1986 · · Score: 1

      Because since it is FOSS, there is NO EXCUSE for Internet Explorer or anyone else to implement it. I have no problem with sites using x264 (I would prefer theora), i am willing to pay a few bucks for Firefox if it mean it would come with x264 support AND theora.

      At this point, everyone wins. At the very least, EVERYONE could play the theora in some fashion, so then it will be up to individual sites to decide. Thus why Wikipedia and OVA are trying to tilt the numbers toward theora.

      --
      ERROR: SIG NOT FOUND (A)bort, (R)etry, (F)ail?:
    210. Re:HTML5 Video by petermgreen · · Score: 1

      BTW debian provide full DVD sets of their main repositry that can be used with apt.

      there aren't any CD images of contrib or non-free but if you download them with debmirror I think everything in contrib and non-free for an architecture will fit on one dvd.

      I think ubuntu do a dvd of main too but unlike debian ubuntu have a fairly small main section and I don't think they do any media of universe.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    211. Re:HTML5 Video by petermgreen · · Score: 1

      Same for security updates.
      On a system with centralised update management (e.g. most Linux distributions) I would agree with you less code duplication makes security updates easier. For this reason you will find the likes of debian making substantial effort to make software build with the system copies of libraries rather than it's own embedded copies.

      On windows OTOH most people won't update software unless it comes with it's own system for nagging them to do so, it is free to do so and they can see an obvious reason for doing so (Sometimes they won't do it even then).

      IMO exposed components shipped as part of firefox have a FAR greater chance of getting security updates in a tiny manner than exposed components installed by some install and forget codec pack.

      Even ignoring the political side of things i'm really not sure exposing every crappy codec a user happens to have installed (of which even on linux some of which may have been installed outside of the repositry system) to malicious websites is such a good idea.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    212. Re:HTML5 Video by LWATCDR · · Score: 1

      Really? I mean are you trying to say that the risk that somebody may not update a codec is worth not using the OSs modular codec system? The same system that every video player already uses?
      And as you have pointed out that on Linux it really isn't an issue unless the end user goes out of their way to install from an iffy repository.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    213. Re:HTML5 Video by shiftless · · Score: 1

      Wikipedia and Mozilla are "big players"? Exactly how much money do these two organizations make per year?

      You're damn right Theora needs to be technically better if it wants to have a prayer of succeeding. Companies are going to use what's standard, and right now H264 is standard. There is all kinds of industry support for this codec. There isn't a fucking thing for Theora, AND Theora is a technically inferior codec. Why the hell would any sane company (i.e. one focused on the idea of making money) prefer to use Theora over H264?

    214. Re:HTML5 Video by Korin43 · · Score: 1

      I'm entirely aware that Directshow and Quicktime have codecs for them, but that's not the issue. The problem is that they don't support Theora or Vorbis by default, so h264 + aac/mp3 will be the only viable format ("Yeah we could use Vorbis, but 50% of our users won't be able to see it"). What Firefox installs doesn't matter because people running IE9 (as their primary browser) aren't going to have Firefox installed.

      Maybe you're getting at how Mozilla could use Directshow and Quicktime on those platforms, and I agree, but that's not the real issue.

    215. Re:HTML5 Video by Matthieu+Araman · · Score: 1

      Windows :
      Ok, looks like recent setup wizard are intelligent enough to not reinstall the same dll twice (or override a newer dll)
      but if application A install DLL version 1.03 in its own directory and system has DLL 1.02, then there will be two dll loaded in memory, one for appli A, one for other applis using the lib...

      Linux(and Unix) :
      version number are part of the file name, which mean you can have several versions in the same directory without overrriding by error a newer version.
      you can have libc.so.1.12.3, libc.so.1.13.4, libc.so.2.0.0
      APP A can link with libc.so.1 and so will use libc.so.1.13.4 in reality
      APP B can link with libc.so.1.13 -> will use automatically libc.so.1.12.3
      APP C can link with libc.so -> will use latest, libc.so.2.0.0
      I think windows should copy and put the dll version in the file names and not just inside the file.

      On windows, an app can install a DLL/lib not part of the application
      On Linux, an app can't install something not part of the app but will have a dependancy on it.
      the setup manager is part of the os, not provided by the app and will automatically try to install dependancies.
      it will also forbid to desinstall a lib used by an application.
      I think it's much more powerfull even if this require to not have everything packaged in the app installer.

    216. Re:HTML5 Video by lennier · · Score: 1

      But why should the average user be quite in some stupid ideological fight when they are never going to be paying for the H.264 royalties that Microsoft, Apple and Google will be shelling out to include H.264 support in their browser?

      It's not ideology, it's law. If patents didn't make distributing H.264 illegal then it wouldn't be a problem. It's not the open-source projects who are being nitpickers; they run the risk of going to jail if they don't.

      But you're right, the average user doesn't seem to care about abiding by law when it comes to software.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    217. Re:HTML5 Video by lennier · · Score: 1

      video codec is spit in the ocean, agreed. the libraries are out there, anyone can encode/decode.

      Not legally they can't.

      Or do you not care about obeying the law?

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    218. Re:HTML5 Video by lennier · · Score: 1

      Last I checked, it was not illegal to purchase a properly licensed GStreamer H.264 codec, and use that. The cheapest bundle including H.264 from Fluendo would cost you 28 euro.

      Then it would be illegal to redistribute that operating system. Game over, end of story, thank you for playing the Open Source game but you lost.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    219. Re:HTML5 Video by lennier · · Score: 1

      No-one said that it is.

      The point is that browser remains FOSS. If user is a FOSS purist, he doesn't install the "evil" codecs, and doesn't go to websites which only provide H.264 streams.

      That's fine. Just don't consider H.264 any kind of 'standard', since it's evidently not.

      And it's not an 'evil' codec - just an illegal one to redistribute. If it weren't illegal (patented) then we wouldn't even be having this conversation. But it is, and because it's illegal to distribute in a free operating system, it should not be a standard.

      Because stop me if this sounds strange, but generally speaking, complying with standards should not require people to break the law.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    220. Re:HTML5 Video by countach · · Score: 1

      If Google or any big company wanted to change the game, all they have to do is throw some money at whoever owns the h264 patents, and buy them out to open it up.

    221. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      That's fine. Just don't consider H.264 any kind of 'standard', since it's evidently not.

      A format specified by an international standards organization is not a standard?

      And it's not an 'evil' codec - just an illegal one to redistribute.

      It's not illegal to redistribute. You can distribute up to 100,000 encoders or decoders per year, legally, without a license. You'll need to pay if you want to distribute more than that, but as soon as you do, it is not illegal to redistribute.

      Then also, in many (most?) countries in the world (U.S. being a notable exception), software patents are invalid, so it's not illegal to redistribute in any quantities.

      Because stop me if this sounds strange, but generally speaking, complying with standards should not require people to break the law.

      Complying with that standard does not require you to break the law. At most, it requires you to pay.

    222. Re:HTML5 Video by shutdown+-p+now · · Score: 1

      Did I say anything about redistributing with the OS? Did you even read messages higher up the thread? This one is about giving the end user a choice in the matter of codecs, and has no relevance whatsoever with either OSS nor redistribution.

    223. Re:HTML5 Video by Anonymous Coward · · Score: 0

      Ah, but the user is not paying if they use Chrome, because they're not paying for the OS (when that finally comes out)

    224. Re:HTML5 Video by arose · · Score: 1

      Ah, I see, that's the only outcome I passionately care for as well. If I can post videos without having to worry about either patents or playback problems then I have won. Of course strictly pushing for one option seems to be about the only way to possibly meet in the middle, so I'm not upset about Mozilla's approach to this one any more then about RMS.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    225. Re:HTML5 Video by quadrox · · Score: 1

      Way to miss the point troll.

      Nobody is denying that MS did *something* right in order to get to where they are. Parent was arguing about technical merits however, and windows certainly wasn't ahead on that score.

      windows had better marketing, foul play, and maybe (just maybe) it even ran on cheap pcs and had more backward compatibility. However, none of these are *technical* merits, which parent was quite obviously talking about.

    226. Re:HTML5 Video by LWATCDR · · Score: 1

      Well getting Safari and IE to default support Theora isn't possible right now.
      Sites like wikipedia and others that use Theora could link to the codec and then people could install it.
      The real issue is that the W3C did not declare that the Theora is the the standard codec for web video.
      The other real issue is that Mozilla is digging in their heals and refusing to support H.264 which makes going to HTML5 difficult at best.
      IE and Safari are only going to support H.264
      Firefox is only going to support Theora.
      Google Chrome is going to support both.
      And I think Opera is going to support both.
      That leaves web developers with a choice.
      They can support H.264 and leave Mozilla users out in the cold.
      They can support Theora and leave IE and Safari users out in the cold.
      They could do a browser detection hack and have two copies of each video.
      Or they can keep using Flash.
      None of these options are optimal.
      Others have suggested that Mozilla can not support H.264 because of licensing costs which it not true.

      Your statment was "The problem is that Quicktime and DirectShow don't support theora or vorbis by default, so hopefully Mozilla/Wikipedia/anyone else who cares can get them popular enough that Microsoft and Apple have to finally support some free codecs."
      Well lack of native support isn't an issue because Firefox can just install the codec when you install the brownser.
      There is no technical problem with Firefox using the OS video subsystem for Video Codec support.
      But Firefox NOT supporting H.264 will not force Microsoft and Apple to support Theora. All it will do is hurt the adoption rate of HTML 5 Video and help keep Flash as the standard for web based video.
      And in the end hurt end users all for taking a political stand.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    227. Re:HTML5 Video by evilviper · · Score: 1

      it even ran on cheap pcs and had more backward compatibility. However, none of these are *technical* merits

      Yes, yes they are.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    228. Re:HTML5 Video by michaelhood · · Score: 1

      I've long felt that silly things like this is what holds open source software back from mainstream assistance. It's just a personal view and you can disagree all you like and try to educate me to your view, but in the end, it's not worth the effort put into it because there are better things to worry about.

      A thousand times this.

    229. Re:HTML5 Video by TheTurtlesMoves · · Score: 1

      Its RAMD as long as everyone gets charged the same amount and is forced to play by the same rules. If the original contract includes "revisions" clause they really can. Be carfull what you sign, and that includes contracts with MPEG-LA. Dam just look at the mpeg-2 licenses.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
  2. Quit embeding the codec support in the browser by Anonymous Coward · · Score: 4, Insightful

    Let the OS handle it, and let the browser interact via plug-ins.

    It's really not that complicated.

    1. Re:Quit embeding the codec support in the browser by mattventura · · Score: 1

      Good for technical people, but some people don't know how or don't want to install those plug-ins. If I wanted to watch videos through the use of a plug-in, then flash works perfectly fine for that.

    2. Re:Quit embeding the codec support in the browser by Pojut · · Score: 1

      If people have the technical chops to install something like flash, why wouldn't they have the technical chops to install something else? Or better yet, just have the browser install it automatically when the browser itself gets installed.

    3. Re:Quit embeding the codec support in the browser by jedidiah · · Score: 1

      If the OS isn't handling your plugins for you then it is lame and you should drop it for something more sophisticated and less user hostile.

      The kind of pseudo-code we're talking about here isn't exactly rocket science (or video compression).

      Although having a proper package manager certainly helps.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:Quit embeding the codec support in the browser by Lunix+Nutcase · · Score: 1

      So you claim that people don't want or can't figure out how to install a plugin for playing HTML 5 video but are somehow able to install Flash?

    5. Re:Quit embeding the codec support in the browser by sopssa · · Score: 1

      It's not like it's really hard for a browser to provide links to those downloads. Whatever the results will be, we will have at most H.264 and Theora. H.264 is already included in any recent Windows and Mac OS X (Linux users probably can figure out how to install it on their own). Only thing a browser needs to do is provide a download link to Theora, if it ever does catch on.

    6. Re:Quit embeding the codec support in the browser by Lunix+Nutcase · · Score: 1

      If the OS isn't handling your plugins for you then it is lame and you should drop it for something more sophisticated and less user hostile.

      Yes because no one has to install plugins in Linux, right?

      Although having a proper package manager certainly helps.

      Why do you need a package manager when browsers have been facilitating the easy installation of plugins, such as Flash, for years now?

    7. Re:Quit embeding the codec support in the browser by mattventura · · Score: 1

      You're misreading my post. I wasn't saying that having plug-ins for the video was better/worse than a flash plugin, I was saying that there is a better way to do that. The flash part was only there to show that having plug-ins for video formats is just as bad as flash.

    8. Re:Quit embeding the codec support in the browser by Abcd1234 · · Score: 5, Insightful

      Why do you need a package manager when browsers have been facilitating the easy installation of plugins, such as Flash, for years now?

      Because the point is the browser shouldn't need *any* codec-specific plugins at all. The browser should simply use the existing mechanisms in the operating system or desktop environment for performing video decoding. On Windows that means DirectShow, and on Linux that means gstreamer. Codec installation is then a task for the operating system or package manager. The result is a better experience for the user, and a simpler implementation for the developers, as they need only to interface to a generic video backend, rather than incorporating a completely codec stack into the browser.

      'course, this kind of reasonable design decision would get in the way of pointless political posturing, and who really wants that?

    9. Re:Quit embeding the codec support in the browser by tepples · · Score: 1

      If the OS isn't handling your plugins for you then it is lame

      What happens when your operating system handles plugins for the user but reminds the user: "If you click Install, and you live in the United States, you are breaking the law." ? Ubuntu does exactly this for the gstreamer-plugins-ugly package.

    10. Re:Quit embeding the codec support in the browser by Abcd1234 · · Score: 1

      What happens when your operating system handles plugins for the user but reminds the user: "If you click Install, and you live in the United States, you are breaking the law." ? Ubuntu does exactly this for the gstreamer-plugins-ugly package.

      Uh, good. That's *precisely* how this should be handled. The user should be warned of the issues with installing the codec, and then given the choice to continue. Eliminating this choice is completely antithetical to the very concept of free software.

    11. Re:Quit embeding the codec support in the browser by natehoy · · Score: 2, Insightful

      You pirate a clip of "Beavis and Butt-head" snickering and muttering "heh heh, breaking the law" to listen to while you download it.

      Or you support sites that use open standards.

      Or you buy a license for each of the proprietary standards that "plugins-ugly" provides. There's a reason it's called "ugly", and it's not just a lack of rugged good looks.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    12. Re:Quit embeding the codec support in the browser by Anonymous Coward · · Score: 0

      Why? Browsers don't let the OS handle HTML rendering and image decompression either. This would just cause unnecessary platform dependencies. These things belong in (ideally, portable) libraries, for example libavcodec for audio/video. Whether these libraries have to be bundled with the browser, or can shared among applications and handled by some package management depends on the OS, but doesn't really matter.

      Plugins were a stupid idea from the beginning and still cause a lot of problem in browsers; for example by breaking keyboard shortcuts. I hope than one day we can forget about browser plugins altogether.

    13. Re:Quit embeding the codec support in the browser by ObsessiveMathsFreak · · Score: 1

      Let the OS handle it, and let the browser interact via plug-ins.

      We tried that. It didn't work.

      --
      May the Maths Be with you!
    14. Re:Quit embeding the codec support in the browser by h4rr4r · · Score: 1

      Because then you end up with the hell that is windows software updaters?

      Stop trolling nimrod.

    15. Re:Quit embeding the codec support in the browser by shutdown+-p+now · · Score: 1

      I assume you mean <object>. It never worked because 1) there were too many codecs in practice, and 2) there was no standard interface to interop with the embedded player from JavaScript on the page. HTML5 video fixes the latter, and as for the codecs, we're down to H.264 and Theora now.

    16. Re:Quit embeding the codec support in the browser by Anonymous Coward · · Score: 0

      Because the point is the browser shouldn't need *any* codec-specific plugins at all. The browser should simply use the existing mechanisms in the operating system or desktop environment for performing video decoding. On Windows that means DirectShow, and on Linux that means gstreamer. Codec installation is then a task for the operating system or package manager. The result is a better experience for the user, and a simpler implementation for the developers, as they need only to interface to a generic video backend, rather than incorporating a completely codec stack into the browser. 'course, this kind of reasonable design decision would get in the way of pointless political posturing, and who really wants that?

      Sun/Oracle, apparently. (JavaFX's media player uses the operating system's mechanisms -- though it also makes VP6 available just in case). But that doesn't get you away from needing a plug-in to begin with.

    17. Re:Quit embeding the codec support in the browser by jonwil · · Score: 1

      1.Windows XP (and probably Windows Vista although I am not sure) dont ship H.264 with the OS. Windows 7 does but you cant rely on that. Getting a H.264 codec that can work on XP is not simple (I have tried and still cant find one that works)
      2.A number of linux distros (mainly the more "commercial" ones like SLED and RHEL) ship builds of libraries like FFMPEG that have all the patented codecs disabled to avoid being sued. In some cases you can get the codecs from a repository but again you have to have the user specifically install it.
      3.Mobile devices may not contain H.264 decoders or if they do, may not make them available for 3rd parties and browsers to use.

      Other codecs such as VC-1 and Theora have even less OS support.

    18. Re:Quit embeding the codec support in the browser by jareth-0205 · · Score: 1

      Let the OS handle it, and let the browser interact via plug-ins.

      Really? Extend that back, would it be better if there was no JPG renderer, and that was handled by a plugin? GIF too? PNG? All separate from the browser? For a consistent and performant experience, having stuff integrated is good...

    19. Re:Quit embeding the codec support in the browser by Anonymous Coward · · Score: 0

      Why do you need a package manager when browsers have been facilitating the easy installation of plugins, such as Flash, for years now?

      If you can't work out by now what the problems are of having a browser able to install software there's no helping you. If the OS by default had no execute permissions on user accessible directories it would virtually eliminate drive by installations of malware. This would not prevent package managers working or passing a program to the shell as input, so installation could still be easy for the user (social engineering would not be prevented).

    20. Re:Quit embeding the codec support in the browser by donatzsky · · Score: 1

      May I suggest CCCP. I don't think I've had any problems after installing that (although it's always a good idea to have VLC around - just in case).

    21. Re:Quit embeding the codec support in the browser by RogerWilco · · Score: 1

      I agree. It would also mean that I don't have to install the same codec for each application that I use. Once I've installed support for Theora, I'd like it if everything that can play video's can now play those as well. It would be a pain to wait for each application implementing it's own patch or plug-in.

      --
      RogerWilco the Adventurous Janitor
    22. Re:Quit embeding the codec support in the browser by RogerWilco · · Score: 1

      Yyes, I'd actually prefer that. Then if I'd installed PNG support in my OS, all of a sudden each and every image manipulation program I have would support it. I can think of other areas where such an approach would help, say word processors,...

      --
      RogerWilco the Adventurous Janitor
    23. Re:Quit embeding the codec support in the browser by Abcd1234 · · Score: 1

      Not to mention the follow-up upgrade issue. What if Firefox incorporates an old version of Theora? Suddenly I have to upgrade both the gstreamer codecs *and* Firefox? That's just flat out ridiculous.

    24. Re:Quit embeding the codec support in the browser by Simetrical · · Score: 1

      Let the OS handle it, and let the browser interact via plug-ins.

      It's really not that complicated.

      It's not that simple. HTML5 video is first-class HTML content. It has to interact with CSS and JS, including potentially things like rotations, other things overlapping it, resizing, etc., and all of these things changing at any time due to script. Who says the OS is going to expose an API complicated enough to support all of HTML's features?

      In fact, notice that every browser that supports >video> uses a library entirely under their control. Firefox uses libtheora and is contemplating GStreamer (at least for mobile); Chrome uses ffmpeg; Safari uses QuickTime; Opera uses GStreamer. In every case, it's either open-source, or developed by the same company. No one is relying on OS support except arguably Apple, and that only on Mac, which they control. Because OS support isn't good enough.

      Disclaimer: I'm not a browser developer, but I do hang out around them a lot. :)

      --
      MediaWiki developer, Total War Center sysadmin
  3. Killer App? by wjousts · · Score: 4, Insightful

    I'm not sure I see Wikipedia as being the "killer app" for video standards. I'm not sure how many articles would be really enhanced by the addition of video, baring in mind that video would need to be licenced under CC or similar, so clips of TV shows / films would probably be out.

    To take a random example (today's featured article) . I'm not sure what video you could usefully add to that article? Especially since somebody who died in 1938 probably isn't featured in many video clips.

    1. Re:Killer App? by DragonWriter · · Score: 1

      I'm not sure I see Wikipedia as being the "killer app" for video standards. I'm not sure how many articles would be really enhanced by the addition of video, baring in mind that video would need to be licenced under CC or similar

      This assumption seems flawed. Wikipedia prefers open licensed content for images, but will accept non-open content with a fair use rationale. Presumably, the same would be true of video clips.

    2. Re:Killer App? by Anonymous Coward · · Score: 0

      I'm not sure how many articles would be really enhanced by the addition of video, baring in mind that video would need to be licenced under CC or similar,

      Your Freudian slip gives me an idea.

    3. Re:Killer App? by Anonymous Coward · · Score: 0

      Who said "killer app"?

      Anyway the same things could be said about images or audio in Wikipedia.

    4. Re:Killer App? by Jay+L · · Score: 1

      Besides, if video on Wikipedia is anything like images on Wikipedia, when you click on it, it won't play the video. Instead, it'll take you to a page of details about the resolution, frame rate, codec, etc. On that page will be a bunch of text links that take you to a page that plays the video.

    5. Re:Killer App? by Anonymous Coward · · Score: 0

      I'm not sure I see Wikipedia as being the "killer app" for video standards.

      It's not. It's a "not dead yet" app for videostandards. It's a very public stand for awareness of un-encumbered codecs, and even that there is something called "open source" & attendant controversies that affect public use of the web.

      Which is terrific. Open video codecs are just going to be sidelined if only some developers are aware. The problem needs to be publicized, and Wikipedia is an excellent foothold due to both broad use and closely partnered philosophy.

    6. Re:Killer App? by city · · Score: 1

      Really? I think this would a perfect article for video. Any video taken of this person would be in the public domain by now. Is there any video out there? I have no idea, but this kind of video doesn't preach to the youtube crowd so where else would you find it online? It's easy enough to find his picture. Wikimedia.org has becom a repository for these types of pictures, you just need to cite the National Library of Australia as its source. This is exactly where wikipedia excells, getting all the library's public domain pictures from all over the world scanned and publish, why couldn't they do the same with public domain video and become a repository for it? There's got to be video of this guy out there somewhere, he's an explorer, that's what they do, get documented going somewhere. Unfortunately it's probably in a vault somewhere.

      --
      I am a v1ral sig. Plse c0py me and h3lp me spread. Thank y0u?
    7. Re:Killer App? by Anonymous Coward · · Score: 0

      I recommend videos of blending of every single physical item listed on Wikipedia.

    8. Re:Killer App? by Xyrus · · Score: 2, Insightful

      Agreed. Porn is. So putting porn videos on wikipedia would be the killer app.

      Natalie Portman, naked, petrified, hot grits, now featured on the Elemental Chart on wikipedia. Nerd nirvana. Or if your feeling less pure, Mila Jovavich naked and shellacked, covered in hot corn nuts doing a spread on the Actinide series. Though really, she's been naked in so much I don't even think that's porn anymore.

      ~X~

      --
      ~X~
    9. Re:Killer App? by mcrbids · · Score: 1

      I'm not sure I see Wikipedia as being the "killer app" for video standards.

      I'm not sure that you see just how big Wikipedia actually is. It's not just a big driver of traffic, it's farking huge. According to Alexa, It's number 6 worldwide, after Google, Facebook, Yahoo, Youtube, and Live.com. Wikipedia pulls an astonishing 12-13% of users worldwide!

      For comparison:

      MySpace is #18, with 3% reach.

      Twitter is #12, with 5% reach.

      Slashdot is #1,262, with 0.1% reach.

      Whatever you do, don't underestimate the gravity of this news - Wikipedia is one of the Internet TITANS!

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    10. Re:Killer App? by Anonymous Coward · · Score: 0

      Mhhm on the other hand, I am sure video will be really useful to improve the quality of other certain articles.

  4. And... by Lunix+Nutcase · · Score: 3, Insightful

    And Google, Microsoft and Apple give out a collective *yawn*. Youtube has more traffic than Wikipedia so if Google is pushing H.264 through there it will have far more impact than Wikipedia. Not to mention that Facebook, who also has more traffic than wikipedia and also youtube, also uses H.264 for its video.

    1. Re:And... by Anonymous Coward · · Score: 0

      Why care? Seriously - is the performance *that* greater that you feel the need to support a commercial enterprise leeching your money over a perfectly free way? I guess it's the "wah! I want in NOW! don't make me wait 0.5 seconds longer!" mentality...

    2. Re:And... by justinjstark · · Score: 2, Insightful

      HTML5 video codec support is not a dichotomous decision. There can be multiple supported video codecs for the video tag just like there are multiple supported image formats for the img tag. Larger sites like Wikipedia supporting only theora will encourage other companies to add support for theora in their browsers...not replace H.264.

    3. Re:And... by shutdown+-p+now · · Score: 2, Interesting

      Those supporting Theora argue that, unless Theora is the video codec for the Net, some people (e.g. Linux users in U.S. not willing to break the law) will be restricted from large parts of the Net that will go H.264-only.

      It's why Mozilla refuses to just use GStreamer codecs for HTML5 video in mainline builds, for example.

    4. Re:And... by Anonymous Coward · · Score: 0

      And Google, Microsoft and Apple are wrong. HTML5 isn't a proprietary, pay-for-use standard, why should video used by HTML5 be?

      It's that simple, logical, non-nonsense concept that somehow goes over the head of these companies and the people who have been conned into supporting them. Use H.264 for your own videos played in your own video player, but on the web, Ogg Theora or shut your goddamn greedy mouth.

    5. Re:And... by Anonymous Coward · · Score: 0

      Those supporting Theora argue that, unless Theora is the video codec for the Net, some people (e.g. Linux users in U.S. not willing to break the law) will be restricted from large parts of the Net that will go H.264-only.

      Shame on them. Nonsensical laws are there to be broken.

      No, really.

    6. Re:And... by Trogre · · Score: 1

      So what? McDonalds has a lot more traffic through than Blockbuster. And Bed, Bath & Beyond have more monthly sales than Max's Mercedes Motors.

      They're different entities serving completely different purposes.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    7. Re:And... by Luke+has+no+name · · Score: 1

      Woe is Wikipedia, it's only the sixth most visited site and youtube is fourth.

      http://www.alexa.com/siteinfo/wikipedia.org
      http://www.alexa.com/siteinfo/youtube.com

      What we really need is Facebook and the 'adult' tube sites to support open video.

    8. Re:And... by Anonymous Coward · · Score: 0

      At this point you are already breaking the law if you listen to mp3 or watch DVDs. Unless you download pirated copies converted to patent-free codecs.

      Mozilla can use gstreamer for all the patent-free codecs and then each user can install the illegal codec themselves from a freer country.

      Illegal? Nothing is illegal if they do not catch you.

    9. Re:And... by Anonymous Coward · · Score: 0

      Nobody cares about lin-sux users except the freetards the continue to use lin-sux while better options like OS X are available.

    10. Re:And... by MtViewGuy · · Score: 1

      Because YouTube is now primarily H.264, I think Google--who owns YouTube and is one of the big proponents for HTML 5.0--will end up making H.264 as the primary video codec standard for HTML 5.0.

    11. Re:And... by Anonymous Coward · · Score: 0

      Those supporting Theora argue that, unless Theora is the video codec for the Net, some people (e.g. Linux users in U.S. not willing to break the law) will be restricted from large parts of the Net that will go H.264-only.

      You don't understand the issue. It's not about Theora versus H.264. It's about open video versus closed video. The web is built on open formats and open protocols. There is no reason for video to be any different. YouTube will move to open video sooner rather than later. Here's an excerpt from Google's point of view on open standards:

      "So if you are trying to grow an entire industry as broadly as possible, open systems trump closed. And that is exactly what we are trying to do with the Internet. Our commitment to open systems is not altruistic. Rather it's good business, since an open Internet creates a steady stream of innovations that attracts users and usage and grows the entire industry."

      Google is one of the biggest technology companies because they understand the value an open internet. You'll come to understand this too.

    12. Re:And... by shutdown+-p+now · · Score: 1

      I suspect that H.264 is "open enough", as far as Google is concerned (which is why they are tacitly backing it). It's a standard, its spec is freely available, so no lock-in and no interop problems or the need to reverse engineer stuff. Yeah, there is a licensing fee, but have you looked at the terms? Heck, it's actually free for <100,000 encoders/decoders shipped annually; and the rates are very reasonable above that level. It's definitely not something that would cause a significant barrier to entry.

      Oh, and "web was built on open standards"? Was it, really?

    13. Re:And... by arose · · Score: 1

      I'm more worried about all browsers being able to play Theora, so I don't have to worry when I use video on my site.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    14. Re:And... by Pecisk · · Score: 1

      Google is somehow partly in this - Chrome supports Theora, but YouTube not (yet). I think one day it will.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    15. Re:And... by Anonymous Coward · · Score: 0

      I suspect that H.264 is "open enough", as far as Google is concerned (which is why they are tacitly backing it).

      If it was, then they wouldn't have bought On2 Technologies. From Google's acquisition announcement:

      "We're excited to welcome the On2 team to Google and to continue to enhance the video experience for users on the web," said Sundar Pichai, Vice President of Product Management at Google. "Through rapid innovation in browsers and web standards, the Internet is becoming the leading platform for development. We believe On2's engineering talent and technology will be an incredible asset for us as we work to improve this platform."

      Interesting, isn't it. I think your problem is you're not thinking big picture. Google, on the other hand, is.

    16. Re:And... by shutdown+-p+now · · Score: 1

      Well, I know that:

      1. Chrome ships with H.264.

      2. YouTube HTML5 demo streams H.264.

      3. Google was arguing against making Theora the universally supported codec for HTML5 video on the W3C committee.

      All of the above clearly seem to point at Google being content with H.264 at least for the time being, open or not. It may be that they have some different long-term future plans, but short-term the picture is rather clear.

    17. Re:And... by Anonymous Coward · · Score: 0

      1. Chrome ships with H.264.

      2. YouTube HTML5 demo streams H.264.

      Yes, YouTube encodes video in H.264 today. YouTube even uses Flash of all things. We aren't talking about what YouTube does today. We're talking about what YouTube will being doing tomorrow.

      3. Google was arguing against making Theora the universally supported codec for HTML5 video on the W3C committee.

      And yet Chrome supports Ogg Theora playback. Again, it isn't about Theora specifically. It's about open video as opposed to closed video. If you want a prognostication on how Google will package their open video, I'd guess VP8 video with Vorbis audio in an Ogg container. Ogg and Vorbis are already widely supported so all they'd need to do is put VP8 in Ogg.

      All of the above clearly seem to point at Google being content with H.264 at least for the time being, open or not. It may be that they have some different long-term future plans, but short-term the picture is rather clear.

      The "long term" isn't going to be all that long. IE is the last major browser that doesn't support HTML5 video. IE9, which does support HTML5 video, will be released in, say, 9 to 12 months time. Google is highly likely to make open video available on YouTube prior to IE9's release to give Microsoft time to add support for it out of the box.

      In the meantime, some large sites are already using open video and more will follow.

    18. Re:And... by shutdown+-p+now · · Score: 1

      Yes, YouTube encodes video in H.264 today. YouTube even uses Flash of all things. We aren't talking about what YouTube does today. We're talking about what YouTube will being doing tomorrow.

      Don't you think that YouTube HTML5 beta is a pretty good indication of what they will be doing tomorrow?

  5. the non-free part isn't so bad by Protonk · · Score: 3, Insightful

    WP should just adopt html5 and give up on the FOSS posturing for once. We already relented on the issue of fair use media--limited use for copyrighted material. Patent protected material seems like a better place to compromise more widely because patents don't live forever. After ~14-21 years, the content path is free. If WP does plan to be around "forever", that isn't too long a time to wait.

    1. Re:the non-free part isn't so bad by jedidiah · · Score: 1

      It's really not a problem. The commercial desktop operating systems are supposed to have all sorts of stuff to handle the "scary technical details" here. WP should be able to offer video in any format they like. They could even host some of the relevant bits of system software and web browser glue-ware.

      Histrionics over strange data formats is so 90s.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:the non-free part isn't so bad by arose · · Score: 1

      They have. HTML5 doesn't specify a codec, so Theora is as valid (as far as W3C is concerned) as any other.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    3. Re:the non-free part isn't so bad by bersl2 · · Score: 1

      Question: Do you believe that, if what Wikipedia itself currently says about the subject is correct, various MP3 patents ought to persist into at least 2012 and possibly as late as 2017? If not, when do you believe all patents covering its design and implementation should expire or have expired?

      I think that if we are to allow patents on algorithms, not only should obviousness standards be rigorously enforced (including the appropriate appropriations from Congress to make it happen), but that we should be talking about terms of no more than 5-7 years. And even then, I would like there to be less time than that.

    4. Re:the non-free part isn't so bad by betterunixthanunix · · Score: 1

      Except that patent encumbered codecs make it difficult for some users to create or view content *now,* which is the problem. Wikipedia is supposed to be for everyone, including people who cannot obtain patented codecs (such people do exist), both for viewing and for creating the videos. I would certainly not encourage Wikipedia's users to violate patent law in their respective localities -- the last thing Wikipedia needs is a lawsuit to deal with.

      It is not a question of compromise, it is a question of the goal of Wikipedia, which is to be as accessible as possible.

      --
      Palm trees and 8
    5. Re:the non-free part isn't so bad by OverlordQ · · Score: 3, Informative

      They could even host some of the relevant bits of system software and web browser glue-ware.

      It does already. Wikipedia uses the OGGHandler extension which tries to determine automagically what method for displaying video the client supports. It supports attempting to use the following clients:

      • Cortado (bundled Java applet)
      • VLC
      • QuickTime with XiphQT
      • Totem
      • Kaffeine
      • KMPlayer
      • (ko)GomAudio

      And then some more generic support for other cases

      --
      Your hair look like poop, Bob! - Wanker.
    6. Re:the non-free part isn't so bad by Anonymous Coward · · Score: 0

      After ~14-21 years, the content path is free.

      We've seen copyrights perpetually extended. Who's to say that the same thing won't happen with patents?

    7. Re:the non-free part isn't so bad by dangitman · · Score: 1

      Histrionics over strange data formats is so 90s.
      KB? SI units are meant to be computationally convenient, not arbitrarily assigned.

      The irony between these two statements is intense.

      --
      ... and then they built the supercollider.
  6. Um, no by eweu · · Score: 2, Insightful

    this will make Wikipedia by far the most likely site for an average internet user to have a truly free and open video experience

    Yes. An experience of videos that won't play in the average internet user's browser. It's easier to click the "close window" button than it is to care about broken video on a broken web site.

    1. Re:Um, no by arose · · Score: 2, Informative

      They have a Java fallback. I Even without a fallback Theora will play on more machines then HTML5 only H.264 would (supported by Safari, Chrome and Opera, where the user cares to add the codec, as opposed to Firefox, Chrome and Opera).

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    2. Re:Um, no by Blakey+Rat · · Score: 1

      Haha. Nobody has Java installed, either... that's the worst "fallback" ever.

    3. Re:Um, no by shutdown+-p+now · · Score: 1

      Actually, you'd be surprised. I've seen some market research desktop penetration figures for Java, and they're really impressive. Not 97% like Flash, but way above 50%.

      I still wonder where that comes from. Very few sites on the Net actually seem to need JRE these days. On the other hand, both my current desktop and my current laptop (HP and Lenovo, respectively) came with JRE preinstalled. Both were purchased within the last two years.

    4. Re:Um, no by Blakey+Rat · · Score: 1

      Last time I bought an HP (and I'll never make that mistake again) it came with a kitchen sink installed too. If that wasn't bad enough, they even installed the crapware on the recovery disk that shipped with it-- I had to borrow a clean Windows CD from a friend and reinstall to make it even slightly usable. (Fortunately, the OEM number worked fine with the clean Windows CD.)

      But anyway. Java's nothing but a security hole now. Like you said, practically no sites require it, the odds of a normal consumer coming across an application that requires it are pretty remove, and it's just as bloated and ugly as ever.

    5. Re:Um, no by Hurricane78 · · Score: 1

      You forget that IE9 will play H.264. And Safari and Opera use the OSs facilities, as every sane design would. (Dunno about Chrome, but since Google owns YouTube the choice is obvious.)
      Now since H.264 is installed on EVERY Mac and modern Windows, only Firefox will be left out in the cold.
      Serves them right for making it a holy war, and only supporting their “one true codec”.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    6. Re:Um, no by arose · · Score: 1

      Well, if I had to use a fallback I'd use stats from my site, not what you feel is right or wrong. My sites stats, weirdly enough, indicate that almost everyone has Java and about 80% have flash, I don't know if that's Flash blockers or a problem with the stat tracker, but either way I'm less likely to believe Adobe's numbers after that.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    7. Re:Um, no by arose · · Score: 1

      You forget that IE9 will play H.264.

      If there is one thing I'm not forgetting, it's the install base of XP.

      And Safari and Opera use the OSs facilities, as every sane design would.

      Wrong and wrong. Safari uses QT, definitely not an OS facility on anything but OS X. Opera uses gstreamer, which might, or might not be part of a modern Linux distro, but is uncommon outside of free software circles.

      In fact, if you are working cross platform, heavily using OS specific frameworks is not as sane as it might sound.

      Now since H.264 is installed on EVERY Mac and modern Windows, only Firefox will be left out in the cold.

      Now since H.264 is installed on EVERY Mac and modern Windows, only Firefox will be left out in the cold.

      Firefox has a bigger install base then OS X, so all caps 'every' isn't that impressive. Modern Windows is still only part of Windows.

      Serves them right for making it a holy war, and only supporting their “one true codec”.

      I fail to see how Microsoft and Apple pushing their single codec (yay patent royalties) is any better.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  7. Re:Good luck with that by md65536 · · Score: 1

    They can dream about unicorns and world peace too but doesn't mean it's gonna happen...

    Not with that attitude it won't!

  8. Re:Good luck with that by 2obvious4u · · Score: 0, Offtopic

    Has anyone tried to create a unicorn using a horse and a narwhal? Why isn't there an island of Dr. Morrow anyway? I think that would be cool. Creating hybrid animals is cool. We should do more experiments along these lines.

  9. Oh the irony.. by Anonymous Coward · · Score: 1, Insightful

    So why does an organization like openvideoalliance.org use flash for their videos?

  10. Good luck. by OrangeCatholic · · Score: 2, Insightful

    They're so uptight about what pictures they'll accept (copyright, fair use), what makes anyone think that Wikipedia is going to become a giant video repository?

  11. Dirac by Anonymous Coward · · Score: 2, Interesting

    I've been playing around with schroedinger 1.0.9 and it's output is nearly indistinguishable from baseline x264. If dirac had even half the resources that have been invested into h.264 encoders, it's possible that quality, compression, and encode/decode speed could be equal.

  12. Re:Good luck with that by arose · · Score: 2, Interesting

    Market share wise browsers with Theora support are actually ahead right now...

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  13. Re:Good luck with that by idontgno · · Score: 1

    Well, I have this half-monkey half-pony hybrid, but my girlfriend doesn't like it.

    --
    Welcome to the Panopticon. Used to be a prison, now it's your home.
  14. Which video game console supports Theora? by tepples · · Score: 1

    Ah, now your real concern appears, I suspect. If Theora starts to get momentum, it'll appear on phones and similar devices quickly enough. My phone already supports Ogg Vorbis. (It may even support Theora; I haven't tried.) If yours doesn't, then perhaps you went with the wrong vendor.

    I want to go with the right vendor. But which video game console supports Theora? None of the big three do. Or should people buy one box for Theora video and one box for games?

    If you want Wikipedia to go with your proprietary, encumbered format(s), your best be is to lobby the patent holders to donate the patents to the public domain. Good luck with that. :)

    That depends on what Google decides to do with VP8.

    1. Re:Which video game console supports Theora? by JackDW · · Score: 1

      A hacked one? :)

      If you want a machine to play video files in any format, then may I suggest an old PC? A powerful machine isn't needed, so whenever you upgrade, you get a new "free" media player. (I was amazed at how quiet my old desktop became, once I'd replaced the hard disk with a USB stick and downgraded the graphics card.)

      --
      You're an immobile computer, remember?
    2. Re:Which video game console supports Theora? by tepples · · Score: 1

      If you want a machine to play video files in any format, then may I suggest an old PC?

      The problem with an old PC is that it's big and noisy, and most PC games really designed to run in situations commonly associated with a TV. Then I'm back to "one box for Theora video and one box for games". And if one doesn't have a spare old PC handy, would you recommend an ION nettop like the Aspire Revo?

    3. Re:Which video game console supports Theora? by JackDW · · Score: 1

      It entirely depends on what suits you best. I didn't want to buy a special nettop, mini-ITX or similar because I wanted everything to be very, very cheap. Therefore, I only used spare parts. I could probably build a quieter or more energy efficient solution if I spent $$s, but I think it would be a false economy. Sans hard disk, the machine is already very quiet.

      However - I think it's quite normal to have a whole range of devices attached to your TV for playing media in different formats. It's the modern equivalent of a hifi that includes several machines for playing LPs, CDs and tapes. Now, we end up with a stack of different consoles and a PC, because each plays a different sort of media.

      --
      You're an immobile computer, remember?
    4. Re:Which video game console supports Theora? by michaelhood · · Score: 1

      If you want a machine to play video files in any format, then may I suggest an old PC?

      The problem with an old PC is that it's big and noisy, and most PC games really designed to run in situations commonly associated with a TV. Then I'm back to "one box for Theora video and one box for games". And if one doesn't have a spare old PC handy, would you recommend an ION nettop like the Aspire Revo?

      i've been doing a lot of research on this to build a tiny, silent set top for media purposes. it seems like our bet bet is the ZOTAC IONITX-A-U Atom 330. It's fanless, so I've been looking at using either an off-the-shelf SSD or a cheap CF-to-SATA with cheap CompactFlash cards (which I have piles of from my cameras)

  15. Oh, they WILL be paying. by Anonymous Coward · · Score: 1

    They just won't know it. (Oh, and a more idealistic person might even say that they'll not only be paying money, but paying in a more metaphorical sense with lock-in, etc.)

    1. Re:Oh, they WILL be paying. by Lunix+Nutcase · · Score: 4, Insightful

      They just won't know it.

      Know what? People pay 0 dollars for a browser. Exactly what costs are they bearing due to Apple or Google or Microsoft including H.264 support in the browser?

      Oh, and a more idealistic person might even say that they'll not only be paying money

      Paying money where? Browsers have all been free for quite some time now.

      but paying in a more metaphorical sense with lock-in, etc.

      What lock-in? What exactly am I "locked-in" to when I watch H.264 HTML 5 movies on youtube? And how would those movie being encoded in theora make me less "locked-in"?

    2. Re:Oh, they WILL be paying. by K.+S.+Kyosuke · · Score: 3, Informative

      Know what? People pay 0 dollars for a browser. Exactly what costs are they bearing due to Apple or Google or Microsoft including H.264 support in the browser?

      I would assume that the licensing fees for MPEG are a part of the Windows and Mac OS X price tag.

      --
      Ezekiel 23:20
    3. Re:Oh, they WILL be paying. by Alphathon · · Score: 1

      ^This^. Makes you wonder how it'd be done though - in browser or as part of the OS. Euther way the price will increase slightly to pay for the licencing fee (if it is in OS then it could be a specific fee, if in browser then it'll be an invisible price increase). As for Google, they make enough money from advertising to support development of all the software they make. I'm sure they'd just go the same route for the licencing.

    4. Re:Oh, they WILL be paying. by Lunix+Nutcase · · Score: 1

      I would assume that the licensing fees for MPEG are a part of the Windows and Mac OS X price tag.

      So at $5 million dollars a year split over the 10s of millions of licenses a year that comes out to what? A handful of change? Oh noes!

    5. Re:Oh, they WILL be paying. by dave420 · · Score: 1

      If by a handful of change you mean a few cents, then yeah - it's practically free for all involved. Teh horrorz!

    6. Re:Oh, they WILL be paying. by Kohath · · Score: 2, Insightful

      I would assume that the licensing fees for MPEG are a part of the Windows and Mac OS X price tag.

      Is there someone who wouldn't assume that? What would it be like if someone found out the answer and posted it?

      Meanwhile, this uncertain assumption that some unknown cost paid by some unknown entity and then included as an unknown component cost in some unknown products is hardly a call to arms .

    7. Re:Oh, they WILL be paying. by Anonymous Coward · · Score: 0

      Know what? People pay 0 dollars for a browser. Exactly what costs are they bearing due to Apple or Google or Microsoft including H.264 support in the browser?

      Ask that in the fedora forums. You must pay for Apple and MS OS's and they include support. You can download Fedora for free and they don't include support. This is, in fact, a major obstacle to the widespread adoption of free software. Redhat, among others, have demonstrated that quality software can be developed and released profitably under open source licences. That has the potential to be a massive benefit to society in that productive capability can be had for $0 for those willing to use it without support. Currently that potential is mainly being filled by copyright infringement. Support for codecs in FOSS allows that free cost software distribution to happen legally.

      You see, when FOSS is downloaded, the wealth in existence increases by one copy of software. When proprietary software is downloaded, it drains the economy of the retail price set by the vendor (I'm not sure how but the proprietary vendors assure us it is so). So it is vitally important for our economy for us to have patent free codecs.

    8. Re:Oh, they WILL be paying. by jim_v2000 · · Score: 1

      There is no such thing as a "drain" on the economy. Goods and money simply move around.

      --
      Don't take life so seriously. No one makes it out alive.
    9. Re:Oh, they WILL be paying. by diamondmagic · · Score: 1

      Wealth is subjective, and people value goods differently. Thus there can be a "drain on the economy" in the sense you can create and destroy wealth (voluntary exchange which creates wealth, and war/violence that destroys wealth). What Coward is wrong about is that you can drain the economy of a certain dollar value: An economy transforms inputs (land, labor, capital, consumables) into more highly valued outputs, and in the end, money isn't an input.

    10. Re:Oh, they WILL be paying. by Anonymous Coward · · Score: 0

      Not really, considering that people would have still bought those operating systems at the same price even without an MPEG license.

      It's like if I buy a burger and fries for $5.00 and they throw in a Coke for free. You could say that the cost of the Coke is covered in the $5.00, but to me it's free since I was already going to spend the $5.00 on just the burger and fries.

    11. Re:Oh, they WILL be paying. by PhunkySchtuff · · Score: 1

      I would assume that the licensing fees for MPEG are a part of the Windows and Mac OS X price tag.

      And I would assume that of the total cost of my OS, the licensing fees for H.264 are at most a few cents, which I'm more than happy to pay if it supports formats that are out there to be used, are technically quite good and supported by a lot more than just video on the internet - things like video cameras, media centres, handheld devices, and a lot of these devices have hardware accelerated playback so all the better.

    12. Re:Oh, they WILL be paying. by Anonymous Coward · · Score: 0

      Okay, smartass. Let's reword it:

      Licensing fees for MPEG are a part of Windows and Mac OS X price tag. Full stop.

      Neither Microsoft nor Apple can print money. It has to come somewhere.

    13. Re:Oh, they WILL be paying. by Lunix+Nutcase · · Score: 1

      Licensing fees for MPEG are a part of Windows and Mac OS X price tag. Full stop.

      And the price of neither operating system has changed in any significant way since they've included H.264 codecs in their OSes for some time now.

    14. Re:Oh, they WILL be paying. by Lunix+Nutcase · · Score: 1

      Sure, and they amount to a couple of cents. Oh noes! A couple of pennies is gonna break mah bank!

    15. Re:Oh, they WILL be paying. by Anonymous Coward · · Score: 0

      Is there someone who wouldn't assume that? What would it be like if someone found out the answer and posted it?

      OK, sure. Let's be like Albert Einstein, and do a thought experiment. (That's where you use your brain and your knowledge of reality to derive a correct conclusion. Be sure to have a brain and some connection to reality before trying this.)

      Codecs are programs. The programmers who wrote the non-free codecs were paid money by their employers. Money is not created from thin air by employers (it is created by banks and to a lesser extent by governments, but let's not get sidetracked). Employers get their money by selling product, which in this case is the non-free codec. The employers sell licenses to use the codecs to OS vendors. OS vendors also have to pay their employees, and they get the money by selling OSes. The cost of OSes is determined by the cost of production plus profit. The profit is determined by the market's ability to foster competition and by the amount of money consumer have available to spend. The OS vendors profit is only limited by promises their executives have made (contracts and regulations), the market's ability to offer alternatives, and consumer spending - but the production cost is fixed before the product arrives in the market, and cannot be unpaid.

      Understanding these basic facts, we are led inexorably to the conclusion that consumers pay for all costs of production, including codec licensing fees, except in cases where the vendor goes bankrupt or otherwise ceases to exist, or cases where one product line subsidizes another (in which case one group of consumers pays the costs of another group of consumers). The money that is delivered to the licensor by the OS vendor is coming directly from the consumer.

      Now, it's interesting to note: at certain points in the economic cycle, profits can be pushed very high - for example, when the competition has not yet attained functional parity, or when a vendor suborns a regulatory body to prevent competition. At such points, reducing the cost of production does not reduce the cost of product, it just increases profit for the vendor, who can will then have the financial resources to distort the market further, usually by funneling cash to regulatory bodies (such as the US congress).

    16. Re:Oh, they WILL be paying. by sglewis100 · · Score: 1

      Licensing fees for MPEG are a part of Windows and Mac OS X price tag. Full stop.

      So if IE 9 comes with h.264 support, and it's made available for download for existing Vista and Windows 7 users... what were you saying again? Believe it or not, every now and then, a company doesn't pass down a cost to the consumer in such a direct fashion. And you can't say "well they COULD have lowered the price by $1 instead", since they wouldn't do that to their OS. It's just a cost to them. A cost which helps them protect marketshare.

    17. Re:Oh, they WILL be paying. by Matthieu+Araman · · Score: 1

      You're assuming wrong. You've got a restricted licence included with Windows. If you're out of the licence scope, you need to buy another licence ! For example, if you produce your videos, you can be very quickly out of the licence scope.

    18. Re:Oh, they WILL be paying. by lennier · · Score: 1

      What lock-in? What exactly am I "locked-in" to when I watch H.264 HTML 5 movies on youtube? And how would those movie being encoded in theora make me less "locked-in"?

      You're locked into exactly the set of platforms which provide you a legal H.264 player - a set which explicitly excludes open-source platforms because the H.264 patent is contrary to the spirit and letter of the GPL and any other Free licences. It cannot be legally distributed as part of any Free software distribution.

      If you don't care about both open source or abiding by law, then you have no problem.

      If you like Linux but don't mind modding your distro with illegal software, then you also have no problem - but if you're that sort of person who doesn't mind breaking the law to get free stuff, you probably also have no problem with pirating Windows or movies outright. Which is a legitimate viewpoint but not a legal one.

      If the movies are encoded in Theora, however, you are legally allowed to watch them on any current or future platform, including Free ones without running the risk of you or your distribution's creators being thrown in jail.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    19. Re:Oh, they WILL be paying. by countach · · Score: 1

      Didn't somebody mention a $5M cap? So Mozilla pays their $5M, and now their products can be distributed ad-infinitum, right?

    20. Re:Oh, they WILL be paying. by Anonymous Coward · · Score: 0

      What Coward is wrong about is that you can drain the economy of a certain dollar value

      I'm not wrong about it, I just thought the sarcasm was obvious enough to not need a tag. Proprietary IP vendors make the case that it costs, so I used that fallacious argument in my response. There's also no need to be so formal, you can call me by my first name, "Anonymous".

  16. Scareware disguised as codec by tepples · · Score: 1

    If people have the technical chops to install something like flash, why wouldn't they have the technical chops to install something else?

    Because they trust adobe.com and distrust random codecs downloaded from random sites that infect people with the "Antivirus 2009" scareware.

  17. This is great for web filtering and searching by Anonymous Coward · · Score: 0

    h.264 = Porn and "funny", time wasting, videos

    Theora = Actually useful stuff

    1. Re:This is great for web filtering and searching by shutdown+-p+now · · Score: 5, Insightful

      h.264 = Porn and "funny", time wasting, videos

      Theora = Actually useful stuff

      That's a long way to spell "H.264 wins".

  18. Existing PCs don't run recent Windows by tepples · · Score: 1, Informative

    H.264 is already included in any recent Windows

    At least two-thirds of PCs run Windows XP, Windows Vista Home Basic, Windows Vista Business, or Windows 7 Starter. These operating systems do not include an H.264 decoder. Among Windows operating systems, only Windows Vista Home Premium, Windows Vista Ultimate, and Windows 7 Home Premium or higher include an H.264 decoder.

    1. Re:Existing PCs don't run recent Windows by shutdown+-p+now · · Score: 1

      I suspect that one of two things will happen if/when H.264 becomes a de facto standard for HTML5 video:

      1. Microsoft will roll out H.264 support for those OSes (e.g. with IE9)

      2. Google will roll out third-party H.264 support for those OSes (a la Google Gears for various browsers).

    2. Re:Existing PCs don't run recent Windows by jonwil · · Score: 1

      Wont happen. Ever.
      H.264 requires per-unit royalties to be paid to patent holders (usually via the MPEG LA patent pool) and there is no way they will grant a license for a free download.

    3. Re:Existing PCs don't run recent Windows by Pentium100 · · Score: 1

      Among those PCs that run Windows OSs without h264 codec, a lot have a third party codec downloaded and installed.

    4. Re:Existing PCs don't run recent Windows by shutdown+-p+now · · Score: 1

      Uhh, didn't you notice that Google does exactly that already? Chrome is completely free, and ships with HTML5 H.264 video support...

      Trick is, per-unit royalties are capped at $5M/yr total. Frankly, this is chump change for Google, not to mention Microsoft.

      In fact, so far as I can see, it would actually cost them nothing at all, since the cap seems to be company-wide, and not just for a specific product. You can bet Microsoft already hits the cap for Windows 7, and Google probably just pays it as a kind of a "flat fee" so as to permit users to freely redistribute Chrome.

    5. Re:Existing PCs don't run recent Windows by jonwil · · Score: 1

      I wasnt aware that Google Chrome has support for H.264 in the tag or that there was an upper limit on royalty fees.

      In any case IE9 wont be released on XP, nor will any H.264 support.

  19. Infringement on the repo's part by tepples · · Score: 1

    The user should be warned of the issues with installing the codec, and then given the choice to continue.

    Some lawyers for MPEG-LA members would try arguing that the maintainer of a repository that doesn't use IP address geotargeting commits infringement.

    1. Re:Infringement on the repo's part by shutdown+-p+now · · Score: 1

      This is already how some other patented MPEG LA codecs are handled - e.g. AAC in Ubuntu. No legal troubles so far.

  20. Re:Good luck with that by magus_melchior · · Score: 1

    I believe I told you: Half means half the genetic codebase, not half the mass.

    In short, yes, you did use too many monkeys.

    --
    "We are Microsoft. You shall be assimilated. Competition is futile."
  21. I've been waiting for this by DerekLyons · · Score: 1

    I've been waiting for this - because it's a rare organization that can long resist the desire to go political.

    So much for their independence and reliability.

    1. Re:I've been waiting for this by shutdown+-p+now · · Score: 1

      Wikipedia was always political in that sense (free and open formats).

  22. This is counter to Wikipedia by Anonymous Coward · · Score: 2, Interesting

    First of all, bad headline. This is not Wikipedia's assault; in fact, this will be seen as an assault on Wikipedia, to unduly promote a new product. Most of these additions will be reverted as spam, and the organization from that website will be seen as illegitimate canvassing. A campaign to get anything on Wikipedia is against Wikipedia's policies on neutrality. Now it's true that Wikipedia has a tendency to bend to other free-as-in-speech interests, but those video files are going to draw more attention and ire than the usual debates.

    1. Re:This is counter to Wikipedia by Compaqt · · Score: 1

      What? Wikipedia already has open-format video on Wikipedia.

      Saying that a campaign to get open-format videos onto Wikipedia will be viewed as spam is like saying a campaign to get ASCII-format articles will be viewed as spam.

      Oh, and they're actually working with the Wikipedia folks to streamline the video-upload procedure.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    2. Re:This is counter to Wikipedia by Anonymous Coward · · Score: 0

      Sigh, lame analogy. The campaign is working on a technical front with Wikipedia to make standards-based video available on the site. That's the part where they put on their diplomatic hats to make sure the site is suitable for the campaign they want to run.

      The other part, the part which TFA is actually about, is getting a bunch of standards-based activists to start flooding Wikipedia with videos in order to establish those codecs on the web, using Wikipedia's popularity as a launching platform. Here you are confusing "can" with "should". Nobody said that Wikipedia can't have videos. Reading comprehension please.

  23. Non-free content in a free encyclopedia? by saibot834 · · Score: 1

    This assumption seems flawed. Wikipedia prefers open licensed content for images, but will accept non-open content with a fair use rationale. Presumably, the same would be true of video clips.

    You are referring to the fair use policy on the English Wikipedia. Please note that this is a policy for English only, not all language versions allow non-free content.

    IANAL, but I doubt that non-free videos would really be a breakthrough. They'd have to be short and low-resolution (at least that's what Wikipedia demands for non-free images and audio). You couldn't just take any youtube video.

    In my opinion, that's a good thing. The original idea behind Wikipedia (or it's predecessor Nupedia) was to create a free-as-in-freedom encyclopedia. Wiki-style editing, a strong community and rejection of ads, all those concepts are nice and good, but they are secondary. The real goal is to create a free encyclopedia. There is a wonderful page that explains why fair use should not be on Wikipedia: Veganism parable

    As for the project itself (the summary doesn't mention much about the technical background), this brings some nice usability features with it. Until now, if you wanted to add media (images/audio/video), you would have to register (preferably) on Wikimedia Commons, upload the file there, then remember/copy the exact name of the file and include it in the article. Now you can just go to an article, click on the add media button and a wizard pops up and you can upload your file, while editing.

    1. Re:Non-free content in a free encyclopedia? by game+kid · · Score: 1

      There's already a few featured articles with non-free clips, e.g. Star Trek: First Contact and Cartman Gets an Anal Probe. The "breakthrough" has already happened; it's just that those adding the clips do so quietly and sparingly (they are non-free, after all).

      Not every article will benefit from a video; sometimes a GIF or basic image will do. Even in articles where non-freeness doesn't keep video to a minimum, resources (number of editors, file size, etc.) and common sense will. Video won't reach banner-ad ubiquity on WP, but every once in a while you'll see one and say "ooh, neat".

      --
      You can hold down the "B" button for continuous firing.
  24. Wikipedia? by TopSpin · · Score: 5, Insightful

    So far the comments are focused on teh 3v1Lz H.264 vs. 'open' codecs, why one is better than the other, etc. What about Wikipedia?

    Perhaps Wikipedia doesn't actually need to be riddled with video. Maybe Wikipedia is actually better off without it. Have you ever had to suffer through some lengthy, 99% irrelevant video to get a specific piece of information? How many times have you just not bothered to watch that video because it's frustrating, you can't afford the time, don't have just the right version of some plug-in, etc? Ever tried to copy and paste from a video?

    How much of the useful content of Wikipedia is going to end up trapped inside videos when easily indexed and searched, entirely unencumbered US Grade-A ASCII^h^h^h^h^hUTF-8 would have been sufficient? How much more bandwidth is Wikipedia going to have to fund to serve up cell phone footage of Silambarasan Rajendar waving at people?

    --
    Lurking at the bottom of the gravity well, getting old
    1. Re:Wikipedia? by steveg · · Score: 1

      Good point. If my students can't cut and paste from Wikipedia, why would they even bother to go there?

      --
      Ignorance killed the cat. Curiosity was framed.
    2. Re:Wikipedia? by imakemusic · · Score: 1

      A picture is worth a thousand words. A video is worth 24,000 words per second.

      --
      Brain surgery - it's not rocket science!
    3. Re:Wikipedia? by jez9999 · · Score: 1

      What? Videos on Wikipedia don't replace an article, they're used in floated, captioned boxes to enhance an article.

    4. Re:Wikipedia? by Simetrical · · Score: 1

      How much of the useful content of Wikipedia is going to end up trapped inside videos when easily indexed and searched, entirely unencumbered US Grade-A ASCII^h^h^h^h^hUTF-8 would have been sufficient?

      None. Videos will supplement the textual content of Wikipedia, not supplant it. They can already be found in some articles floated to the side, like images often are. Also, Wikimedia Commons is happy to host educational material that's not useful to Wikipedia.

      --
      MediaWiki developer, Total War Center sysadmin
  25. All this means is competition.... by avatar_charlie · · Score: 4, Funny

    ......just not between corporate entities.

    No, the competition will be between various wiki-weirdoes over who can be first to enshrine their peckers forever by putting video of it on the articles for "Penis", "Herpes", and any other genital or sex-related article on that site....of which there are no small number.

    1. Re:All this means is competition.... by Anonymous Coward · · Score: 0

      ......just not between corporate entities. No, the competition will be between various wiki-weirdoes over who can be first to enshrine their peckers forever by putting video of it on the articles for "Penis", "Herpes", and any other genital or sex-related article on that site....of which there are no small number.

      You seem very well informed on the matter.

    2. Re:All this means is competition.... by Anonymous Coward · · Score: 0

      Almost all serious wiki editors/admins seem to have some fairly introverted social issues and many appear to be heavily sexually repressed: I would not be surprised.

  26. Re:Good luck with that by amRadioHed · · Score: 1

    Yeah, but what's that worth when almost no one is using the Theora support?

    --
    We hope your rules and wisdom choke you / Now we are one in everlasting peace
  27. Amanda Seyfried/Julianne Moore love scene? Check! by Impy+the+Impiuos+Imp · · Score: 1

    I can imagine being an access provider, with the more bloated, unpatented, public video versions becoming the rule rather than the exception.

    On the other hand, it will create demands for even more throughput, which will happen sooner or later anyway...

    --
    (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
  28. A long lost battle. by Hurricane78 · · Score: 2, Interesting

    Give us a real codec.
    Linux beats the crap out of Windows.
    Firefox beats the crap out of IE.
    Vorbis beats the crap out of MP3.
    And Theora should beat the crap out of H.264!

    But right now it’s a toothless tiger, slow, bad quality/size ratio, outdated technology...
    Until that changes, well... frankly nobody in the real world cares for evangelical wars.
    And I’m saying that as someone who almost exclusively uses open source software, and is very very happy with it!

    I wish I could write codecs. I’t word night shifts to kick H.264s ass. ^^

    But hey, as previously said: If Firefox just binds to generic facilities/libraries like ffmpeg, DirectMedia and CoreVideo, the whole discussion goes away, since everybody can choose what to use anyway.
    Unfortunately right now they play little dictators, enforcing what they see as “the one true codec” in their holy war.
    Maybe I can at least write a patch that creates these bindings.

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:A long lost battle. by amirulbahr · · Score: 1

      I wish I could write codecs. I’t word night shifts to kick H.264s ass. ^^

      AFAIK you wouldn't be able to do that without violating some H.264 patent.

    2. Re:A long lost battle. by Anonymous Coward · · Score: 0

      Linux beats the crap out of Windows.

      That isn't objectively true. Its desktop usage share is still around 1%, and that's counting dual-booters and all the communist countries where buying Apple or Windows products is a no-no. And I'm still having more stability and usability problems with Ubuntu than for Windows 7 - Linux definitely ain't ready for grandma's computer just yet. You might say that Linux beats Windows in specific deployment categories (most Web server situations, supercomputing, etc), but you need to qualify your statements as such. And to make your arguments valid you'd also need to compare the leading FLOSS solution to a leading proprietary solution, which doesn't always come from Microsoft.

      Firefox beats the crap out of IE.

      Again an invalid comparison. IE is not the best proprietary Web-browser in terms of quality (Opera, Safari, Chrome), but it is the most popular.

      Vorbis beats the crap out of MP3.

      MP3 is not the latest or best proprietary audio format.

      And Theora should beat the crap out of H.264!

      Yes, we want this to be the case, but it isn't a foregone conclusion.

      Unfortunately right now they play little dictators [...]

      So do the GPL authors. Only the software that doesn't rely on government force is truly free!

      (Signed: Alex Libman's sock-puppet.)

    3. Re:A long lost battle. by damaki · · Score: 1

      Vorbis beats the crap out of MP3.

      Used to. That's not even true anymore at transparency bitrates with lastest Lame improvements. -V5 and -V6 are transparent in most cases.
      You examples are quite meaningful of the general openness problem : better quality does not mean wider userbase. Typical users do not really care about quality because they do not know what quality is.

      --
      Stupidity is the root of all evil.
    4. Re:A long lost battle. by Hurricane78 · · Score: 1

      You are seriously stating that it’s impossible to invent better theories and algorithms than H.264??
      I’m not talking about imitating them and trying to improve on it, like a loser!
      I’m talking about creating the next generation! Something that is outside of the box of what previous generations dared to think about! :)

      <black voice>That’s what I’m talking ’bout!</black voice> ;)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    5. Re:A long lost battle. by Hurricane78 · · Score: 1

      Used to. That's not even true anymore at transparency bitrates with lastest Lame improvements. -V5 and -V6 are transparent in most cases.

      Sorry, but that’s a straight out lie, and you knw it.
      You can optimize the encoder as much as you want. It won’t make the limitations of the format itself go away. To make MP3 better than Vorbis, it would have to stop being MP3 at all.

      You examples are quite meaningful of the general openness problem : better quality does not mean wider userbase. Typical users do not really care about quality because they do not know what quality is.

      Sadly, I have to agree. :/
      “good enough” is... well... good enough. The first codec to get above that limit, is going to make it. Everything after that doesn’t matter that much. Like the landing on the moon. Nobody cares that you did it better, when you were the second one landing there. ;)
      So what could move people to another codec?

      I’d guess something that they want, but can’t have with the old one.
      In case of video codecs, there may be a chance, if H.264-encoders were not free, and not easily available to everyone.
      Seeing that YouTube already offers that service for free, and most DVD burning programs that you get for free with you DVD drive offer it too, that’s not going to happen.

      So is it really that important that it’s free? I mean if there are no advantages that anyone can feel... does it matter?
      After all that’s the whole point of it mattering: It gives you an advantage / prevents a disadvantage.

      Conclusion: As long as users don’t clearly see a large enough disadvantage, and/or we don’t offer a large enough advantage, there is no point in changing things.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    6. Re:A long lost battle. by damaki · · Score: 1

      http://listening-tests.hydrogenaudio.org/sebastian/mf-128-1/results.htm
      Do you have anything to support your point of view?

      --
      Stupidity is the root of all evil.
    7. Re:A long lost battle. by damaki · · Score: 1

      And I have to add this : http://listening-tests.hydrogenaudio.org/sebastian/mp3-128-1/results.htm
      Yeah, transparency is pretty damn high at this range...

      --
      Stupidity is the root of all evil.
    8. Re:A long lost battle. by lennier · · Score: 1

      Are you saying that nobody in the real world cares about obeying the law in regards to software?

      While that may be true, it seems a rather sad state of affairs.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    9. Re:A long lost battle. by lennier · · Score: 1

      If Firefox just binds to generic facilities/libraries like ffmpeg, DirectMedia and CoreVideo, the whole discussion goes away, since everybody can choose what to use anyway.

      No, they can't. Not legally. Not in the USA.

      It is illegal to distribute a free H.264 player in the USA.

      The code exists. It is copyright-free. But it is illegal to ship due to software patents.

      If you either a) don't particularly care if Linux provides H.264 support, or b) don't particularly care about obeying the law, this is not a problem. If, however, you want both of those, you have a legal problem.

      The only way to remain legal is to NOT provide illegal H.264 support. If you also want to be able to watch videos, it would be nice if they weren't in a format that requires someone to break the law to give you the ability to watch.

      Why is it so hard for people to understand that this has nothing to do with ideology and everything to do with obeying the law?

      Yes, the law is broken and should be changed. But since it hasn't...

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
  29. rules have ridiges?!? by Anomalyst · · Score: 1

    You'll get much further in life when you stop living your life wrapped around retarded ridged rules that make you prejudice against valid alternatives while at the same time giving your competition, which isn't so warped, an advantage.

    Rules with ridges are often more rigid. Com'on guys, were goin' over the top, mind the barbed wire.

    --
    There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
  30. Re:Go Fuck Yourself Troll by Anonymous Coward · · Score: 0

    Did you forget your lithium this morning?

  31. Fail by Anonymous Coward · · Score: 0

    Fail - somehow inneficient implementation?, takes to much CPU, laggy experience makes me want the sht that works instead.

  32. They're calling it the Magna Encarta by ArundelCastle · · Score: 1

    (good, encyclopedia style videos only!).

    Odds on how many Mythbusters citations per page? I'll bet 3.

  33. How useful will these videos be? by Alien1024 · · Score: 2, Interesting

    I don't think this will make much of a difference as the videos in Wikipedia will probably be of little value. Like almost every Internet user I often get a Wikipedia article when searching for something. The things I find useful in it are the external links and to a lesser extent, the text and images in the articles. But most OGG samples are rarely worth checking out. The same probably goes for their Theora videos. It's just not easy to produce or find informative and encyclopedic audios or videos that can be made available under Creative Commons. The text found in copyrighted sources can be reworded to present only the facts, which can't be copyrighted. But you can't do the same with audiovisual material.

  34. Strike a blow for Freedom, indeed! by davevr · · Score: 1, Flamebait

    Consumers are most interested in freedom from buggy, hard-to-install, hard-to-configure, don't-play-my-youtubes, unsupported-by-my-PC-maker codecs.

  35. Open codec or google is a traitor by Mordocai · · Score: 1

    I found it more convenient to post my thoughts on my blog, but basically it wraps down to this: Google will support an open codec or they are a traitor to the community they say they support. Here is the rest: http://fossstudent.blogspot.com/2010/03/googleyoutube-and-h264.html

    1. Re:Open codec or google is a traitor by shutdown+-p+now · · Score: 1

      Your reasoning seems to be flawed. Google supports FOSS community, yes, but not exclusively - many of their products are still non-FOSS, for example. So how they can be "traitors" is beyond me.

      And, by the way, this kind of rhetoric and loaded word usage is precisely what turns many people away from FOSS advocates.

    2. Re:Open codec or google is a traitor by Mordocai · · Score: 1

      Your reasoning seems to be flawed. Google supports FOSS community, yes, but not exclusively - many of their products are still non-FOSS, for example. So how they can be "traitors" is beyond me.

      And, by the way, this kind of rhetoric and loaded word usage is precisely what turns many people away from FOSS advocates.

      Well, they are supposed to be open standards supporting. They commonly say "we support ". So yes, I would say that using a codec that free software cannot ethically use would be betraying the community that they make use of every day. They use our software to make money, and this is the best possible way they could give back.

    3. Re:Open codec or google is a traitor by Mordocai · · Score: 1

      Your reasoning seems to be flawed. Google supports FOSS community, yes, but not exclusively - many of their products are still non-FOSS, for example. So how they can be "traitors" is beyond me.

      And, by the way, this kind of rhetoric and loaded word usage is precisely what turns many people away from FOSS advocates.

      Well, they are supposed to be open standards supporting. They commonly say "we support ". So yes, I would say that using a codec that free software cannot ethically use would be betraying the community that they make use of every day. They use our software to make money, and this is the best possible way they could give back.

      I apologize, that was supposed to say "They commonly say "we support (insert open standard/free software product here)." And just an addendum, if we didn't use "loaded word usage" we would simply be ignored. Just because you think it is fine that the millions of FOSS users could not use YouTube/wikipedia(if they didn't make this stand), doesn't mean we agree.

    4. Re:Open codec or google is a traitor by shutdown+-p+now · · Score: 1

      So yes, I would say that using a codec that free software cannot ethically use would be betraying the community that they make use of every day.

      Why don't you consider Google releasing non-Free software a betrayal, then?

      Or how about the use of Flash for YouTube? How long has this been going under Google now? And you realize that it's actually using H.264, too, right?

    5. Re:Open codec or google is a traitor by shutdown+-p+now · · Score: 1

      And just an addendum, if we didn't use "loaded word usage" we would simply be ignored.

      Do you have any evidence that it actually helps?

      It's actually one remarkable difference between Open Source and Free Software propaganda campaigns - the latter are almost always received with derisive laughter from pretty much everyone but those participating in them, for their sheer stupitidy. Here would be one recent example of such. OSS guys at least talk about how and why their stuff is good, not about how teh evil proprietors are taking over the world.

      Just because you think it is fine that the millions of FOSS users could not use YouTube/wikipedia(if they didn't make this stand), doesn't mean we agree.

      Frankly, I would be extremely surprised if FOSS purists (which are people who wouldn't use anything non-FOSS, such as Flash) would number even in tens of thousands, much less millions, worldwide. Non-purists don't actually have the "can't use" problem - they'll use either the Flash version, or they'll use Chrome (which comes with a built-in licensed decoder), or they'll buy the GStreamer codec, or they'll just ignore the U.S. law and use ffmpeg or whatever.

  36. Re:Go Fuck Yourself Troll by Anonymous Coward · · Score: 0

    No, most eleven-year-olds act like that. You can tell he's proud that he just learned the word "ideology," though.

  37. Re:Good luck with that by shutdown+-p+now · · Score: 1

    Market share wise, web sites with H.264 support are significantly ahead right now (YouTube HTML5 demo).

  38. JPEG by wiredlogic · · Score: 2, Insightful

    JPEG images are patent encumbered too. There's just a gentleman's agreement among group members not to pursue royalties for "baseline" implementations of the standard. I don't see anyone scrambling to remove them from Wikipedia.

    --
    I am becoming gerund, destroyer of verbs.
    1. Re:JPEG by arose · · Score: 1

      You are thinking of JPEG2000, since JPEG doesn't have this stupid notion of profiles. There was some saber rattling with JPEG as well, but it never went anywhere.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    2. Re:JPEG by Simetrical · · Score: 1

      JPEG images are patent encumbered too. There's just a gentleman's agreement among group members not to pursue royalties for "baseline" implementations of the standard. I don't see anyone scrambling to remove them from Wikipedia.

      JPEG has no known patents on it, according to Wikipedia. A couple of companies have asserted patent rights on JPEG, but it's not at all clear that the patents are actually valid: some have already been overturned by the Patent Office, and others are undergoing review.

      --
      MediaWiki developer, Total War Center sysadmin
  39. Nature of the problem: by Anonymous Coward · · Score: 0

    >>> What I'm more worried about is that I cannot watch Wikipedia videos with any other device than my PC

    > Ah, now your real concern appears, I suspect.

    Actually, I think his fears are unfounded, as any (proprietary) converter software will probably be able to transcode a free format to a proprietary one. The reverse is where the real problem lies.

    > If Theora starts to get momentum, it'll appear on phones and similar devices quickly enough. My phone already supports Ogg Vorbis. (It may even support Theora; I haven't tried.) If yours doesn't, then perhaps you went with the wrong vendor. I didn't look for Vorbis support for my phone, but I did look for openness; if that wasn't a factor in your choice of phone, then my sympathy for you is nil.

    My exact thoughts. People who don't value open formats not only harm themselves, they harm everyone -- because the larger the number of morons, less interesting is for a vendor to approach the comparative lower number of the ones in-the-know.

    Regarding Theora appearing on phones, I have something to say. I have an ogg-playing radio (and a portable ogg-player). Besides Linux, of course. But when I must play things on mp3-only equipment... well, no ogg music. At all.

    For a while, it bothered why the radio vendor doesn't advertise the ogg playing feature. I suspect 3 things:

    - the radio maker "licensed" the project and doesn't know about ogg;
    - the potential buyers of ogg hardware are still just a few and the vendor simply doesn't care;
    - the vendor is afraid of patent-related suits and doesn't advertise ogg, believing it could violate someone's patents.

    I think this is like the .doc x .odt x .ooxml thing: you can use odt but remember to also save on proprietary formats for interchange with M$-slaves. Given enough time and increased usage of ogg (Vorbis or Theora), more and more hardware will play ogg.

    > If you want Wikipedia to go with your proprietary, encumbered format(s), your best be is to lobby the patent holders to donate the patents to the public domain. Good luck with that. :)

    This can, unfortunately, be quite easy. A favourite tactic is enabling free use of proprietary formats for as long as needed for it to "catch". When everybody uses it, then start charging...

    1. Re:Nature of the problem: by Pentium100 · · Score: 1

      I think this is like the .doc x .odt x .ooxml thing: you can use odt but remember to also save on proprietary formats for interchange with M$-slaves.

      Yes, because every "M$-slave", who has an older PC which is enough for an older version of Windows and MS Office and is enough for their work, should have to buy a new PC, install Linux, learn how to use it and then continue doing their work like nothing happened, except that they wasted money (for the PC) and time (for learning a new OS).

      Besides, OpenOffice supports .doc good enough. The new document formats are not technically superior than .doc, then why why should one spend money and.or time to use them?

      If yours doesn't, then perhaps you went with the wrong vendor. I didn't look for Vorbis support for my phone, but I did look for openness; if that wasn't a factor in your choice of phone, then my sympathy for you is nil.

      When I was looking for a phone a few years ago I was looking for:
      1. A good camera (the ability to take photo of a A4 sheet and be able to read the text).
      2. 3G support with IrDA and Bluetooth support, so I can connect to the internet with my laptop or PDA.
      3. An OS, so that I can install software.
      4. A media player.
      5. Reliable phone.
      6. A good keypad with big buttons, so I don't press a few of the buttons at once.

      I bought a Nokia N93. I used Nokia phones since a long time ago and know they are reliable. I like my phone, and do not want to replace it (especially not with a phone that does not have a keypad). I don't know if it supports Ogg audio, since most of my digital music collection is mp3. I only wish that this phone supported HS(D|U)PA, since it only supports UMTS. Would I buy the same exact phone but with Ogg and theora support? Probably, if it was available at the time, since more supported formats = better. Would I sacrifice the optical zoom to get theora support? No.

      It is interesting to me how the FOSS crowd does not want to pay money for anything, but fully expects other people to pay money to be compatible with the FOSS crowd.

  40. So many people passing comment, so few understand. by pslam · · Score: 1

    Hardly a day goes by without HTML5/H.264/Theora popping up here. Here's the facts, not the fiction:

    • Theora is not as good as H.264, but it's not far off. People seem to turn this into huge issue. It's just not quite as good as H.264, but it's still perfectly usable (I would say better than just 'usable') as an alternative codec in pretty much every use case. A universally supported codec is far more useful than a slightly better but non-free codec.
    • Hardware support is a RED HERRING. You don't need hardware support in most of the cases mentioned. An iPhone is perfectly capable of playing 480p resolution Theora in realtime, in software only (yes I've tried this). Most of the newer Android handsets likewise (not tried this but they're similar or better spec). Please don't tell me you want 720p on your handset. Power consumption difference to hardware decode is noticeable, but it's not huge, and again - it works, and that's what matters.
    • Hardware support wouldn't involve re-inventing huge bits of codec. Theora is strikingly similar to the way MPEG-4 works in many ways. Most hardware codecs run configurable microcode anyway.
    • The bigger issue for most vendors is QA. Distributing software in the non-FOSS world isn't as simple as adding a library a flipping compiler switches. They'll have to support Theora from then on, test it for exploits, crashes, compliance, and keep on doing that every release. It's a support burden. It's chicken and egg: there isn't the demand, so they aren't supplying.
    • Mozilla can never include H.264 support as it would make the browser non-free-as-in-freedom, which is entirely against their mission. People suggesting they do this either do not understand the point of free software, are just selfish, or are (here anyway) trolls. Redistributors (Firefox) may be able to include H.264 support but it seems to be on shaky legal ground to me (IANAL).
    • Whether they can just support generic plug-ins is another issue altogether. My opinion: using system plug-ins is a bad idea because it takes the (presumably) well examined, mostly-exploit-free browser code and exposes it to (from experience) the much less well examined system plug-ins. But that argument is separate to everything else.

    I'm guessing from the number of people that think Theora is unusable, too slow, requires hardware to run on handsets, and H.264 can just be popped into Mozilla, that there's the usual troll:signal ratio problem.

  41. Who Died in 1938? by westlake · · Score: 1

    Some of the folks who died in 1938:

    Clarence S Darrow, attorney

    Thomas Wolfe, author

    Warner Oland, actor (Charlie Chan)

    Pearl White, US actress/stunt woman (Perils of Pauline)

    Benjamin Cardozo, American jurist

    E.C. Segar, American cartoonist (Popeye)

    Mustafa Kemal Atatürk, founder and the first President of Turkey

    Typhoid Mary, carrier of the typhoid disease

    Karel Capek, Czech author (R.U.R.)

    Joe "King" Oliver, jazz cornet and bandleader

    Famous Deaths for Year 1938

  42. /.'s resident Anarcho-Capitalist troll approves! by Anonymous Coward · · Score: 0

    Way to go Wikipedia! The quality, performance, and user convenience may not be 100% yet, but HTML5 can meet and exceed its proprietary competitors very quickly, especially with the backing of a site like Wikipedia.

    "Be the change you want to see in the world." --Gandhi

    (Signed: Alex Libman's sock-puppet.)

  43. we just had this discussion on /. by roman_mir · · Score: 1

    we just had this same discussion on /. concerning Flash vs HTML5, I said HTML5 was a clear winner, because it is not Flash, because it is not a proprietary tech.

    Some disagreed. I still say it is the only right way to go, towards the open standards, to be just like the rest of the Internet, which could not have survived without the open standards. Don't care if Flash is 5 times faster and 10 times flashier. We need an open standard, so that nobody owns the only allowed implementation, so that nobody can control the Internet through proprietary means. Many people want to control the Internet, proprietary tech is the only way that they could, let's not lose our Internet to them.

  44. Re:Good luck with that by arose · · Score: 1

    Fuck those eggs, we need chickens!

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  45. your mom won't use theora by Anonymous Coward · · Score: 0

    as a content producer, i see one of the biggest hurdles to open video standards adoption to be the lack of options in mainstream production tools. Until it is a "one-click" option to encode in ogg/theora, most FCP and Premiere users are not going to do it, especially when they have h.264 support built in with a one-click preset.

    I asked Mozilla's Chris Blizzard about this part of the puzzle at SXSW this week, and he blew me off as being "cute." I think this is indicative of their non-realistic view of the situation. If they don't include the production side of the equation in their plans to push for an open standard, then they're pretty much ensuring that open video remains a fringe issue.

  46. As much as I dislike Wikipedia... by QuietLagoon · · Score: 1

    ... for all the usual reasons, I have to say... this takes balls. Kudos to Wikipedia.

    1. Re:As much as I dislike Wikipedia... by MtViewGuy · · Score: 1

      Gutsy move maybe, but when YouTube--the world's largest video repository--is mostly H.264, unless Google is willing to recode all those YouTube videos in Ogg Theora format, you can forget about Ogg Theora being widely accepted as the HTML 5.0 video standard.

    2. Re:As much as I dislike Wikipedia... by QuietLagoon · · Score: 2, Interesting
      but when YouTube--the world's largest video repository--is mostly H.264, unless Google is willing to recode all those YouTube videos in Ogg Theora format, you can forget about Ogg Theora being widely accepted as the HTML 5.0 video standard.

      .

      You could say the same thing about FireFox's challenge to the Microsoft disaster known as Internet Explorer.

      Yet FireFox has driven the web towards standards-based web design, instead of Microsoft-based web design.

      And Google recoding the videos is little more than the mother of all batch jobs.

    3. Re:As much as I dislike Wikipedia... by Compaqt · · Score: 1

      It's not necessarily an either-or scenario.

      YouTube will continue to support Flash, which people will already have.

      If people want to access the #6 site on the Web (Wikipedia) they'll be using open formats to do so. Maybe not every single Wikipedia user will immediately start using open formats, but it'll have an effect.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    4. Re:As much as I dislike Wikipedia... by Compaqt · · Score: 1

      One approach that I think could work is to have an open-format pledge bank.

      I.e., Wikipedia has 13% of the Web, Youtube has 20?%. Once you get enough sites to add up to 50% or so committing to using open formats, it becomes a juggernaut. This is a good approach because it avoids any one site having to make the first step.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
  47. I don't buy it. by gbutler69 · · Score: 1

    My guess is that what you are calling "implemented in hardware " is actually "firmware" for a "DSP".

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  48. Really? by gbutler69 · · Score: 1

    Lots of the devices that support h264 do it in hardware^H^H^H^H^H^H^H^Hfirmware embedded in ROM using a DSP. Something we are unlikely to see out of Theora.

    There fixed that for you. So, we're just a firmware upgrade away from Theora on most devices, right? If I'm the manufacturer of these devices, with continuing falling RAM/ROM prices, if Theora becomse even 10% of available video, I'll include it or I'll lose to my competitors.

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  49. Theora already works fine on PS3... by Anonymous Coward · · Score: 0

    ... under Linux. The standard "libtheora" library simply compiles and runs and does full screen video just file. The only thing needed for Theora on Wikipedia to work in the gameos is for Sony to get off its ass an add it.

    And whats this "sub standard" crap? Since when is "better than everything except the very best and most recent proprietary format" substandard?

  50. pungi for downloading dependencies by jrincayc · · Score: 1

    I would recommend using pungi and Fedora. It can determine all the prerequisites of the programs you specify and download them as well. Basically, you just use the gather portion and it downloads all the files. I used it for maintain
    https://fedorahosted.org/pungi/

  51. Just use same bitrate for Theora as H.264 by jrincayc · · Score: 1

    If bandwidth is the problem, just use the same bit rate for each codec. H.264 will probably be a bit better, for the same bandwidth, but for the people who don't have a H.264 decoder, this may just be fine. Theora is probably about the same as H.263, which is what youtube was originally anyway.

  52. Re:HTML5 Video - history repeats dumb dumb by Anonymous Coward · · Score: 0

    VHS vs Betamax
    you learned nothing - again

  53. This is... by abigsmurf · · Score: 1

    "Free as in use exactly what we want you to use and nothing else"?

  54. Alignment, that's it by Anonymous Coward · · Score: 0

    Not only Wikipedia, Red hat. Canonical should put its weight behind this as well (I'm not hoping for Novell/SuSE, but hey).

    Mark? Are you listening?

  55. If it's "practically free", why not make it free? by Anonymous Coward · · Score: 0

    If it's "practically free", why not make it free? After all, they're not making any money off it, are they.

  56. Contributory infringement by tepples · · Score: 1

    Among those PCs that run Windows OSs without h264 codec, a lot have a third party codec downloaded and installed.

    Recommending that end users install an infringing third-party codec pack could be considered contributory infringement.

    1. Re:Contributory infringement by Pentium100 · · Score: 1

      You don't have to recommend a specific implementation of the codec, just state on the system requirements that for h264 video playback you need h264 codec compatible with DirectShow (or whatever the equivalent on Linux is). My video card, for example, came with Cyberlink PowerDVD, which includes the h264 codec and, I assume, does not infringe the patent even if it was recognized in my country.

  57. x86 instruction format by StripedCow · · Score: 1

    We're lucky that the x86 instruction format is not patent-encumbered.

    Imagine we'd have to pay Intel every time we compiled a program...

    --
    If Pandora's box is destined to be opened, *I* want to be the one to open it.
  58. Porn by SgtChaireBourne · · Score: 1

    So that's a long way of saying that Theora will steam roll all other formats if the porn industry takes it up, right?

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  59. Ooh.. Shiny Shiny by ratboy666 · · Score: 1

    "Like it or not, the iPhone's dominance isn't because of any media blitz or cult of Apple, it's because it came out in a market where it was by far the best choice and is still superior to any other smartphone I've seen."

    Really? iPhone vs. Blackberry 9000. About the only thing the iPhone wins at is Shiny Shiny.

    --
    Just another "Cubible(sic) Joe" 2 17 3061
    1. Re:Ooh.. Shiny Shiny by moderatorrater · · Score: 1

      The Blackberry is still not as good for average users. It has a nub as opposed to the entire phone being a large touchscreen, making it so that there's less presentation area and flexibility. It has a different class of applications, making it very well suited to business use but not as broadly appealing. The iPhone integrates with computers in a way that's familiar to people who already own iPods. The app store makes it ludicrously easy to install applications.

      Most importantly for the applications, the development environment doesn't have legacy cruft like Blackberry's traditionally had, and, because it was able to grab large chunks of the market quickly, it was able to get a robust development ecosystem. The iPhone isn't superior in every way to the Blackberry, but to say that it doesn't win at anything other than "Shiny Shiny" is just plain wrong.

    2. Re:Ooh.. Shiny Shiny by ratboy666 · · Score: 1

      Blackberry Bold vs. iPhone 3G (the two I have access to):

      Plug-in expandable memory. Replaceable battery. Takes videos. Has a flash. Synchs with Evolution. Synchs with Google Calendar. Better Bluetooth. Standard disk when plugged in. Free office suite. Better phone. Keyboard for accurate email entry. sms/mms. Java. Plays AVI files without transcoding needed. No special application needed on computer. Works with "other" OSs (Solaris, Linux). Comes in "unlocked" flavors not tied to carrier.

      And I didn't touch on a single "corporate" feature in that entire list. (Note - the last iPhone firmware supports tethering. I haven't tried it yet, though.).

      Just saying... (my wife likes the "shiny shiny" and so do my kids -- I also have an iPod Touch and we throw them at the kids to keep them amused on trips). Even though the Blackberry supports some "games", I wouldn't give it to the kids -- too much of my business data is on the phone. The iPhone is a platform that happens to communicate. The Blackberry is a communications device that happens to be a platform (mostly PDA functionality).

      If you don't have regular access to a Mac OS X or Windows XP (Vista/7) computer that is a "home" for the iPhone, the Blackberry is a far superior device. If you want want a good phone and communications device, the Blackberry is a superior device. If you want a cool (shiny shiny) platform that is also a phone, go with the iPhone. Can you imagine a Blackberry without a phone/phone-email? I wouldn't touch it, either. But it IS a better smartphone ESPECIALLY for business use.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
  60. ways you pay for being proprietary by Anonymous Coward · · Score: 0

    There is a lot of mention about the cost being very small, or the concept that the end user never pays for this. This message is just for them...

    I beg to ask these questions:
    1) how is my O/S provider going to pay for this "small" cost? Especially since I don't pay my O/S provider any money for development.
    2) what exactly is small about this cost? You take the total number of customers and divide it by the maximum licensing cost to reach a per-user cost??? This doesn't come out to a small number when the total number of users is smaller.

    These questions become very real when you use an operating system that doesn't come pre-installed on your computer.

    If you can for one moment, imagine that you are not a common computer user with a common operating system. You will see that the usage of proprietary licensed video formats is another mechanism to keep the large O/S providers in demand and to reduce or eliminate competition from alternate operating systems with a smaller user base. In other words, the status quo is one which encourages monopolistic positions and discourages competition.

    I agree that these sorts of decisions and thought patterns may not interest the average computer consumer would can easily afford an additional $50 ish payment to an O/S provider to not have to deal with these issues each time they purchase new hardware. But please... think of the children and by that I mean think of those in countries with a lower standard of living.

    If you can imagine that, then maybe you can start seeing the big picture. We have free and open alternatives to just about every digital storage format available. And yet we don't take the 2 seconds of time in order to set the Word document default to an open standard. What kind of world do we live in where we are so lazy that we would rather push proprietary requirements onto others? These proprietary formats being ones which require the end user to pay or commit a crime????

    Who are these people? Why do they demand others to pay for their choices?

    BTW: I will tell you that it is not the government. Because at least they are aware that such demands mostly effect the poor.

    Also, I would just like to add that it is completely incorrect and ignorant to believe that open formats are not as good then their proprietary brother-en. I agree that they often have different and other characteristics... but I would be hard pressed to find such an instance where the obvious issue preventing a feature enhancement to an open product is not one which is not caused by a proprietary format (software/hardware) that is being withheld from the open source community. ie: if you see deficiencies in open source... the #1 suspect is underlying proprietary issues. Get rid of these issues and you will see how much better software could be.

    Lastly, I want to say that I do not personally see the benefit of open source as one about cost. It just really is a better model for getting better software to the people... regardless of the channel used to deliver it. I am saying that open source is far better then any alternative out there for producing solid, secure and timely software. IMO: we will all consider this an obvious fact within a decade. Then all slashdot members will lament about how the death of windows is a bad thing... because that's what slashdot does: fight for the underdog.

  61. Legal consequences (Sue Linus) by Anonymous Coward · · Score: 0

    When do you think Linus Torvalds will get sued?
    He installed the Gstreamer ugly plugins
    https://bugzilla.redhat.com/show_bug.cgi?id=439858#c19
    and ugly includes MPEG-LA patents
    http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-ugly-plugins/html/
    and users have patent liability:
    http://weblogs.mozillazine.org/roc/archives/2010/01/h264_licensing.html