Slashdot Mirror


H.264 vs. Theora — Fightin' Words About Patentability

An anonymous reader writes "Thom Holwerda from OS News has penned a rebuttal to claims from Daring Fireball's John Gruber that Theora is a greater patent risk than H.264. Holwerda writes, 'And so the H264/Theora debate concerning HTML5 video continues. The most recent entry into the discussion comes from John Gruber, who argues that Theora is more in danger of patent litigation than H264. He's wrong, and here's why.'"

421 comments

  1. First Post by DarkKnightRadick · · Score: 1

    And the lawsuit goes to...h.264!

    --
    "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    1. Re:First Post by MrNaz · · Score: 5, Insightful

      Why on Earth does HTML5 need to even specify the codec? I mean the tag doesn't specify an image format, why should not just have a src= attribute and any video supported by the system will play in it. That way it'd be the same as the change from GIF to PNG all those years ago, where those who want to use GIF could, and those who needed / wanted the free option (which was also superior) could use it without killing support for the other.

      I don't see why this is an either / or issue.

      --
      I hate printers.
    2. Re:First Post by OrangeTide · · Score: 2, Insightful

      so your suggestion is that all devices need all codec to be practical? Which is the current situation. Right now you just make H.264 videos to reach the widest possible audience, but it's still not 100% of HTML5 enabled browsers. If there was one good codec that a website creator can count on being supported, it makes things like HTML5 very useful. Without it you might as well use Flash because that is more widely supported than H.264 these days.

      --
      “Common sense is not so common.” — Voltaire
    3. Re:First Post by Anonymous Coward · · Score: 0

      Untrue. In a codec agnostic environment, you could use h.264 as the most commonly supported format if you needed total ease of use by the end user, but you also have the option of askin your users to potentially install a codec.

      There's no reason to believe that a browser doesn't support JPG these days, even though it's possible.

    4. Re:First Post by Anonymous Coward · · Score: 1, Informative

      Flash uses h264 for video compression since Flash 9.

    5. Re:First Post by Anonymous Coward · · Score: 4, Insightful

      No, he's not suggesting that all devices support all codecs. He's quite rightly suggesting that HTML5 should support all codecs. Why on earth should it be stuck with one? That makes no sense whatsoever. It would make HTML5 very limited and that is not something that W3C or any other standards body should ever even think of doing. The 'img' tag doesn't support one type of image format, nor does the 'object' or 'embed' tag support only one form of content for their usage.

      By the way, Flash is NOT a video codec, nor a video standard. Flash video *IS* H.264 (MPEG-4) video.

    6. Re:First Post by bhtooefr · · Score: 2, Informative

      And that's what it's doing right now. HTML5 itself is codec-agnostic.

      The problem is that it doesn't matter what codecs are supported, it matters what codecs people actually use to post content online. If you can't legally support H.264, and people want to post H.264 videos, you're screwed.

      Now, can browsers support the system codecs? Yes, and I've heard claims that on Unix, Opera actually does. Problem solved, anything that you have a GStreamer codec for can be played in Opera using <video>.

      However, part of the point of <video> was that it would get rid of having to download codecs and media players and such.

    7. Re:First Post by dgatwood · · Score: 1

      Here's a novel idea. How about the browser vendors get together and standardize on a single bytecode and API for compression codecs similar to the way they standardized the Netscape plug-in API all those years ago.

      Provide a very limited API that takes a stream of data in from the browser and writes out a series of audio and video frames to a buffer, with a bunch of common math operations (FFTs/DFTs, DCTs, etc.) provided as library calls into native code. Allow the codec to provide a vector version and a non-vector version if needed.

      Allow the codec (in bytecode form) to be downloaded from a web page and executed without being stored locally as a plug-in in much the same way that JavaScript is loaded now. Heck, given that most browsers compile JavaScript to native code anyway, it could even be a JavaScript codec API, so long as you provide a sufficient library of transforms so people don't have to write their own in JavaScript....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    8. Re:First Post by GigaplexNZ · · Score: 1

      He's quite rightly suggesting that HTML5 should support all codecs.

      Which means that open source software is now in violation of not paying royalty payments on certain codecs because they implemented an open specification requiring proprietary codecs.

    9. Re:First Post by gig · · Score: 4, Insightful

      > I don't see why this is an either / or issue.

      In one word: standardization.

      For the same reason we standardize markup around W3C HTML5, we standardize video around MPEG-4 H.264. We need to be able to make just one Web app and have it work on any browser from any manufacturer. We need to be able to make just one video and have it work in any video player from any manufacturer. If we don't have that, then consumers cannot choose their own preferred browser, or preferred media player. They get stuck using IE6 or Windows Media Player solely to decode nonstandard Web apps and video. It's not acceptable.

      Modern consumer electronics devices have one video codec burned into hardware, and that is MPEG-4 H.264. This is almost 10 years old now. Same as DVD players all had MPEG-2. That's the reason the H.264 codec exists. If you want to publish a video that will play on iPod and other media players, iPhone and other smartphones, various set-top boxes, both FlashPlayer and QuickTime Player, both YouTube and iTunes, that is H.264. If you want to play video that was made with Flip camcorders, or Kodak camcorders, or Canon cameras, or Nikon cameras, or Panasonic cameras, or iPod/iPhone, that is H.264.

      A key thing to understand is that MPEG-4 is not owned by any one company. The patents are not held by any one company. They are put into a pool and licensed equally to all comers. This puts all the consumer electronics manufacturers on equal footing. Flip is not going to cease to exist one day because a submarine patent takes all their devices off the market. The entire MPEG-4 group would address the submarine patent, all the manufacturers are protected from litigation in this way. That's just not true with Ogg.

      On a Mac/PC, if you are somewhat technical, you can load all kinds of software codecs, most of which are made for authoring or some other special purpose, not made for consumer playback. Same as you can happily make Web apps for IE6 if your company uses IE6. But if you want to share Web apps with the world, you use HTML5. If you want to publish video for the world, you use H.264.

      Also, you have to understand that video authoring tools all work with H.264 for many years now, and not with nonstandard formats. Where you see Ogg video, or Windows Media, or Real Media, or any other nonstandard media, they were very likely created from H.264.

      This all has nothing to do with HTML5. As I said, H.264 is almost 10 years old and both YouTube and iTunes and both FlashPlayer and QuickTime Player play it. That *is* Web video. H.264 plays in Firefox today, and will play there tomorrow. HTML5 standardizes *markup* not video. So browsers now have to become video players. If Firefox doesn't want to do that, then they will see their users make an exodus for Chrome or Safari. There isn't any way to turn back time to when Ogg was current technology and rewrite history and re-encode the incredible amount of video that is stored in H.264.

      If you imagine that Mozilla was saying "we can't support UTF-8" that is the same as them not supporting H.264. The UTF-8 text is already out there, and there's no other technology to replace it, and that is the same with H.264 video. A Web browser that can't play YouTube is not a Web browser.

    10. Re:First Post by Nikker · · Score: 2, Insightful

      With todays servers if someone posts a video to my site I can just transcode it to any format I wish. If I want I can bite the bullet and pay for one license to transcode and no one knows the difference. When it comes down to it the end user just wants to see a slide show at around 30 fps, no special magic no 3D rendering just what they shot on their camcorder or their crappy cell phone camera. So why all this fuss? HTML5 is just a tag not much more and the end user sure as hell doesn't care, they just want to click and see a video. So saying by any justification one method is "better" than another is just plain stupid. Hell at the end of the day I could just buy one license for H264 and host on Amazon S3 offering for a small charge instant transcoding of all material to DIVX,Theora or GIF if I wanted to and tell everyone else to go fuck themselves.

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    11. Re:First Post by nog_lorp · · Score: 4, Interesting

      If we don't have that, then consumers cannot choose their own preferred browser, or preferred media player.

      Actually, if we DO have that, I cannot choose my preferred browser: an open source one. Yeah, big problem there for slashdotters - FOSS cannot implement H.264 because of the patent encumbrance.

      Flip is not going to cease to exist one day because a submarine patent takes all their devices off the market. The entire MPEG-4 group would address the submarine patent, all the manufacturers are protected from litigation in this way. That's just not true with Ogg.

      Licensing the H.264 pool does not protect you from submarine patents, but it doesn't matter as submarine patents are no longer viable.

      It is true that it is incredibly important that codec management no longer be a complication for the user. HTML 5 handles this well:
      <video>
        <source src='video.mp4'>
        <source src='video.ogg'>
      </video>

      There: it plays the "more advanced", more established, license-fee-encumbered codec if available. Otherwise, it falls back on the FOSS codec.
      There should be a single format that all browsers support, but this codec should not require an exorbitant license fee without excluding a huge segment of the browser market (FOSS). As for protection from patent trolls, it is reasonable to presume that Google will side with any other company that is targeted for use of Theora.

      All browsers should support Theora, and publishers can host H.264 (or any other codec) seamlessly on top of that if they want.

    12. Re:First Post by Anonymous Coward · · Score: 0

      For the same reason we standardize markup around W3C HTML5, we standardize video around MPEG-4 H.264.

      There is a huge difference, one is an open an unencumbered standard, the other a profitable monopoly for a cartel. We should standardize around something open like what W3C does and Theora is closest to that.

    13. Re:First Post by TheRaven64 · · Score: 2, Insightful

      The problem with this idea is twofold. First, that mobile devices do the decoding in hardware, so you'd have to expose functions like 'send this H.264 stream to the ASIC,' which is not very useful in the general case. The second problem is what exactly to put in the API. You mention DCT, but Dirac uses DWTs, so a Dirac implementation would need to do the wavelet operations entirely in bytecode. Alternatively, you could need to force every browser to implement DWT, even if they never played back Dirac content.

      Given the security holes in browsers' JavaScript sandboxing over the past few years, I'm also not completely convinced that this is more secure than just installing a CODEC once for each format that you want to play.

      --
      I am TheRaven on Soylent News
    14. Re:First Post by Jesus_666 · · Score: 2, Insightful

      Why would they want to? Internet Explorer and Safari play H.264 just fine so where's the incentive for Microsoft and Apple? Google already has ffmpeg built in and most likely won't want to absorb another codec (interface).

      That leaves us with Mozilla and Opera. Even if they agree on an ABI that hardly makes for an industry-wide standard.

      Plus, Opera's method of just leveraging codecs the system has does the same without duplicationg data and without requiring the user to figure out which website to trust when downloading codecs.

      In fact, that's the biggest problem with your post: It assumes that either every website out there is honest and good or that every user is competent in the field of browser plugin threat analysis. Most users aren't going to know whether it's good or bad to install the h.265 codec girlswithbigtits.cn is offering them.

      There are reasons why the Netscape plugin architectore hasn't already been used to deal with this. The fact that trusting random websites to install plugins in my browser (plugins that directly talk to my GPU no less) is a bad idea is one of them.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    15. Re:First Post by Anonymous Coward · · Score: 1, Interesting

      If you imagine that Mozilla was saying "we can't support UTF-8" that is the same as them not supporting H.264. The UTF-8 text is already out there, and there's no other technology to replace it, and that is the same with H.264 video. A Web browser that can't play YouTube is not a Web browser.

      YouTube isn't played in the web browser today. It's played in a Flash applet. Flash is not "the web" and it never can be. It's a closed system that takes a free ride on the open protocols and open formats of the internet. And that's the core of the entire issue, isn't it. Without open, royalty-free video, video will never be played within the browser. It will be constrained to closed frameworks and closed libraries which you can't use without paying a toll (even if the implementations of those libraries are open source, you can't use them without paying that toll). That's a problem. That's not the web.

      But you don't want the web. You're proposing a closed system control by a very concentrated collection of corporate interests for the sake of what you view as pragmatism. That isn't pragmatic and it's a very short sighted perspective. It just builds a network that limits competition and entry to new developers for new platforms because to get anywhere they have to overcome the price barriers you want to erect.

      I don't want an Internet that's a patchwork of fiefdoms. I want a open, competitive network and open formats are the best way to build it.

    16. Re:First Post by Anonymous Coward · · Score: 1, Interesting

      "If you imagine that Mozilla was saying "we can't support UTF-8" that is the same as them not supporting H.264."
      No it's not. This is not a technical problem. It's a licensing problem and some web-browsers just can't support H.264 in it's current state. Regardless of how many times people repeat the mantra about H.264 it doesn't make any different until the licensing issues go away. If you don't have a free software browser and the money / incentive dries up to keep pushing HTML forward ( like it did with IE 6) then you end up in exactly the situation we are now moving away from it.

      Theora can be made better, theora can be added to hardware and H.264 can theoretically be licensed in a compatible manner. The problem is that only the first two options seem to have anyone working on them.

    17. Re:First Post by Anonymous Coward · · Score: 1, Funny

      Most users aren't going to know whether it's good or bad to install the h.265 codec girlswithbigtits.cn is offering them.

      "Firefox can't find the server at www.girlswithbigtits.cn"

      :(

    18. Re:First Post by Rockoon · · Score: 1

      ...but there is no reason for browsers to implement any video codec... so what you said in the first paragraph is stupid.

      If your browser is decoding videos, FOSS or not, then your browser is wasting your money...

      I hear this argument again and again... "but if they choose H.264 then my FOSS browser..." blah blah blah... FireFox is FOSS, but most FireFox users have been playing H.264 web content for years.. hardware accelerated even... [B]end of fucking story[/B]

      Sure.. the zealots will complain because they cant have a "totally free" computer.. you know.. those guys that dream of HURD being usable one day... 99.995% of the rest of the world just don't give a fuck. They paid for an H.264 license and its like spitting in their eye if you refuse to not only support it, but not support it in the best pay possible.. through the codecs they already own, customized for their hardware.

      --
      "His name was James Damore."
    19. Re:First Post by Drakonik · · Score: 1

      Sooooooo...H.264 needs to be the standard because it's the standard? Your argument is kinda cyclical. IE6 used to be the ubiquitous. used to be acceptable to use. Why aren't they anymore? Because something better came along. Tech isn't good just because it's universally supported. It just makes it hard to transition away from.

    20. Re:First Post by ilguido · · Score: 2, Informative

      That way it'd be the same as the change from GIF to PNG all those years ago, where those who want to use GIF could, and those who needed / wanted the free option (which was also superior) could use it without killing support for the other.

      IE didn't support transparent PNG files until IE7, 2006 (yes... 2006). I hope I have answered your question.

    21. Re:First Post by OrangeTide · · Score: 1

      but it's not the same code and cannot be shared with anything else. Adobe just doesn't work that way. Flash is its own stand-alone beast.

      --
      “Common sense is not so common.” — Voltaire
    22. Re:First Post by OrangeTide · · Score: 1

      Except there are plenty of devices not capable of supporting H.264 due to licensing reasons or in some cases (rarer now) because the software doesn't exist on those platforms. But JPEG is actually supported everywhere. Probably because it is old and unencumbered.

      Perhaps in 15 years H.264 will be as practical and easy to support as JPEG.

      --
      “Common sense is not so common.” — Voltaire
    23. Re:First Post by skyfex · · Score: 1

      > All browsers should support Theora, and publishers can host H.264 (or any other codec) seamlessly on top of that if they want. As of right now it's just as impossible for all browsers to support Theora as it is for all browsers to support H.264 (well, I'd argue it's not impossible for Firefox to support H.264 in practice, but that's another discussion). Mobile browser just doesn't have the hardware support it needs for decent support for Theora video. Personally I'd prefer it if H.264 became the standard. It's partly developed by the same standardization grouped that developed JPEG (ITU-T), and in my opinion JPEG is a pretty good example of a successful standard. I just don't think that Theora will be as successful as H.264 without proper industry backing. And even though the licensees aren't legally exempt from patent litigation with H.264, I think you'd be more protected in practice (it's in ITU-T/MPEG's interest to protect the standard).

    24. Re:First Post by Anonymous Coward · · Score: 0

      HTML5, today, does *not* specify a codec.
      Whether or not it needs to specify one is in theory the subject of debate.
      However, please understand that, technically, today it doesn't.
      It's believed that HTML5 could be finalized without specifying a codec.
      I also believe that HTML5 will be successful in any event.

    25. Re:First Post by diamondsw · · Score: 1

      All browsers should support Theora

      And they won't; see Internet Explorer, Safari.

      Next.

      --
      I don't know what kind of crack I was on, but I suspect it was decaf.
    26. Re:First Post by petermgreen · · Score: 1

      Which is why we have a problem. Mozilla refuse to support h.264 because they cannot license it in a way that they believe is compatible with opensouce principles. Apple and nokia (maybe others too) refuse to implement theora claiming it's a submarine patent risk (personally I suspect the real reason is they have a vested interest in h.264).

      The HTML 5 guys have no real power to fix this impasse since there is no law or contract requiring anyone to follow thier standard. All they can do is document the fact that the browser vendors couldn't agree and leave websites with the choice of either encoding everything twice or only supporting a subset of users.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    27. Re:First Post by Anonymous Coward · · Score: 0

      Modern consumer electronics devices have one video codec burned into hardware, and that is MPEG-4 H.264.

      Ever try loading one into Microsoft Movie Maker on Windows XP?

      The most popular movie editor on the most popular operating system on the planet does not understand it. Even on a machine with Windows Media Player that can play it.

      Is that a licensing issue? Does it have to be licensed for each app that uses it? Crazy! Does it have to be licensed for each core of each processor for each app? Or for each I/O port?

      How about something with a free license?

    28. Re:First Post by petermgreen · · Score: 1

      That statementt is half true and rather misleading. IE (at least IE6) supported 256 color pngs with a transparent color (e.g. what you will get when you convert your gifs to pngs).

      It didn't support alpha channel transparency and I don't think it supported truecolor pngs with a single transparent color but unless you count some dirty hacks with gif (that didn't work very well and I don't think I ever saw in practice) it didn't support either of those things with any other format either.

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

      Why on Earth does HTML5 need to even specify the codec?

      Because leaving it unspecified nullifies the value of a standard video tag, encourages continued fragmentation of web content, and leaves a door wide open for some vendors to force other vendors to choose between violating the law or preventing their users from accessing a wide range of Internet content.

      In short, because it forces open source vendors like Mozilla to forego interoperability with the web. With no codec [which can be legally and practically implemented by every vendor] specified, the de facto standard (h.264) is unavailable to about a quarter of web users.

    30. Re:First Post by omfgnosis · · Score: 1

      How do you propose open source vendors like Mozilla address the fact that they cannot legally implement the apparent standard?

    31. Re:First Post by dgatwood · · Score: 1

      Since I'm commenting anyway, I'd like to add that such an API should also allow for "container" plug-ins (a.k.a. demuxing plug-ins) for specific container formats, which output multiple streams and tag them with a particular MIME type and provide an optional URI for a decoder plug-in for that MIME type (which the browser is allowed to ignore if it already has a built-in decoder for that type). Now, to address your points.

      First, that mobile devices do the decoding in hardware, so you'd have to expose functions like 'send this H.264 stream to the ASIC,' which is not very useful in the general case.

      As far as I can tell, mobile hardware is gradually moving away from using custom ICs for decoding and towards small general-purpose vector engines. For example, iPhone 3GS uses a PowerVR chip as best I can tell from a quick Google search. As such, I don't think that issue will be particularly important in the long term. Also, any such system whose CPU and GPU aren't fast enough to do a software decode would be incapable of ever supporting any other codecs anyway, making the argument moot. Ideally, the language design should be such that the code can be compiled and executed on the CPU or on a GPU, whichever is more capable. This obviously puts limits on what you can do in the language, but also greatly enhances the ability of mobile devices to tune the efficiency of playback to maximize battery life.

      The second problem is what exactly to put in the API. You mention DCT, but Dirac uses DWTs, so a Dirac implementation would need to do the wavelet operations entirely in bytecode. Alternatively, you could need to force every browser to implement DWT, even if they never played back Dirac content.

      Sure, throw in some wavelets. I wasn't trying to give a compete list of transforms that should be included, just the first few examples that popped into my head. Working out which math ops should be included is the sort of thing standards bodies are good at doing, so long as those mathematical transforms are not patented. Besides, if you use compiled JavaScript as I suggested, there shouldn't be a huge performance difference between a native code library and a JavaScript port of that library anyway except in the amount of time it takes to download the codec (which was the whole point of providing more math functions).... You might have to limit the use of certain JavaScript constructs, but you'd probably have to avoid those anyway to compile for a GPU, so that's probably a moot point.

      Given the security holes in browsers' JavaScript sandboxing over the past few years, I'm also not completely convinced that this is more secure than just installing a CODEC once for each format that you want to play.

      Such a design would be inherently a lot more secure than installing native code. For one thing, bugs in the JavaScript engine notwithstanding, you can't generate out-of-bounds memory accesses or call arbitrary native code functions using JavaScript. The ability to restrict the developer to a very limited set of calls (with no developer-accessible pointers, per se) means that they can't, for example, read and write arbitrary files on your hard drive, change random preferences, or open a port 25 connection and send a death threat to the President. Any security problems caused by bugs in the engine are likely to be present in the engine even if you don't expose this additional use of the engine, making any argument about whether this is a good idea based on that rather moot.

      Besides, the point of using JavaScript was not security. The point was to create a CPU-agnostic (or even GPU-agnostic) codec API designed as a simple filter (compressed data in, uncompressed frames out). The security bit basically comes for free in such a design; it's hard for code that can only call specific functions and shares no variables (two ring buffers notwithstanding) with any other running code t

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    32. Re:First Post by dgatwood · · Score: 1

      Why would they want to? Internet Explorer and Safari play H.264 just fine so where's the incentive for Microsoft and Apple? Google already has ffmpeg built in and most likely won't want to absorb another codec (interface).

      The same reason Apple supports NPAPI, and in fact, has been a major contributor to the modernization of NPAPI recently---so that they can point to documentation and say, "Tell the developer to code their page right" instead of saying, "Sorry, that doesn't work in our browser. Use FireFox for that site." As for Internet Explorer, the only reason they're not in the same position as Apple is that they still have the dominant position. Give them a few more years of continuous market share losses, and I'm pretty sure you'll see them coming around to the importance of standards. They are already showing some indication that they "get it" inasmuch as they are supporting the <video> and <audio> tags in IE 9.

      Plus, Opera's method of just leveraging codecs the system has does the same without duplicationg data and without requiring the user to figure out which website to trust when downloading codecs.

      No, it really doesn't. For non-default codecs (e.g. Theora), the Opera scheme just forces the users to go out and search for the codec themselves, then download it as a system codec, and then decide whether to trust it or not. Moving the trust problem around a little does not eliminate it in any way.

      Further, the design I would suggest for this programming interface is such that the user shouldn't have to care whether that plug-in from girlswithbigtits.cn is safe in the first place. The JavaScript you got from loading the page itself could do more damage. The plug-ins would not talk to the GPU. They would perform operations on blocks of data, which the browser would compile into either native CPU or GPU functions that operate on the actual data. This makes the risk of them interfering with anything else your CPU or GPU is doing fairly minimal, and the total exposed surface far, far smaller than the main JavaScript engine, or even the HTML parser or PNG renderer....

      Put another way, yes, it would be a bit of an added security risk, but orders of magnitude lower than any native plug-in or codec, which is what people will end up using in the absence of such a feature. :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    33. Re:First Post by Anonymous Coward · · Score: 0

      it's not like when they come out with png they were worried about devices not being ready to use it. browser followed with the ability to display png, and then website were developed by it. will be the same: the first run will be h.264, xvid and maybe theora, and then an ubiquitous standard will emerge.

      and please, thora is a shitty codec, stop complain that it's not seriously considered as an h264 replacement, because it really isn't. go, make it better, and come back. you'll be surprised with the result when your code will suck less

      http://www.streaminglearningcenter.com/articles/ogg-vs-h264---round-one.html (somewhat discussed result by Greg Maxwell, but his line of defense 'it was done with an old codec' crumbled when asked for which code to use: 'the one not yet released')

    34. Re:First Post by nog_lorp · · Score: 1

      Bullshit. How is Firefox going to support H.264 out of the box? The entire point of this discussion is to stop users from having to run around downloading "codec packs".

    35. Re:First Post by nog_lorp · · Score: 1

      Mobile support is the kind of thing worth adding an H.264 encoded video along with a Theora video for.

      Any web content requires special considerations for mobile, and that is simply one of them.

    36. Re:First Post by hkmwbz · · Score: 1

      For the same reason we standardize markup around W3C HTML5, we standardize video around MPEG-4 H.264.

      Not for the same reason. W3C standards are open and free. H.264 is patent-encumbered and therefore closed. It is in no way like any open web standard.

      --
      Clever signature text goes here.
  2. Patent risks by Elektroschock · · Score: 4, Insightful

    If you want to get rid off patent risks abolish software patenting of technical standards, embrace open standards.

    1. Re:Patent risks by bunratty · · Score: 1

      The website sure makes a whole lot more sense than the arguments against software patents I saw on Slashdot last week (main argument -- ideas can't be patented LOL). But it still doesn't seem to be able to explain why absolutely all software patents should be abolished.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:Patent risks by Toonol · · Score: 1

      Why should they be allowed? Not allowing patents is the default position. There are a lot of ideas that can't be patented. I've written a book; I can't patent it, even though there are original ideas within.

      Before arguing that patents shouldn't cover software, there should first be some reasonable argument to extend them there in the first place.

    3. Re:Patent risks by bunratty · · Score: 1

      First, inventions are what can be patented. If you invent an algorithm, why should you not be allowed to patent it?

      Second, we don't need any argument to extend patents to algorithms. They already are. If you want to abolish software patents, however, you should make a good case for that move.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    4. Re:Patent risks by Sir_Lewk · · Score: 5, Insightful

      You keep on bring this up. The answer is, and always will be, because software is math. Under US patent law math is not supposed to be patentable.

      You might not agree with this, but that is in fact why most of us argue that software should not be patentable. I suspect you confuse comprehension with agreement.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    5. Re:Patent risks by Anonymous Coward · · Score: 0

      Algorithms are math, and math is not patentable. There are various reasons for this, and many of them are good ones.

      and so software shouldn't be patentable.

    6. Re:Patent risks by Toonol · · Score: 2, Informative

      First, inventions are what can be patented. If you invent an algorithm, why should you not be allowed to patent it?

      It stretches the definition of 'invention' to claim that algorithms are inventions.

      Second, we don't need any argument to extend patents to algorithms. They already are. If you want to abolish software patents, however, you should make a good case for that move.

      They aren't patentable in most of the world, nor were they even here for the period of most explosive growth of software. Software patents are a bit of an anomaly, and their presence still needs justification.

    7. Re:Patent risks by TheRaven64 · · Score: 1

      I think you have the question back to front. The default state is no enforcement of any intellectual property. Governments introduced things like copyright and patents because they believed there to be a positive benefit from doing so. Patents were encouraged during the industrial revolution because everyone was spending a lot of time obfuscating their ideas and ending up inventing the same thing. By agreeing to enforce a temporary monopoly in exchange for disclosure, the government encouraged inventors to share ideas, which sped up development.

      It is clear that patents have both positive and negative effects. By enforcing a monopoly, they make it harder to build new things using existing ideas. By requiring disclosure, they make building on the ideas of others easier. The question that needs to be asked is which of these two effects is dominant in the case of software.

      It is easy to point to examples of harm to the industry caused by software patents. The Eolas patent alone cost Microsoft half a billion dollars and looks likely to cause the rest of the industry even more. It is much harder to point to examples of patents that have benefitted the industry.

      Things like H.264 are examples of things that are certainly nontrivial to invent, but the question is would they have been invented without patents? A lot of the work in that area is conducted in universities with public money, so that part would have been. What about commercially? Given the huge amount of money that can be made with a decent CODEC by the film industry, it seems pretty obvious that the research and development would have been funded even without patents. I'd cite DIRAC as evidence of this: The BBC requires an efficient CODEC to deploy, so they funded the creation of one (which is patent free and open source). If H.264 had not been developed for licensing, it would almost certainly have been developed by funding from film and TV companies, or even by the likes of Sony for use on BluRay disks: being able to store a reasonable amount of HD video on a single disk makes it much easier for Sony to license BD to third parties.

      --
      I am TheRaven on Soylent News
    8. Re:Patent risks by bunratty · · Score: 1
      I suspect that the actual reason most people here are against software patents has no resemblance whatsoever for the arguments against software patents you're presenting. I think the reasoning given in the website is far more reasonable and, frankly, honest.

      Software patents miss their legitimate purpose. Patents on software favour litigation in detriment of innovation, defeating their democratic justification. They force software producers to spend on bureaucracy, lawsuits, and circumventing dubious granted claims on software what would otherwise be spent on Research and Development. Owners of patents on software, who sometimes doesn't produce software themselves, obtain a means to exert unfair control over the market.

      That's a much better argument than simply stating "software is math" over and over again.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    9. Re:Patent risks by Toonol · · Score: 1

      That's a much better argument than simply stating "software is math" over and over again.

      Unless software is math, in which case no better argument is needed.

    10. Re:Patent risks by funkatron · · Score: 2, Informative

      Well for a start software already gets copyright, there's no need for double protection. Secondly, the whole patent idea seems a little flawed. If you come up with an idea that solves a problem, that's great. If someone else faces the same problem, works on it and comes up with a similar solution, that's a patent violation. In effect you can sue people for accidents of history. If my second point gets corrected by someone who knows what they're talking about then refer to point 1.

      --
      "Welcome to our world. We are the wasted youth. And we are the future too." Yes, I know these are stupid lyrics.
    11. Re:Patent risks by Anonymous Coward · · Score: 0

      because the only way for trolls like you to have the needed scarcity is for the rest of us to live under your totalitarian regime.. thoughts can NOT EVER be treated as physical property. if you want to make some money from your ideas, go make something with a natural scarcity and sell it. quit demanding that the rest of us worship the emperor's new clothing.

    12. Re:Patent risks by Sir_Lewk · · Score: 1

      Well then congratulations. You have discovered why people don't like software patents and have completed your quest for knowledge. Happy yet?

      Also, it should be noted that stopsoftwarepatents.eu is of course an EU website. You'll note that more American centric commentary often brings up the non-patent-ability of math.

      Citation: Donald Knuth

      To a computer scientist, this makes no sense, because every algorithm is as mathematical as anything could be. An algorithm is an abstract concept unrelated to physical laws of the universe.

      http://progfree.org/Patents/knuth-to-pto.txt

      For more examples of this argument being made, see EndSoftPatents.org.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    13. Re:Patent risks by im_thatoneguy · · Score: 3, Funny

      So just because it's on a computer and not manufactured it shouldn't be patented. Poppy-cock.

      The virtual world should get the same protection as meatspace. If you invent a new non-obvious widget you should be able to patent it regardless if a CNC machine or injection molder was required to manufacture it.

    14. Re:Patent risks by im_thatoneguy · · Score: 1

      Given the huge amount of money that can be made with a decent CODEC by the film industry, it seems pretty obvious that the research and development would have been funded even without patents.

      If there is sufficient motivation to create open source patent free licenses then they'll happen regardless if there are patented competitors.

      This is a case where the FOSS community wants all of the benefits of patented software which is in this case technically superior without having to pay for it.

    15. Re:Patent risks by Sir_Lewk · · Score: 1

      More links for you, because I'm feeling generous (and bored):

      Tones of links at groklaw, more than a few that take the "software is math" angle
      A very blunt, and to the point page from End Soft Patents.

      I did not just make this argument up off the top of my head. I promise you I'm not that creative. It is a very common argument, and generally considered to be very strong, since it's a pretty damned simple logical statement: A = B, B != C, thus A != C. You could find elementary school students to explain it to you I'm sure.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    16. Re:Patent risks by EvanED · · Score: 2, Insightful

      Unfortunately you're dealing with someone who is quite clearly not a computer scientist or mathematician.

      Huh?

      I consider myself a computer scientist (and the fact that I have a BS in both math and comp sci and am halfwayish through a CS PhD program would seem to support that assertion), and I firmly believe that a sufficiently clever algorithm is as much an invention as a sufficiently clever physical invention.

      Saying "algorithms are just math" is about as convincing to me as saying "your prototype is just matter."

    17. Re:Patent risks by EvanED · · Score: 2, Insightful

      BTW, that's not to say that I support the current status quo regarding software patents. I think software patents should undergo some reform to make them both more restrictive (Amazon one-click? really?) and probably shorter duration. That said, I definitely think something like the RSA algorithm was as worthy of a patent as most anything else out there.

    18. Re:Patent risks by Billly+Gates · · Score: 1

      The problem is open standards are being patented to force them to act like closed standards.

      A patent by definition creates a monopoly for a limited time. A monopoly is the opposite of a standard because only one company has a right to use it and own it. If a standard is patented and requires license then its not a standard but private property.

      OpenXML, .NET, and H.264 are all examples of standards. Can I be sued using them without a license even if they are free software? You bet! Which is why I do not use Mono or H.264.

    19. Re:Patent risks by Billly+Gates · · Score: 1

      I think the fact that software is patentable is the symptom rather than the cause of patenting math.

      The symptom is intense government corruption by the software. Something has to give as this country is moving far into this direction.

      Rather than whining I would advise people to look into organizations like the coffee party which are made up of a whole bunch of angry citizens who want to do something about this ... not just the TEA party.

      As soon as the country listens to us and not the corporations we will never have any rights and laws will not matter as they will be written to serve only the wealthy.

      Before I get modded down to an oblivion I would like to say the Coffee party is not affiliated with Obama in anyway nor is the founder even on the payroll of the democratas so please do not listen to Fox News with a knee jerk reaction.

    20. Re:Patent risks by Ihmhi · · Score: 1

      Just like the rules of a game can't be patented?

      The problem is that they can just change some wording. It would go from patenting the code to patenting the "Method and Apparatus" of the code, its execution, etc.

    21. Re:Patent risks by poetmatt · · Score: 1

      If you patent something that is intangible, that is against the intent of patents themselves. This is what is completely misunderstood.

      You have to be able to patent something specific and tangible because otherwise there is both a: no way to verify it and b: no way to work around it.

      If I were able to patent math, or a concept, which is too generic for a patent, what is to stop me from suing anyone for doing anything considered "Similar" to said concept? This is the issue. When you get down to patenting 2+2 that means you can stop people from patenting any form of math. See how this leads to a circular argument that only goes down the drain for inventors?

    22. Re:Patent risks by node+3 · · Score: 1

      Let's say your goal is to have a video format in the HTML spec that will be usable on handheld devices all the way up to desktop computers and TVs. With that in mind, do you think you'll have better chances of achieving that goal by railing against patents? Or by adopting a standard that already works on all of those devices with hardware acceleration, is top notch in terms of video and audio quality, and is already the predominant web format?

      I'm all for abolishing software patents. And I'm all for working towards that goal. But as far as addressing the problem at hand, h.264 is the right choice, and it's far more likely to be accomplished. I mean, really, it's a fait accompli. Only Mozilla[*] is standing in its way, and Mozilla stands zero chance in defeating h.264. The only things they might accomplish are bringing the issue of patents to light, and muddying up the HTML5 standard by not having a universally supported format.

      But in no way whatsoever will Mozilla stop h.264. If they don't ship with it, or without supporting a plugin that will play h.264 directly (without the overhead of Flash, but as a native HTML5 tag), then it's not h.264 that will fail, but Firefox. It will be a hockey stick downwards in the popularity of Firefox.

      The biggest problem is that Mozilla's argument isn't technical. It's political. If their stance at the very least had the quality of being technically superior, it'd be worth defending. But to support the inferior technology? WTF? "Use us, we suck most, but are ideologically pure!" is not a compelling rallying cry.

      [*] There's also Opera, but in terms of impact on web development, their contribution is negligible.

    23. Re:Patent risks by ceoyoyo · · Score: 1

      It's not a particularly good argument against software patents though. It's a good argument against poor software patents. The same argument works just as well against poor patents of any other sort.

      The "software is math" argument is silly as well. Software isn't math. Software is a set of instructions for doing something. The BEST patents are sets of instructions for doing something: industrial smelting and refining processes, for example.

    24. Re:Patent risks by Lars+T. · · Score: 0

      You keep on bring this up. The answer is, and always will be, because software is math. Under US patent law math is not supposed to be patentable.

      You might not agree with this, but that is in fact why most of us argue that software should not be patentable. I suspect you confuse comprehension with agreement.

      Yeah, exactly and math isn't patentable because Math isn't real science like building perpetual motion machines - which you can patent.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    25. Re:Patent risks by macro187 · · Score: 1

      This is a case where the FOSS community wants all of the benefits of patented software which is in this case technically superior without having to pay for it.

      What? Seems clear to me that the entire issue is that the FOSS community does not want the patented software.

      Also, what is an "open source patent free license"?

      You don't really know what you're talking about, do you...

    26. Re:Patent risks by johnncyber · · Score: 1

      That said, I definitely think something like the RSA algorithm was as worthy of a patent as most anything else out there.

      You do the realize that at the heart of the RSA algorithm (and most if not all cyptography algorthims for that matter) is a series of mathematical equations (See: http://en.wikipedia.org/wiki/RSA#Operation). Therefore under US law it should not be patentable, yet for some reason because it relates to computing it is was granted a patent.

    27. Re:Patent risks by Sir_Lewk · · Score: 1

      Actually, the USPTO no longer lets you patent perpetual motion machines.

      You are out of date on this subject, I'd take the time to catch up if I were you...

      Furthermore, Mathematics is not universally considered a science. and "being real science" is not the one and only test of patentability.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    28. Re:Patent risks by EvanED · · Score: 3, Insightful

      You do the realize that at the heart of the RSA algorithm (and most if not all cyptography algorthims for that matter) is a series of mathematical equations...

      You could say the same thing about physical inventions, and it would only be a bit more far-fetched IMO. "At the heart of an internal combustion engine is just the physical principle that a fuel-air mixture burning will create an increase in volume." The presumably patentable thing in the case of the internal combustion engine is the clever idea that you can harness that increase in volume to turn linear motion into rotational motion, and use that to, for instance, move a car forward. Similarly, there may "just" be some number theory behind the RSA algorithm, but the thing I think should be patentable in its case is the clever idea that you can harness those equations in order to do public-key cryptography.

      (I don't actually know whether the internal combustion engine was patented, or what parts of it were, etc.; but you get the idea.)

      Therefore under US law it should not be patentable, yet for some reason because it relates to computing it is was granted a patent.

      I can't speak to what should or shouldn't be patentable under current law; I'm just saying that I think a system that allows at least some aspects of software to be patented makes perfect sense.

    29. Re:Patent risks by Sir_Lewk · · Score: 1

      Yeah, no kidding. These loons would apparently see nothing wrong with Pythagoras patenting his little theorem back in the day either. Truly boggles the mind.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    30. Re:Patent risks by Sir_Lewk · · Score: 1

      You could say the same thing about physical inventions

      There is a difference between "describe-able with math" and "is math".

      I can't speak to what should or shouldn't be patentable under current law

      Ahhh..... Not really sure why I am bothering to have this conversation in that case.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    31. Re:Patent risks by b4dc0d3r · · Score: 5, Interesting

      Nope it's dishonest. The same thing applies to software and hardware patents. There's no distinction in that explanation that cannot be applied to mechanical inventions. You've made the case for voiding all patents, not just software.

      A far more coherent argument would include the rapid evolution of software, with examples such as GIF. Of course GIF is a special case which allowed a better candidate, PNG, to become more common (with a side journey into IE's market dominance holding back PNG acceptance while IE's PNG support sucked). So GIF encouraged invention, the "legitimate purpose" of patents. So a good argument is difficult to make.

      Very simply, math is abstract and remains free. The formula to calculate mortgage interest, or the location of a thrown object given the initial vector, gravity, atmospheric pressure (density), and external force such as wind, are not patentable. You can discover them and write papers and be influential in the field, but never patent it.

      PKZIP had a patented compression method. Zlib did the same thing, just using a different method, and created compatible files. MP3 encoders bypassed Fraunhofer patents. Maybe the output wasn't byte-for-byte the same, nor the compression levels equal, but there is a serious hole in the argument for software patents when you can just do the same thing a different way and get around the patent.

      The answer to Microsoft's Linux patent FUD is: Show us the patent, we'll work around it. The only place that fails is specific implementations like H.264 or FAT LFN or MPEG or SMB which are multi-platform. You can't program around a patented file format. Did you know that reverse engineering is valid for compatibility purposes? Why would that exist if not for a purpose? Then when you successfully reverse engineer something for compatibility, you can't use it because of patents. Why even have that exception if patents make it irrelevant?

      That's my main argument these days - if I can break the DMCA for interoperability, I can ignore patents for the same reason.

      The perfect mouse trap is invented, or the perfect lawn mower. I can choose to buy the patented solution, or go with a competitor. I buy in, paying extra for the patented hardware, and break a part. Is it allowed to fabricate my own parts to replace a broken one? Not if it violates the patent. So why can I reverse engineer for software interoperability, but I can't for hardware? Law may say one thing, here's my argument.

      Hardware which is validly patentable does not have an interoperability requirement. Your saw does not have to work with other saws, so the parts may be patented. A company like Black and Decker could patent a battery which powers their tools, and they would own interoperability among products but I'm free to choose a competitor or build my own, which need no interoperability.

      Software patents are increasingly used to protect a desirable object, so that content creators or consumers or both have to pay to create and/or access the content. Here's a new video codec, use it for a while while we hammer out the standards, then I pull the trigger and require payments. If you are the sole distributor of content and content will be consumed on your device (such as Pez and the Pez dispenser), patent away. But a method of packing up video to be shared with your devices, other companies, competitors and those in unrelated fields - interoperability is a requirement, and patents simply don't make sense.

      I have a mathematical algorithm which uses psychoacoustic modeling to reduce the audio data which must be encoded, resulting in smaller files. Brilliant idea, which is unpatentable by itself. The algorithm is unpatentable by itself. I can develop a separate model to accomplish the same thing, better, using the exact same algorithm (with a different model underneath). Psychoacoustics happens to be a fundamental part of the universe, which should be unpatentable like (natural) DNA is, or a description of gravity.

      So I u

    32. Re:Patent risks by cyberthanasis12 · · Score: 1

      Donald Knuth has stated that algorithms ARE math. Do you know better?

    33. Re:Patent risks by pem · · Score: 4, Interesting

      There is a difference between "describe-able with math" and "is math".

      Perhaps, but that difference is small, and shrinking everyday. I think that is why several people, including myself, feel that it is splitting hairs to let the whole math thing get in the way of the debate. It's a distraction. I believe that most, if not all software patents are bogus, and many hardware patents are bogus, but that does not *necessarily* mean that there should be no software patents, just that we're going about the whole patenting thing the wrong way.

      Or to put it another way....

      Simulations of CMOS computer chips are so good that (in most cases, if you are not doing a shrink to a new node where there are new physical problems to find), if you design a circuit, you can simulate it (using software), and have well above 90% confidence that it will work just like your sim after you spend a million bucks to build a mask set to do the photolithography do do the chip. (If you think about it, that must be true, else no one would bother building any really dense silicon chips at all because it would be too risky.)

      SO...

      The design, as simulated by the computer, just using software and math, is not patentable, because it's "just math." But OTOH, the design, as put into the real hardware, should then not be patentable, because its operation is utterly predictable (and predicted) by the non-patentable prior-art act of simulating it!

      Now, you can use all the weasel words you want to distinguish the hardware from the software, and in fact, this is probably, kind of, sort of, how we got to the weasel words that allow software patenting "in conjunction with a machine." BUT, there is (to my mind) a fundamental problem that a chip designer using math and software tools to build hardware is not doing a job that is FUNDAMENTALLY more difficult or technical, or more important to the economy, or which requires more invention, or greater math skills, or even skills which are really that different than a lot of highly skilled software designers.

      So, what distinguishes the results to make one patentable and the other one not. Well, we've already got "one is realized in real hardware." OK, where does that leave a logic design that could be stuffed into an FPGA or into a real chip? In one case, it's quasi-software -- easily reprogrammable, arguably as non-patentable as software should be. In the other case, it's an invention realized in hardware.

      For a living, I write software, I write hardware that gets synthesized into CMOS, and I do emulation of the hardware in FPGAs. To me, these are all fundamentally the same, and it would be intellectually dishonest for me to argue otherwise. OTOH, I am the inventor or co-inventor of 16 patents, mostly hardware, and mostly junk -- the kind of patents that big companies put in their arsenals for the whole "mutually assured destruction" thing that fell apart with the arrival of non-practicing patent trolls.

      So, my opinion is that the system is broken, but that in trying to fix the system, it is a counterproductive distraction to try to split hairs between hardware and software.

    34. Re:Patent risks by westlake · · Score: 0, Offtopic

      The answer is, and always will be, because software is math.

      Patents are traditionally awarded to the man who sees a problem and find a creative and practical solution that has eluded everyone else who began with the same knowledge and resources.

      Math and logic are simply tools - as accessible to the machinist as they are to the programmer.
       

    35. Re:Patent risks by naasking · · Score: 1

      That argument can equally be applied to legitimate patents, and so is not an argument at all. The reason math and software cannot and should not be patented is because software is a description of abstract ideas, where patents protect physical inventions. If you cannot patent Harry Potter, then you cannot patent software.

      We already have protection of abstract ideas called "copyright". Abstract ideas and physical devices have very different properties which is why the rules governing their use are so different; physical devices require tools and raw materials to copy, where abstract ideas do not. This is why software and math both belong under copyright and have no place gaining patent protection.

      I've debated this issue a thousand times on reddit, so I'll just point you to the good posts here, here, here, and this epic thread.

    36. Re:Patent risks by naasking · · Score: 1

      and I firmly believe that a sufficiently clever algorithm is as much an invention as a sufficiently clever physical invention.

      Harry Potter was just as much an invention as a clever physical device. That's not an argument to allow patenting of Harry Potter now is it? See my post above for why math and software should not get patent protection, or if the only way to end this silly debate is to allow it, why those patents should have significantly reduced durations.

    37. Re:Patent risks by jim_v2000 · · Score: 1

      Can't any processs be broken down to math? I don't see how that argument really suggests that software patents are invalid.

      --
      Don't take life so seriously. No one makes it out alive.
    38. Re:Patent risks by Cidolfas · · Score: 1

      Software patents are a bit of an anomaly, and their presence still needs justification.

      How does a brown paper bag full of Benjamin Franklin marked "Campaign to Re-elect Senator ????" sound for a justification? It'll be waiting behind the usual dumpter (you know, the one in the Microsoft parking lot).

      --
      I am become /dev/null, destroyer of data.
    39. Re:Patent risks by naasking · · Score: 1

      Software is a set of instructions for doing something.

      And math is not a set of instructions for doing something? That one sentence describes exactly what constitutes math. It also describes exactly what is not patentable, ie. abstract ideas. What is patentable is a physical invention that implements a particular set of instructions.

    40. Re:Patent risks by jim_v2000 · · Score: 1

      Actually, no. The difference is that one accomplishes a task, the other does not.

      --
      Don't take life so seriously. No one makes it out alive.
    41. Re:Patent risks by jim_v2000 · · Score: 1

      It's so strong that there's no such thing as a software patent in the US, right?

      --
      Don't take life so seriously. No one makes it out alive.
    42. Re:Patent risks by naasking · · Score: 1

      No, the physical machine that executes the program accomplishes the task, and the machine itself is patentable. The software is merely a description, like a story about Harry Potter, or a physics paper, and thus subject only to copyright.

    43. Re:Patent risks by GigaplexNZ · · Score: 1

      If there is sufficient motivation to create open source patent free licenses then they'll happen...

      It isn't the license of the OSS that needs to be aware of the patents. If the software does something that a different piece of patented software does, then it is infringing. During the development of the Dirac codec, they had to peruse existing patents and make sure what they implemented didn't infringe (to the best of their knowledge) on existing patents. It isn't quick or easy to know whether you infringe on someone else.

      ...then they'll happen regardless if there are patented competitors

      If what they want to implement has already been patented by competitors, then they can't implement it without an agreement with the patent holder or risk of lawsuit.

      This is a case where the FOSS community wants all of the benefits of patented software

      The FOSS community doesn't want patents at all, and instead prefer to rely on copyright for protection of software. It's easy to avoid copyright infringement, just don't copy the code. It's hard to avoid patent infringement, accidentally coming up with the same idea independently without knowing you did is enough to screw you over.

    44. Re:Patent risks by Cidolfas · · Score: 1

      If I were able to patent math, or a concept, which is too generic for a patent, what is to stop me from suing anyone for doing anything considered "Similar" to said concept? This is the issue. When you get down to patenting 2+2 that means you can stop people from patenting any form of math. See how this leads to a circular argument that only goes down the drain for inventors?

      Unless the inventors work for a company with the legal and financial muscle to compete. I'm really jaded (especially in presentation), but the system really is set up so that innovation can be stifled so that large entities who could be destroyed (in whole or in part) by rapid market innovation don't have to worry. I know the system is set up in such a way that it's supposed to protect the very people it stifles from having their ideas stolen instead of bought, but the practice of overly-broad generic patents on basic concepts in many fields has created litigious loopholes which allows the giants to reverse the tables on the small innovator, forcing them to sell the idea or face a patent suit that will bankrupt them before discovery is finished. (Holy run-on sentence Batman!) I don't like that setup, I'd rather let market forces subject only to anti-collusion and anti-price-fixing regulations reach a similar end effect in the marketplace independent of the litigation.

      --
      I am become /dev/null, destroyer of data.
    45. Re:Patent risks by ceoyoyo · · Score: 1

      No, math is not instructions for doing something. If you want a one sentence summary of math it would be more like "a collection of consequences of a set of axioms."

      Here's some very simple math:

      ax+b = c

      Now, what part of that says "a set of instructions" to you?

    46. Re:Patent risks by naasking · · Score: 2, Informative

      Oh ye of little imagination. The algebraic expression you provided is a parameterized program with unknown variables x, a, b, c. You have provided exactly a simple program which can be evaluated, once the variables are provided, by the rules of algebra, which form the instructions of the machine that can execute this program.

      See the Curry-Howard correspondence for a formal proof of this. Types are logical propositions, and programs are proofs. It is a mathematical fact that programs are math, that the instructions of a machine correspond to the axioms of a formal/mathematical system, and that "sets/sequences of instructions" correspond exactly to mathematical proofs.

    47. Re:Patent risks by walshy007 · · Score: 1

      replying to undo accidental bad moderation

    48. Re:Patent risks by Sir_Lewk · · Score: 1

      The government royally fucks something up and acts illogically. News at 11. ...doesn't make it right.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    49. Re:Patent risks by Sir_Lewk · · Score: 1

      You're right. Software isn't math. Turing, Church, Knuth, etc were all wrong for all of those years!

      Westlake has proven them wrong and defied solid logic and mathematics with the simple words: "Math and logic are simply tools - as accessible to the machinist as they are to the programmer."! Stop the presses and re-write the math books, westlake has changed everything!

      For his next act westlake is going to solve world hunger by suggesting that everyone without bread simply eat cake!

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    50. Re:Patent risks by Anonymous Coward · · Score: 0

      Well for a start software already gets copyright, there's no need for double protection.

      Software gets copyright protection to bring it up to the same level as real property, so there's still no extra protection overall.

    51. Re:Patent risks by gnupun · · Score: 1

      If you patent something that is intangible, that is against the intent of patents themselves. This is what is completely misunderstood.

      Sorry, but software is a tangible machine than runs off another tangible machine called the CPU. Software is tangible because it is always stored in a sequence of 1s and 0s on some tangible medium such as a disc. Math does not operate any machinery that we know of although mechanical, electrical and computer engineers use math extensively to develop their technologies. Math does not require a CPU or any other technology to be useful whereas without a CPU, all software is useless.

      Therefore, software should be patentable, just as electronics hardware is. After all, today's patentable electronics hardware is developed using VHDL (like Pascal/Ada) or Verilog (C). So why should software be discriminated against?

    52. Re:Patent risks by logixoul · · Score: 1

      Had he patented it, it would've expired in a couple of years and all would be the same. What's your point?

    53. Re:Patent risks by harlows_monkeys · · Score: 1

      Algorithms are math, and math is not patentable. There are various reasons for this, and many of them are good ones.

      Mechanical devices are physics, and physics is not patentable. There are various reasons for this, and many of them are good ones.

      and so software shouldn't be patentable.

      and so mechanical devices shouldn't be patentable.

    54. Re:Patent risks by gnupun · · Score: 1

      Well for a start software already gets copyright, there's no need for double protection. Secondly, the whole patent idea seems a little flawed...

      Fine, why don't you write a successful, profit-making software that has some new, innovative technology. I will just look at the disassembly of the innovative algorithms, figure out how they work and rewrite in another language and slightly change the structure/variable names etc. to avoid copyright infringement and make big bucks off your talent.

    55. Re:Patent risks by harlows_monkeys · · Score: 1

      You keep on bring this up. The answer is, and always will be, because software is math [wikipedia.org]. Under US patent law math is not supposed to be patentable.

      Software is math in the same sense that any physical device is physics, and so you could make the exact same argument against all non-software, non-business method patents, since physics is not patentable.

    56. Re:Patent risks by evilviper · · Score: 1

      Sadly few have realized (despite it being the main focus of most of those articles, but hey, who reads those) that quality will not be the merit to win this battle.

      Abolishing software patents will work wonderfully for your PC... It will likely do absolutely nothing for your cell phone, however. Note that MP3 decoder software is unencumbered in countries that ignore software patents, but MP3 decoder software burned into the Flash chips of MP3 players need to be licensed...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    57. Re:Patent risks by Nikker · · Score: 1

      I do agree that if you were to or have created an algorithm that preformed a task in an incredibly unique or efficient way you should be able to be protected from people using your particular algorithm but you cannot stop someone from preforming the actual task. That is the main issue in software patents especially as we have seen in something as simple as VOIP where the "patent" holder did not pursue the algorithm but the task its self saying the mere act of sending data via separate networks that is intended to represent audio was theirs and theirs alone. If they came up with a very efficient way to facilitate such a task then great but there is no way anyone should be able to stop me from sending raw wave form data through a network. At the end of the day if you develop a logic system you own that exact sequence of events no more no less, they are just math but you do own the copyright if you can prove you were the first one to do it but you cannot patent the input or the result, just your transition between the two.

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    58. Re:Patent risks by TheTurtlesMoves · · Score: 1

      However both RSA and DH is/was patented in the US and enforced!

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    59. Re:Patent risks by Nikker · · Score: 1

      You could patent the size of your combustion chamber, the length of your push rods, the dimensions of your crank shaft and the exact design of your fuel delivery system but you cannot patent the laws of Physics that allow you to harness combustion and demand all uses of combustion to be your invention. You mention you have a strong maths and CS background but listening to your posts is like Microsoft saying they should be able to patent the concept of the operating system, you have a great interest in your claims.

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    60. Re:Patent risks by Anonymous Coward · · Score: 0

      No. A chip is a machine that does math.
      What you are simulating is the math output of that chip, not the chip itself. You can simulate chips you cannot even make.

      Simulating and making is not the same thing. We can simulate lots of things with computers and not all are possible with our technology. We can simulate space travel faster than our current space vehicles. We can simulate an entire building during an earthquake. But all of those simulations are mathematical approximations. Guessings made by a calculator.

      Then you have to deal with this 'less than 10%' of 'unexpected' that the simulation was unable to simulate.

    61. Re:Patent risks by evilviper · · Score: 1

      A lot of the work in that area is conducted in universities with public money, so that part would have been. What about commercially? Given the huge amount of money that can be made with a decent CODEC by the film industry, it seems pretty obvious that the research and development would have been funded even without patents.

      The H.264 patent list for companies vastly overwhelms those from Universities. Besides, even if ALL the patents were owned by universities, there would be no standards group to put them all together, and make a product out of it. I believe MPEG-2 would have happened if patents didn't exist, but MPEG-4 and H.264 was a VASTLY more involved and complex undertaking.

      H.264 is also all about low-bitrate streaming video. It really doesn't perform significantly better than MPEG-2 when you get into high bitrates, as you're talking about.

      So we can pretty well say that H.264 in particular, would have no chance of happening in a world without patents, and software patents in particular.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    62. Re:Patent risks by jesset77 · · Score: 1, Insightful

      If there is sufficient motivation to create open source patent free licenses then they'll happen regardless if there are patented competitors.

      This is a case where the FOSS community wants all of the benefits of patented software which is in this case technically superior without having to pay for it.

      I'm sorry, the FOSS community wants what now? Most of the FOSS community backs Theora. Toe to toe, H.264's superiority of Theora is marginal. It's main claim to fame is simple Ubiquity. Most embedded devices choose to hardware accelerate H.264 instead of Theora, with the net effect that I (as a video producer and distributer) will likely be forced to pay royalties at some unspecified time in the future per consumer of my work in order to take advantage of said short-sighted hardware support decisions.

      Next will you argue that Internet Explorer is "superior" to Safari simply because more computers have it installed at present, or because it appears faster when you click the little "e" due to components automatically preloading with Windows?

      --
      People willing to trade their freedom of expression for temporary entertainment deserve neither and will lose both.
    63. Re:Patent risks by Nikker · · Score: 1

      Step 1) multiply a by x
      Step 2) add result to b

      So unless multiplication and subtraction were not implied "instructions" by that algorithm then you are right.

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    64. Re:Patent risks by jesset77 · · Score: 1

      The virtual world should get the same protection as meatspace.

      Feh, I'll just wait around on your WoW server until you PK someone and then have you arrested for murder.

      --
      People willing to trade their freedom of expression for temporary entertainment deserve neither and will lose both.
    65. Re:Patent risks by EvanED · · Score: 1

      You could patent the size of your combustion chamber, the length of your push rods, the dimensions of your crank shaft and the exact design of your fuel delivery system but you cannot patent the laws of Physics that allow you to harness combustion and demand all uses of combustion to be your invention.

      You seriously think that the guy who invented the internal combustion engine* could have patented all those dimensions and such, but shouldn't have been able to patent something as general as "a motor that operates by drawing fuel into a combustion chamber through a valve, closing that valve, compressing the fuel and air, igniting it, opening a valve, and exhausting the burned products through that valve during four successive strokes"?

      If so, then we disagree on rather more than just software patents. ;-)

      * Disclaimer: I'm not sure how discrete this invention actually was; for purposes of argument, assume that the idea was suitably novel.

    66. Re:Patent risks by jesset77 · · Score: 1

      "Use us, we're 7% slower, but we won't grab your balls and gouge you to death with arbitrarily decided licencing fees a year or two from now!"

      It's just, you know, you had this typo. there. Spell checker doesn't catch those.

      --
      People willing to trade their freedom of expression for temporary entertainment deserve neither and will lose both.
    67. Re:Patent risks by nog_lorp · · Score: 1

      True. Or, at least, it should be recognized that many things patentable today constitute some of the only reasonable ways to solve a common problem. Like "method of swinging on a swing" http://www.google.com/patents?id=T2QKAAAAEBAJ.

      When someone engineers a basic combination of a couple of algorithms, they should either be denied a patent or receive, at most, a year of exclusive use.

      One year is plenty of time to monetize on a useful idea.

    68. Re:Patent risks by EvanED · · Score: 1

      I do agree that if you were to or have created an algorithm that preformed a task in an incredibly unique or efficient way you should be able to be protected from people using your particular algorithm but you cannot stop someone from preforming the actual task.

      I really like these words, but I think we still may disagree on what extent software "inventions" should be patentable.

      The problem I see is a lot of the time, "algorithm" and "task" are pretty tightly intertwined; further, I think we would often take different positions on which is which. Take the decryption portion of RSA. I would say that the task it performs is "given a cyphertext c that was encrypted with RSA, along with the private key (n,d), determine the original message." I would say the algorithm for decryption is "take c^d modulo n." But in this case, the algorithm is the only way to accomplish that particular task. (Except for brute force search and the NSA's super-secret RSA-breaker, neither of which I think should be covered by an RSA patent.)

      In the context of H.264, I suspect the case is similar: presumably there are steps of the encoding and decoding process that can only be done (at least by current knowledge) in one particular way; and these would then presumably be reasonably valid candidates for a software patent.

      At the end of the day if you develop a logic system you own that exact sequence of events no more no less, they are just math but you do own the copyright if you can prove you were the first one to do it but you cannot patent the input or the result, just your transition between the two.

      Maybe what we really need is something between the two, or a special kind of patent. The problem I have with all the people saying "software gets copyrighted" is I don't think that protection goes far enough. If I give you a general description of (to use my example from the other portion of this thread) an internal combustion engine, some machining tools, and a bunch of time and hunks of metal, you might be able to develop your own engine. It'd probably look quite a bit different from the original one, yet the physical patent presumably would cover your reengineered version. (See my reply to another of your posts in this thread.) And I think that position is quite reasonable. Yet if I give you a general description of the RSA algorithm and you go implement it, copyright alone doesn't cover your reengineered effort (which is the whole purpose of a cleanroom implementation). But I think there are plenty of things in the software world that are deserving of such protection.

      (Perhaps I should justify that last statement a bit more. Why are copyright and patents, in general, a good thing? The reason is that they protect R&D investments in some sense, because someone can't take the money and effort that you invested figuring out how to do something (e.g. make an engine) and just copy it, until you've had a bit of time to recoup your losses yourself. When actually selling whatever product is the consequence of the R&D, you have to charge the incremental cost of whatever you're selling plus something to recoup your investment, while a "pirate" would only have to charge the incremental cost. The pirate thus undercuts your price, and "robs" you of sales. This general principle is true of both copyright and patents.

      And I don't understand why so many people here (many more than seem to be against copyright and patents in general) think that this principle applies to algorithms and software any less than another invention. Algorithms still have a R&D cost. How many different things did R, S, and A try before coming up with something that worked? How much effort was put into figuring out how H.264 should drop out things that don't matter to the viewer? To me, saying that things like these shouldn't be patentable, if you accept non-software patents, is saying the R&D cost of algorithms is zero. And I don't understand how you can take that last position.)

    69. Re:Patent risks by dhalgren · · Score: 1

      Mechanical devices are physics, and physics is not patentable. There are various reasons for this, and many of them are good ones.

      Mechanical devices are not physics, they are the application of ideas which are confirmed by physics. In other words, they are technology, not science.

    70. Re:Patent risks by macro187 · · Score: 2, Funny

      The biggest problem is that Mozilla's argument isn't technical. It's political.

      Of course it's political. It's power. Power that a whole lot of people have spent the past decade voluntarily building up, to counterbalance corporate attempts to monopolise the web.

      If that work hadn't been done, and Firefox didn't have the market share -- and therefore power -- that it has today, we wouldn't even be having this discussion. Because this entire issue would have been decided behind closed doors in some boardroom at Microsoft.

      We're on the brink of seeing the last piece-of-shit corporate dependency -- Flash -- removed from the web.

      Anyone advocating throwing that away in exchange for some minor technical advantage is either young, stupid, or suffering from a severe case of Stockholm Syndrome.

      Wake up, Serf.

    71. Re:Patent risks by nog_lorp · · Score: 1

      Well, that is really too bad.

      I think it is more important to protect an individuals right to have ideas, than it is to protect an individuals right to exclusivity in those ideas.

      It is impossible for me to engineer anything and ensure that I am not violating any idea anyone has ever claimed exclusivity to.

    72. Re:Patent risks by nog_lorp · · Score: 1

      Well, that is really too bad.

      I think it is more important to protect an individuals right to have ideas, than it is to protect an individuals right to exclusivity in those ideas.

      It is impossible for me to engineer anything and ensure that I am not violating any idea anyone has ever claimed exclusivity to.

    73. Re:Patent risks by nog_lorp · · Score: 2, Insightful

      Erm. Software is, fundamentally, a collection of data inputs and NAND logic that is stored physically somewhere. The fact is, it is a mathematical logic construct that is being covered under a software patent. The data that represents the software is NOT patentable, it is copyrightable.

      The abstract design of a physical application has many, many more variables than the abstract design of a mathematical construct, and exclusivity of a physical design rarely prohibits all other innovators from making progress without it.

    74. Re:Patent risks by Bugamn · · Score: 1

      Isn't everything math, according to some philosofers? Could we use that to finish all patents?

    75. Re:Patent risks by makomk · · Score: 1

      Not only is RSA a series of mathematical equations, it's been discovered at least twice entirely independently (and possibly even more times - the NSA won't admit either way).

    76. Re:Patent risks by makomk · · Score: 1

      Software is math in the same sense that any physical device is physics

      Nope. Physical devices are merely an application of physics. Software is maths.

    77. Re:Patent risks by sopssa · · Score: 1

      Mechanical devices are not physics, they are the application of ideas which are confirmed by physics. In other words, they are technology, not science.

      So just like computer algorithms are application of ideas which are confirmed by math?

      And it's not like software patents often involve any specific math - they involve the idea or outcome in very specific terms.

    78. Re:Patent risks by harlows_monkeys · · Score: 1

      Nope. Physical devices are merely an application of physics. Software is maths

      Software is not math. It is at best an application of math.

    79. Re:Patent risks by gnupun · · Score: 1

      Software is, fundamentally, a collection of data inputs and NAND logic

      Well, everything can be modeled and represented as a collection of data, including planet earth and every single thing on it. In this case, the software is both a collection of data and a complex machine.

      The data that represents the software is NOT patentable, it is copyrightable.

      By that retarded logic nothing is patentable, since every machine invented by man can be represented as data on a computer somewhere -- every machinery involved in cars, factories, buildings, electronics etc.

    80. Re:Patent risks by Darren+Winsper · · Score: 2, Insightful

      No. Algorithms are the maths. An implementation of the algorithm is the application. However, we already have a system for protecting implementations of algorithms, we call it copyright.

    81. Re:Patent risks by Darren+Winsper · · Score: 1

      That would be why they couldn't patent physical principle of fuel-air mixture burning. Instead, they had to patent an engine that used it.

    82. Re:Patent risks by Darren+Winsper · · Score: 1

      How the hell are you on your way to a PhD? You're describing a motor, not the law of physics that combusting something causes it to expand, causing pressure against its container. If somebody patented "The combustion of fuel causing the resulting pressure to push against an object, therefore causing motion", it might be analogous to a patent on an algorithm.

    83. Re:Patent risks by dissy · · Score: 1

      PKZIP had a patented compression method. Zlib did the same thing, just using a different method, and created compatible files. MP3 encoders bypassed Fraunhofer patents. Maybe the output wasn't byte-for-byte the same, nor the compression levels equal, but there is a serious hole in the argument for software patents when you can just do the same thing a different way and get around the patent.

      That is the entire point of patents however. They are NEVER to cover an outcome, only a process.

      So of course getting the same result as another patented process is OK, and totally irrelevant.
      Only using the same process to get there makes you run fowl of the patent laws.

      (Yes I realize there are 'end result' patents currently, but they all go against the patent offices charter statements, and the constitutional additions that let that office exist in the first place.)

    84. Re:Patent risks by bunratty · · Score: 1

      Copyright is for software. Patents are for algorithms. We've covered this several times already. Also, if it were not for patents, inventors would have to keep their ideas secret to gain protection.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    85. Re:Patent risks by Draek · · Score: 1

      Then hardware shouldn't be patentable either, problem solved.

      It's not about effort, it's never been about effort. Mathematicians have a job just as hard, or harder even, than most programmers and engineers yet their inventions are not only unpatentable, but uncopyrightable as well merely because we've deemed them to be far too fundamental to our society to be otherwise. If that thinking takes out hardware patents as well, or even all patents in general, then so be it.

      --
      No problem is insoluble in all conceivable circumstances.
    86. Re:Patent risks by Draek · · Score: 1

      Sorry, but software is a tangible machine than runs off another tangible machine called the CPU.

      Wrong. Look up the concept of Turing Machines for starters.

      Software is tangible because it is always stored in a sequence of 1s and 0s on some tangible medium such as a disc.

      Wrong. Software can be represented as an equation (by the Church-Turing thesis) and, therefore, can be stored in the same way that any other equation: in paper, in your mind, whatever.

      Math does not require a CPU or any other technology to be useful whereas without a CPU, all software is useless.

      Again, wrong. Whoever taught you CS should be fired on the spot.

      Therefore, software should be patentable, just as electronics hardware is. After all, today's patentable electronics hardware is developed using VHDL (like Pascal/Ada) or Verilog (C). So why should software be discriminated against?

      Then hardware shouldn't be patentable, not the other way around. Seems you failed not only your CS courses but Logic as well, huh.

      --
      No problem is insoluble in all conceivable circumstances.
    87. Re:Patent risks by Draek · · Score: 1

      I consider myself a computer scientist (and the fact that I have a BS in both math and comp sci and am halfwayish through a CS PhD program would seem to support that assertion), and I firmly believe that a sufficiently clever algorithm is as much an invention as a sufficiently clever physical invention.

      And what makes a sufficiently clever mathematical equation so different from both that it cannot be patented, or even copyrighted?

      Frankly, all the arguments in this whole thread have only convinced me that patents of *all* kinds should be abolished, not just software ones.

      --
      No problem is insoluble in all conceivable circumstances.
    88. Re:Patent risks by Sir_Lewk · · Score: 1

      Those so called instructions are very much mathematical operators. What exactly do you think your point is?

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    89. Re:Patent risks by MeNeXT · · Score: 1

      you answered your own question. One is simulated based on math and the other is a very expensive working / failing product.

      What I have a hard time with is that most patents borrow from the past in order to achieve their monopoly. A good example is one click. It's called an account. You setup an account so next time you prove who you are and we will apply your purchase to your account. The only thing is we threw in the word Internet and now it's a software patent.

      --
      DRM? No thanks, I'll just get it somewhere else...
    90. Re:Patent risks by Sir_Lewk · · Score: 1

      That's a nice idea, except far better mathematicians than you disagree.

      This is absurd, of all the ways to argue for software patents, you guys choose "software isn't math"? Something that is considered to be a mathematical truth? That is just setting yourself up to look like an inbred illiterate, on the same level as flatearthers or Kansas schoolboard members.

      Actually, you look worse. This isn't just a practical science like geology or biology you are sticking your fingers in your ears and chanting "NaNaNaNaNa" too. This is fucking math. How do you even begin to deny this?

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    91. Re:Patent risks by Sir_Lewk · · Score: 1

      I can't possibly see a way to reduce my argument any further. If you honestly see nothing wrong with basic mathematical formulas being patented, then you are beyond hope.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    92. Re:Patent risks by poetmatt · · Score: 1

      software runs off math. So no, software should not be patentable. It's not a sequence of 1's and 0s, it's binary math.

      All your cpu is doing, is performing math really fast.

    93. Re:Patent risks by Lars+T. · · Score: 0, Troll

      Actually, the USPTO no longer lets you patent perpetual motion machines.

      You are out of date on this subject, I'd take the time to catch up if I were you...

      So the USPTO was wrong about perpetual motion, but not about Math - which would have proven perpetual motion wrong. Gee, I wonder if that was my point.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    94. Re:Patent risks by Sir_Lewk · · Score: 1

      Actually, it is thermodynamics that proves perpetual motion wrong, not math. Math is used in that proving process, but without the laws of thermodynamics, using purely math, there is nothing intrinsically wrong with perpetual motion. Math is abstract, and assuming certain physical laws, I can use it to say anything about the physical world that I want. It is the physical laws that are important here.

      Gee, I wonder if that was my point.

      Re-reading your original post, I'm fairly certain it was not.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    95. Re:Patent risks by Anonymous Coward · · Score: 0

      The FOSS community wastes time explicitly avoiding accidentally touching the many bogus patents by some obvious solution to a routine problems - and so does everyone else.

    96. Re:Patent risks by pem · · Score: 1
      I don't necessarily disagree, but, you can't stop at hardware. Airfoil design, drug design, bridge design, basically anything. We are getting to the point where what people call "math" in this argument can be used to simulate anything and give you almost whatever confidence level you want that it is going to work.

      Anyway, my argument about "effort" wasn't amount. A restaurant busboy or dishwasher, or someone who mows lawns for a living expends considerably more effort than I do. My argument was basically about the KIND of effort.

    97. Re:Patent risks by etrusco · · Score: 1

      The intention of patents is to not spur competition, it's to encourage innovation by justifying/giving ROI to research. The examples you cite are demerits of the patent system: divergent formats were created, duplicating efforts and worsening user experience, not for technical reasons, but to avoid the patent costs and pitfalls.

    98. Re:Patent risks by harlows_monkeys · · Score: 1

      This is fucking math. How do you even begin to deny this?

      Have you ever actually done either math or software? I suspect not.

    99. Re:Patent risks by EvanED · · Score: 1

      So were several physical inventions. The airplane might have been one of them. (And yes, the Wright brothers did get a patent on several aspects of their plane, and were apparently actually pretty fiercely litigious about it, with some success.)

      So while you're right that RSA I guess shouldn't have been patentable, the reason was just prior art which isn't particularly germane to this discussion. I would still say that the first guy to come up with it should have been able to patent it, had it not been bound up by a bunch of secrecy.

    100. Re:Patent risks by Nikker · · Score: 1

      You seem to think that if you spend $X on a task or project you somehow deserve $X+n in return. If you had any idea how much companies spend each year in R&D versus how much of that R&D actually produces actual results you would realize your opinion is reseted firmly in fantasy. In reality companies *DO* lose money but how you may ask since they have put so much effort into their task? How can the public not just give them their money back that put into working on their dreams? Because it does not work like that. At the end of the day encryption algorithms as you mention take someone else's data and encrypt / obfuscate it until the appropriate algorithm is applied to return the cipher text to its original state. Now if I used a different encryption algorithm then am I circumventing someone else's algorithm? No one is suggesting H246 should be forced to be released under an open source license or any other than specified by the author. Should I be able to patent a method, by which a source of binary sequence is processed by electronic means in a manner that the original binary sequence is indistinguishable from its original state, then a method by which a binary sequence is then processed to represent its original state? At that point you have just cornered the entire encryption concept. Is that what you feel is what you should be granted? If so your friends R,S & A would be unhappy with you as they were not the first to create encryption but they did facilitate a very good method of encryption.

      Please don't misinterpret my response to say your contribution should go unnoticed and others should be able to be able to copy your work as their own because that is furthest from the truth. What I am saying is if you were to research and develop a method that even exceeded RSA's implementation then should you not be able to recoup your costs as well? In the end patents are just there to incite innovation, not to stop someone from trying to innovate because someone else already did something similar. If that was the case then the first raw video format would have stopped H264 or any other codec for that reason from even being pursued just because the originator patented his/her/their implementation.

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    101. Re:Patent risks by EvanED · · Score: 1

      You seem to think that if you spend $X on a task or project you somehow deserve $X+n in return.

      I don't necessarily think quite that. I would say that you deserve a chance to get that much in return without someone else being able to come in and undercut your R&D costs. If your R&D didn't produce something that is worth $X+n, then of course you shouldn't get it back. The catch is that by "is worth $X+n," what I mean precisely is something like "people would be willing to pay $X+n for your gadget if you were the sole source."

      Now if I used a different encryption algorithm then am I circumventing someone else's algorithm?

      No, of course not. (With a possible exception if, 4000 years ago or whatever, some guy invented the entire concept of encryption; depending on circumstances, I might say that should be patentable.)

      No one is suggesting H246 should be forced to be released under an open source license or any other than specified by the author.

      If by "H264" you mean "the code to a particular implementation of H264", then yes, you're correct. But I think protecting just a particular implementation of H264 doesn't go far enough, for reasons I've already said (since I think it's reasonable that a cleanroom implementation of the same algorithm shouldn't be allowed for the same reason I think a cleanroom implementation of an engine shouldn't be allowed).

      If by "H264" you mean the general algorithm, then yes, that's exactly what lots of people here are saying. (More precisely, they are saying that the original author should have no say in what happens to the algorithm at all, because there should be no protection for an algorithm.)

      What I am saying is if you were to research and develop a method that even exceeded RSA's implementation then should you not be able to recoup your costs as well?

      Yes, you should. And the patent you'd get on your algorithm would let you do that. :-) What you shouldn't be able to do IMO is to basically ride on the coattails of RSA and use what they developed. You can license RSA's patent or wait for it to expire.

    102. Re:Patent risks by EvanED · · Score: 1

      You're describing a motor, not the law of physics that combusting something causes it to expand, causing pressure against its container.

      This is what I would say:

      The motor is a way to harness several laws of physics in order to create rotational motion. Those laws include things like "burning stuff expands" and "if I push on a pole from one end, that transfers the force to the other end" and "if I apply a force in one direction but the object is constrained from moving in exactly that direction, it will move in as close to that direction as it can" (which in the case of the engine is around in a circle).

      An algorithm is a way to harness several laws of math in order to perform whatever task. For example, for RSA those laws includes things (I'm pulling from Wikipedia here; my number theory is pretty weak) like "modular arithmetic behaves a lot like standard arithmetic", Euler's theorem, and the Chinese Remainder Theorem.

      And actually, this just now occurs to me:

      If somebody patented "The combustion of fuel causing the resulting pressure to push against an object, therefore causing motion", it might be analogous to a patent on an algorithm.

      See, that's actually very close as to what I envision the patent on an engine being, except that I'd flesh out the description a bit more. In another post I said that the following should be patentable: "a motor that operates by drawing fuel into a combustion chamber through a valve, closing that valve, compressing the fuel and air, igniting it, opening a valve, and exhausting the burned products through that valve, during four successive strokes."

      It never even occurred to me until now that perhaps the people who support standard patents but are against software patents would see a valid patent on an engine in a different manner. Is this true?

    103. Re:Patent risks by EvanED · · Score: 1

      It never even occurred to me until now that perhaps the people who support standard patents but are against software patents would see a valid patent on an engine in a different manner. Is this true?

      I think I might be able to express this thought a bit better now.

      What would a patent on the internal combustion engine cover? I see it as covering the operation of the engine -- basically, how it works. And this is perhaps why I don't see a difference between patenting an engine and patenting RSA.

      You seem to see it covering the engine itself. But I don't know what that could mean, except for the exact physical form of the engine. And it's my understanding that patents cover more than that (i.e. if you make an engine that's a fair bit different but still operates with the same basic principle, that'd be covered), and I definitely feel that they should cover more than that.

    104. Re:Patent risks by Anonymous Coward · · Score: 0

      Actually, within limits (eg: no guns), you can produce a good that is patented. You cannot import, sell, offer for sale, lease, give away, distribute or do much of anything else with it, but you can create and use a patented device on your own.

      However, patent law hinges on the fact that this is most likely not a feasible or very economic solution, so it is easier for people to buy the good from a manufacturer that has (presumably) licensed the patent. However, if a company has not licensed a patent for a good they produce, and you buy one of their goods before they are taken to court, only they are responsible, the customer/consumer is not, because they bought it based on the assumption that the manufacturer had licensed it, which is a useful and understandable assumption to make.

      Patent law is complicated and nuanced and is probably above the average Slashdotter's head, which is why lawyers exist. Unfortunately there are a few lawyers out there, and a few companies, that make a bad name for the rest of them (insert many lawyer jokes here).

    105. Re:Patent risks by Reality+Master+101 · · Score: 1

      This is absurd, of all the ways to argue for software patents, you guys choose "software isn't math"? Something that is considered to be a mathematical truth? That is just setting yourself up to look like an inbred illiterate, on the same level as flatearthers or Kansas schoolboard members.

      Sheesh. I'm sorry, but you have no idea what math is, or what software is.

      Math is an abstraction, it doesn't exist in any real sense. It is simply a statement of truth, like 1 + 1 = 2.

      Software is a MACHINE. It's an organized system of steps, just like any other machine. Instead of levers and gears, you have ifs and formulas. Instead of a motor turning the machine, you have a program counter. Instead of blue prints, you have a source listing. The whole point of software is AUTOMATION. Just like mechanical machines. It performs a task over a period of time.

      Mathematics does not do anything, it simply IS. It's completely abstract. You can't "execute" a mathematical formula.

      Man, I haven't seen someone so arrogantly and pompously wrong on Slashdot in quite some time.

      --
      Sometimes it's best to just let stupid people be stupid.
    106. Re:Patent risks by Sir_Lewk · · Score: 1

      It is amazing how completely wrong you are.

      I'm not sure why I'm bothering though. Like flat-earthers, you will never be convinced no matter how many citations I give, or no matter how many scientists and mathematicians explain that you are wrong.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    107. Re:Patent risks by Reality+Master+101 · · Score: 1

      I'm not sure why I'm bothering though. Like flat-earthers, you will never be convinced no matter how many citations I give, or no matter how many scientists and mathematicians explain that you are wrong.

      On the contrary, it's even more amazing how completely wrong YOU are.

      Sheesh! Learn the difference between mathematical analysis of process, and mathematical abstraction. ALL MECHANICAL PROCESSES, INCLUDING SOFTWARE, ARE SUBJECT TO MATHEMATICS. That doesn't mean that they ARE mathematics. Mathematics is a tool of ANALYSIS.

      Good God, what do you think mathematics is USED FOR? Do you really think that because I can apply a formula to levers, that means that levers are a mathematical abstraction?

      Basically, you are telling me that because software can be analyzed by mathematics, therefore, is IS mathematics. Sorry, but you are Just Plain Wrong. You don't understand what mathematics is.

      --
      Sometimes it's best to just let stupid people be stupid.
    108. Re:Patent risks by Sir_Lewk · · Score: 1

      Holy fuck, way to link completely irrelevant articles! My link explains how all effectively computable systems are computable on a turing machine, and how anything on a turing machine is an effectively computable system. ie, all algorithms are math. Absolutely no distinction.

      Your link... explains an elementary concept in physics. Amazing. I feel you arn't even trying anymore.

      Physics uses math. Algorithms are math, just as much as polynomials are math. You can attempt to preform as much hand-wavery as you want, trying to obscure the facts. It won't change the fact that real mathematicians say that algorithms are math, and have the math to back it up. Of course this is completely above your head and you have absolutely no idea what point I'm trying to make because you are still stuck in a junior-high mathematical mindset. This is like arguing rocket scientist with a child who's only qualifications is watching a roadrunner blow himself up with firecrackers every Saturday morning. I hope you at least enjoy wallowing in your own ignorance.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    109. Re:Patent risks by Reality+Master+101 · · Score: 1

      The fundamental problem here is that you don't understand what mathematics actually is. And you don't understand what machines actually are. And you don't understand the relationship between the two. You throw out all these concepts as though you're spouting some fundamental truth that no one else understands, yet you completely miss the intrinsic truths of your own points, much less my points.

      Well, congratulations. You've defeated me. I bow to the impenetrable granite of your skull.

      --
      Sometimes it's best to just let stupid people be stupid.
    110. Re:Patent risks by Nikker · · Score: 1

      What good are operators if you are not instructed how to use them?

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    111. Re:Patent risks by gnupun · · Score: 1

      Sorry, but software is a tangible machine than runs off another tangible machine called the CPU.

      Wrong. Look up the concept of Turing Machines for starters.

      But can your precious Turing machine allow you to edit and print a simple word document? No, because it is abstract. You need a real CPU machine and another real software machine for word processing. According to your magical theory of Turing Machines, if I were to take a real hardware machine invention, and represent it with software, instead of plastic and metal, it would magically transform into mathematics. The software you use everyday is not pure math, rather the application of math, and application of math to build technology is engineering. Since software is also technology, but pure math is not, software should be patentable. Let's face it, your regular C statement: "x = y + n;" won't be printed in any textbook because it is an application of math rather than math itself. The distinction is subtle, though obvious.

      Therefore, software should be patentable, just as electronics hardware is. After all, today's patentable electronics hardware is developed using VHDL (like Pascal/Ada) or Verilog (C). So why should software be discriminated against?

      Then hardware shouldn't be patentable, not the other way around. Seems you failed not only your CS courses but Logic as well, huh.

      Your weak, asinine insults bounce off like pebbles. It seems you, like many clueless people, are stuck in the mindset of the horse-cart era -- if I can't see it, touch it, it's not tangible. Wrong, it's time to upgrade your thinking. If some technology yields tangible results, then it is not abstract, it is very, very real. Abstract mathematical equations don't yield tangible results (plugging numbers into equations doesn't count, since that too is a machine, of sorts).

      Name any machine or invention out there. Well, the function and operation of each and every one of those can in turn be converted into a set of equations. So, according to your retarded logic, something should be patentable only based on how to convert those equations into the final product. If the equation can be converted into a piece of wood, plastic or metal, then it should be patentable. If the equation can be converted into a bunch of logical gates and registers, it should be patentable. Ooh, but if the equation is converted into sequence of 1 and 0 bits on a hard disk/CD somewhere, then it is not patentable. How utterly stupid and backward minded is that?

      The process and technologies to convert ideas into usable products is getting easier and easier by the decade. Very soon, we'll be able to build massive ships, organs and other machines with a set of instructions -- sofware. But the intellectual effort to generate those ideas is getting harder and harder (as all the easy ideas have already been done). Software, like all technologies, should be patentable, because

      • It yields valuable, tangible results
      • Requires massive, unique, intellectual effort -- more so than older technologies in many cases
      • Is a piece of technology, not math or science
    112. Re:Patent risks by gnupun · · Score: 1

      software runs off math. So no, software should not be patentable. It's not a sequence of 1's and 0s, it's binary math.

      Software, like engineering, is applied math. Therefore it should be patentable, just like all engineering inventions. Real (theoretical) math is published in textbooks or papers.

    113. Re:Patent risks by Lars+T. · · Score: 0, Flamebait

      Gee, I wonder if that was my point.

      Re-reading your original post, I'm fairly certain it was not.

      Just shows that you are an idiot and your opinions don't matter. Tough luck.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    114. Re:Patent risks by Sir_Lewk · · Score: 1

      Cute. Too bad you've already demonstrated pretty well you haven't actually read up on this subject in the past decade.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    115. Re:Patent risks by Sir_Lewk · · Score: 1

      You can build up operators from more primitive operators in software. These operators can be build up from the even more primitive operators NAND/NOR, which can be built in hardware. So what? You seem to be under the delusion that "being comprised of instructions" precludes something from being mathematics. Nothing could be farther from the case.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    116. Re:Patent risks by Lars+T. · · Score: 1

      Too bad you don't get sarcasm - but then you don't get a lot of things.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    117. Re:Patent risks by Sir_Lewk · · Score: 1

      I take it you are implying that your posed question "Gee, I wonder if that was my point." is sarcastic, implying that you in fact do not wonder if that was your point. This indicates that you are attempting to assert that was in fact your point, to which I responded that I doubt it was. Rather I think you are trying to revise your previous statements without admitting that you were ever wrong. Or perhaps you are referring to your sarcastic remark: "Math isn't real science like building perpetual motion machines" to which I responded with "Furthermore, Mathematics is not universally considered a science." indicating that to say that math is a science is not as true as you may think it is.

      Whichever the case, your ignorance of US patent law remains quite obvious for all to see. What's sad is you can't even be bothered to form a decent ad hominem argument.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    118. Re:Patent risks by nog_lorp · · Score: 1

      Any machine has a physical, mass-taking representation. A program is fundamentally abstract in nature.

      Just like you cannot patent a book, you copyright it.

      Or you could copyright a file that held the physical descriptions of a machine.

    119. Re:Patent risks by b4dc0d3r · · Score: 1

      The context of my reply was rebutting the idea that repeating "software is math" is not the best argument. The quote given to support that applied equally to software and hardware, and I attempted to draw a distinction between the two.

      I could not possibly care any less about the core "patent" idea worldwide, but this is what I base my argument on, it is biased towards a particular country. "Promote progress" does not necessarily mean competition, but it also does not necessarily mean ROI. You seem to have focused on a single sentence: "So GIF encouraged invention, the "legitimate purpose" of patents."

      Patents which affect me are based on Clause 8 of the US Constitution, to promote progress. Whether it accomplishes this the intended way (documenting progress and protecting its use for a limited time) or through the law of unintended consequences is a principled distinction, not a practical one. In the example of GIF, the result was wide adoption of PNG. In the example of PKZIP the result was a less efficient and IIRC more CPU-intensive compression step, so nothing was gained and it's a counter-example to PNG.

      Clause 8. The Congress shall have Power ... To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.

    120. Re:Patent risks by b4dc0d3r · · Score: 1

      A patent is an intellectual property right granted by the Government of the United States of America to an inventor “to exclude others from making, using, offering for sale, or selling the invention throughout the United States or importing the invention into the United States” for a limited time in exchange for public disclosure of the invention when the patent is granted.

      http://www.uspto.gov/patents/index.jsp

      If you're going to refute something that is over your own head, a citation of some sort helps. "Making" is the first word in the list of forbidden things. That's the patent office website. Go find the actual law and see if it supports your comment.

      http://www.uspto.gov/web/offices/pac/mpep/consolidated_laws.pdf

      35 U.S.C. 154Contents and term of patent; provisional
      rights.

      (d)PROVISIONAL RIGHTS.—
      (1)IN GENERAL.— In addition to other rights provided by this section, a patent shall include the right to obtain a reasonable royalty from any person who, during the period beginning on the date of publication of the application for such patent under section 122(b), or in the case of an international application filed under the treaty defined in section 351(a)designating the United States under Article 21(2)(a) of such treaty, the date of publication of the application, and ending on the date the patent is issued—
      (A)(i) makes, uses, offers for sale, or sells in the United States the invention as claimed in the published patent application or imports such an invention into the United States;

      35 U.S.C. 163Grant.
      In the case of a plant patent, the grant shall include the right to exclude others from asexually reproducing the plant, and from using, offering for sale, or selling the plant so reproduced, or any of its parts, throughout the United States, or from importing the plant so reproduced, or any parts thereof, into the United States.

    121. Re:Patent risks by Elektroschock · · Score: 1

      When it is patent encumbered it is no open standard.

  3. First Post? by gbutler69 · · Score: 2

    I'm starting to think that all the Hoopla over Patents, Copyright, and Trademarks is misplaced. Maybe we should all just work within the system?

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:First Post? by selven · · Score: 1

      What is that even supposed to mean? We are working within the system. Working outside the system is what you do when you just go and download everything you want instead of trying to obtain a legal copy. That approach works fine for most people, but not for the corporations who are producing the software (including the open source stuff) we use - they can't get away with it as easily.

    2. Re:First Post? by Anonymous Coward · · Score: 0

      At the same time, "the system" is not globally uniform. The corporate cocksucking laws in the USA mean that H.264 is patent covered. But that is not so or not enforceably so in large areas of the world. I can play H.264 files license-free and fully legally, but I'm not in the USA. Now, the USA/corporations, with ACTA and TRIPS before it, does try to foist its ever more absurd anti-free-market patent monopoly grants on the rest of us, but we're less and less inclined to respect them given the USA's dwindling power and credibility...

    3. Re:First Post? by sortius_nod · · Score: 1

      The system that the US government ignored until it suited them?

    4. Re:First Post? by Auckerman · · Score: 0

      Save for the title being "first post" you really don't deserve a flamebait rating. Post like this is why flamebait is moved to +5 to my account.

      That being said, you're wrong. GPL software is inherently incompatible with software patents. If you're a big company with a big patent portfolio, you can pretty much make any software you want. Someone sues you, you counter sue, because odds are they are breaking at least one of your patents. In general, companies try to avoid suing each other and instead opt to just cross license each others patents, by formal agreement or by understood silence.

      GPL software developers have no such luxury. They aren't known for patenting things and if they do, they then promptly license the patent in a such a way that GPL compatible licenses can use the patent. Which means, BSD licenses can use the patents too. Which means, it can be incorporated into proprietary software without releasing the code. Which, of course, defeats the whole purpose of a patent.

      If firefox includes H 264 decoding in their own software libraries, they are no exposed to a lawsuit. If they opt to use OS native plugins for H 264, they end up creating a logistical nightmare in development, since you can't guarantee that all installs will have the software needed to the embedded movies. Which means the user is going to blame them when it doesn't work.

      The real solution is to work with the standards committees to make the video tag in HTML have real meaning. What movie containers and formats are officially supported by HTML 5? How will the patents work, etc etc. This whole Theora thing is the wrong tactic. They will stand alone and fail. They should call up Apple and Google and ask them to work with them on solving this problem permanently. If they can get the MPEG patent holders to all license their software in such a way that its compatible with the GPL, then the problem is solved.

      --

      Burn Hollywood Burn
    5. Re:First Post? by bcmm · · Score: 1

      I would post a lengthy and reasoned response here, but it's just gonna boil down to the following:

      No, because the existing IP system is fucked and everybody knows it.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
    6. Re:First Post? by gbutler69 · · Score: 1

      I think you may have missed my tongue in my cheek!

      --
      Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  4. Theora vs. H.264 by Anonymous Coward · · Score: 0, Troll

    I think it was decided that in the end the patent liability for both was near equal. So given that H.264 is the superior tech it makes sense to pick that over Theora.

    1. Re:Theora vs. H.264 by peragrin · · Score: 1

      how the they both be equal when MPEG-LA has already announced that they will seek all users, (end users, software distributors, and hardware people ) will each required to buy a license to view H.264 The current free period ends in 2016.

      That sounds like a patent threat all buy itself.

      that is how I took their announcement that they were extending their free licensing.

      --
      i thought once I was found, but it was only a dream.
    2. Re:Theora vs. H.264 by carlhaagen · · Score: 2, Insightful

      MPEG-LA never said they would go after END USERS. They CAN'T go after end users - there is no practical possibility in this. Really, wake up to reality. License fees connected to MPEG-4 technology, all of its levels, are always entirely free for END USERS who are just consuming video or audio built on said tech. Nothing else has ever been said, nothing else will ever be possible. Don't confuse end user's consuming commercial material of MPEG-4 format as being subject to licenses - the ones SELLING said material are the ones subject to the license.

    3. Re:Theora vs. H.264 by mrsteveman1 · · Score: 2, Funny

      It's all very well standing around hinting what a huge penis you have, but sooner or later you're going to have to pull down your pants.

      We are talking about internet video here, what did you expect it would be used for?

    4. Re:Theora vs. H.264 by peragrin · · Score: 0

      Yes they can. If you encode a movie and redistribute said movie you have to pay a fee for it. that includes every home user. you have a digital camera you upload that content onto the net you have redistributed their codec and are required to pay a licensing fee.

      ALL redistribution of ANY H.264 encoded video on through ANY method requires one to Pay FEES. You host HTML5 video encoded H.264 video on your own website. you had better be ready to fork over money to MPEG-la when they start sending out bills. the MPEG group is getting ready to sue everyone who hasn't bought their licensing.

      --
      i thought once I was found, but it was only a dream.
    5. Re:Theora vs. H.264 by Endymion · · Score: 1

      You host HTML5 video encoded H.264 video on your own website.

      That makes you a Content Provider in the eyes of MPEG-la and most of the "intellectual property" industry, not an End User, who is a passive consumer by definition.

      --
      Ce n'est pas une signature automatique.
    6. Re:Theora vs. H.264 by WrongSizeGlass · · Score: 1

      It's all very well standing around hinting what a huge penis you have, but sooner or later you're going to have to pull down your pants.

      Can you please use that in a car analogy?

    7. Re:Theora vs. H.264 by AK+Marc · · Score: 1

      Defining every user of Facebook and MySpace as a non-End User will result in some issues. With Web 2.0, everyone is a producer and consumer at the same time.

    8. Re:Theora vs. H.264 by WrongSizeGlass · · Score: 1

      how the they both be equal when MPEG-LA has already announced that they will seek all users, (end users, software distributors, and hardware people ) will each required to buy a license to view H.264

      2016? 2016? By then there will be at least one - if not more - different video format that we'll be arguing about. Things are moving fast on the intertubes (except for the W3C) so I'm not worried about 2016. Technology will surpass itself given enough motive or profitability.

    9. Re:Theora vs. H.264 by Toonol · · Score: 1

      MP3 was invented in 1991. I imagine it will be the default standard for at least another decade. Such things tend to be in flux for short periods, then become entrenched for long periods, and I think we're in the period of settling for video. Actually, I think it probably already has.

    10. Re:Theora vs. H.264 by Endymion · · Score: 1

      They won't define every user of Facebook as a non-End User, as the average person is not hosting video content. The average person is getting Facebook (or youtube, or whomever) to host it for them, by contract.

      With web 2.0, even fewer people actually pay for their own hosting, and instead use these Walled Garden services to do it for them.

      --
      Ce n'est pas une signature automatique.
    11. Re:Theora vs. H.264 by russotto · · Score: 1

      Yes they can. If you encode a movie and redistribute said movie you have to pay a fee for it. that includes every home user. you have a digital camera you upload that content onto the net you have redistributed their codec and are required to pay a licensing fee.

      Fuck that shit. If I encode a movie with a (licensed) encoder, said movie is not "the codec". It is the result of applying the codec to a video stream. It's no more patented by them than a piece of wood drilled through by a patented drill bit is patented by the drill bit owner. They can claim otherwise all they want, but their claim won't survive the first time they try to enforce it against a big player... and trying to enforce it against small fry won't pay the bills.

    12. Re:Theora vs. H.264 by dgatwood · · Score: 1

      It's all well and good standing around hinting at what a huge compression ratio you have, but sooner or later, you're going to have to open up the throttle.

      Happy?

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    13. Re:Theora vs. H.264 by dgatwood · · Score: 1

      MP3's licensing is also not too draconian, and thus, there was no reason to innovate around it.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    14. Re:Theora vs. H.264 by Homburg · · Score: 1

      If I encode a movie with a (licensed) encoder

      Well, in your parentheses there lies the whole thing. It's the MPEG-LA who specify the license for the encoder, and they won't license an encoder to be used to produce material for distribution. I'm not sure whether that kind of restriction on use will fly, but it doesn't seem totally implausible, and it doesn't quite depend on them claiming some kind of patent rights over the data stream itself.

    15. Re:Theora vs. H.264 by timmarhy · · Score: 1
      no they don't you tard.

      they only require fee's in the event your audence is greater then 100,000 people, and even then it's only $2,500pa. i'd suggest if you are distributing a video to over 100,000 people your making money out of it and your a moron if it's making you less then $2,500pa.

      --
      If you mod me down, I will become more powerful than you can imagine....
    16. Re:Theora vs. H.264 by Anonymous Coward · · Score: 0

      MP3 needed no successor because it was a very good algorithm at the time, but as time progressed higher bitrate audio wasn't needed. No matter what the audiophiles say to you, 320kbps is enough for everyone else. MP3 does a great job at that level of compression. No need to make a new compression algorithm and break all the MP3 players out there.
      Video, on the other hand, has been constantly increasing in quality, and may continue increasing. It all depends on if you think that 1080p is the end of the road for a long time.

    17. Re:Theora vs. H.264 by raynet · · Score: 1

      Humm, does the patent really apply if you just distribute a H.264 encoded video but not decode it in any way?

      --
      - Raynet --> .
    18. Re:Theora vs. H.264 by ducomputergeek · · Score: 1

      It's anyone shipping an encoder/decoder, not content in H.264. If you use iMovie, Apple's already paid for the H.264 encoder in Quicktime. If you shot the video with a camera that has an H.264 encoder chip, you're covered when that chip manufacture paid the license to produce H.264 on a chip.

      The only case where this becomes a problem is if you are using a program like ffmpeg which has not paid for a license and then wish to ship out content in H.264. Same if you are using ffmpeg on the backend of a server to convert video for streaming without paying for a license. For the vast majority of users not on Linux, this is not going to be a problem. Any tool they are likely to be using will be using a H.264 licensed encoder/decoder.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    19. Re:Theora vs. H.264 by russotto · · Score: 1

      Well, in your parentheses there lies the whole thing. It's the MPEG-LA who specify the license for the encoder, and they won't license an encoder to be used to produce material for distribution. I'm not sure whether that kind of restriction on use will fly, but it doesn't seem totally implausible, and it doesn't quite depend on them claiming some kind of patent rights over the data stream itself.

      It does, though. Suppose I encode a movie and pass the encoded data stream on to someone else for distribution. What standing does MPEG-LA have to sue this other person, if they have no rights in the data stream itself?

      IIRC, the MPEG patents DO in fact include claims to distributing the data streams. But like I said, I don't think those claims will hold up against a well-lawyered opponent.

    20. Re:Theora vs. H.264 by tepples · · Score: 1

      i'd suggest if you are distributing a video to over 100,000 people your making money out of it

      Not everyone who has uploaded a video to YouTube and got 100,000 views is making money from the video.

  5. Before someone posts only the xiph link by discord5 · · Score: 5, Interesting

    So before someone starts the whole "which codec is better" flamewar again: someone at xiph thinks theora is better, ars thinks h264 is better, and this guy has a do it yourself kit in the form of a shell script.

    Have fun arguing, as the past few articles have been quite fruitful in that area. Sadly few have realized (despite it being the main focus of most of those articles, but hey, who reads those) that quality will not be the merit to win this battle.

    1. Re:Before someone posts only the xiph link by calmofthestorm · · Score: 2, Funny

      I personally like the mbmp format I just patented. It's similar to mjpeg except using bitmaps instead of jpegs to improve video quality.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    2. Re:Before someone posts only the xiph link by LiENUS · · Score: 1

      It's a shame you use mbmp, I just patented mpng which has a much better compression ratio but still better quality. But the license is only free to people who aren't licensed to use mbmp

    3. Re:Before someone posts only the xiph link by lyml · · Score: 1

      The guy at xiph is retarded, sure in the "random" frame he is showing it's hard to tell a difference but watch the two actual videos side by side at the same time. The superiority of h264 is obvious.

      In particular when there is white text overlay on the film, the compression artifacts of theora becomes very visible.

      Look at (for example) 21s and 26s into the movie and then try to say with a straight face that theora is better.

    4. Re:Before someone posts only the xiph link by TheRaven64 · · Score: 3, Interesting

      That Xiph.org thing keeps being posted. I personally detest it because it compares H.264 and H.263 in the same page, so people who skim the article look at the smaller images and say 'look how much better Theora is!' And they're right, Theora is better than H.263. It's not especially clear which is better in the cherry-picked frame but, as you say, it is obvious which is better when you watch the videos. It's even more noticeable when you grab the lossless DIRAC version of the source movie how much both of them lose.

      --
      I am TheRaven on Soylent News
    5. Re:Before someone posts only the xiph link by hairyfeet · · Score: 1

      There really isn't any argument dude, as pretty much anybody with eyes can tell that Theora is about equal to H.263 but H.264 kicks its ass. That is why the FSF put out that open letter to Google to free VP8 which does kick ass compared to H.264, at least IMHO. Of course I personally think they are wasting their time, as Google keeps the best stuff for themselves (like their in house file system) and I don't see them giving up the ON2 tech.

      Of course the elephant in the room is hardware acceleration. Every box I build, even the cheapest duals, comes with H.26x, WMV 7-9, and MPG 2 as well as Xvid/DivX accelerated out of the box and believe me it does make a BIG difference to user experience. Video is smoother, the machine is more responsive, and even with the lowest Radeon onboards it is just better for the user. And that doesn't count all the mobile devices coming out from PMPs to cell phones with built in H.264 and ZERO support for Theora. Does Theora even have hardware acceleration yet on any platform at all?

      As someone who deal with end users all day I can say that patents don't mean squat to Joe Public, all he cares about is does it work, is it easy, and is it convenient, and just as MP3 won against FLAC and Vorbis so too do I predict that H.264 will win this battle, if the battle isn't already won which I personally believe it is. Sorry FOSS guys, but you really should have jumped on hardware acceleration and been in talks with manufacturers.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    6. Re:Before someone posts only the xiph link by cheesybagel · · Score: 1

      You have not seen enough videos I guess. Theora is clearly superior to H.263. However it is worse in quality/bitrate than H.264. Vorbis is better than MP3 and comparable to AAC.

    7. Re:Before someone posts only the xiph link by Anonymous Coward · · Score: 0

      VP8 which does kick ass compared to H.264, at least IMHO

      And where do you get your Humble Opinion about VP8 from? How did you get to test a codec nobody else has ever even seen?

    8. Re:Before someone posts only the xiph link by jht · · Score: 1

      Bingo - and this is also a huge reason why the cellphone-using masses flock to iPhones and not to all the more "open" devices out there in the market.

      Users don't care if the garden is walled or not. They don't care if their video is served with an ideologically pure codec, either.

      All users want is a phone that works well with plenty of conveient apps and a polished user experience. And they want their video to play in their browser of choice, and they want it to not make their computer's fans whine like crazy or suck down the battery meter on their handheld device. The combination of hardware acceleration support for H.264 on virtually every platform and H.264 support built into the Webkit browser family along with support going into IE9 is the finisher. Pure though Theora may be, this has become a Beta/VHS war and if Firefox doesn't add H.264 support it'll ultimately cost them market share.

      The war is over. Firefox needs to have H.264 support if they want to remain relevant. If content providers decide they like Theora better, then you'll see the other browser makers add support for it but that's pretty unlikely.

      --
      -- Josh Turiel
      "2. Do not eat iPod Shuffle."
    9. Re:Before someone posts only the xiph link by cyberthanasis12 · · Score: 1

      Sadly few have realized (despite it being the main focus of most of those articles, but hey, who reads those) that quality will not be the merit to win this battle.

      You can say that again. Otherwise Windows would be in the dustbin for years.

    10. Re:Before someone posts only the xiph link by Anonymous Coward · · Score: 0

      I’m one of those guys that encodes the videos you might download on eztv.it or piratebay. And I’m sorry, but I tried Theora and really wanted to give it a chance. It just doesn’t cut it. It’s either bigger, or looks just bad in comparison. It can beat XviD. But only losers still use that. The files become just too big. Especially with HD.

      But OK, we don’t give a shit about any patents anyway. I give you that. :)

    11. Re:Before someone posts only the xiph link by dgatwood · · Score: 1

      ...and this guy has a do it yourself kit in the form of a shell script.

      Aw, man! And I was hoping he had written a codec as a shell script! That would be freaking awesome. (Of course, he'd also probably have to write a shell that precompiles shell scripts into native code, but....)

      Ooh. I know what I'm going to do today. :-D

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    12. Re:Before someone posts only the xiph link by evilviper · · Score: 1

      So before someone starts the whole "which codec is better" flamewar again: someone at xiph thinks theora is better, ars thinks h264 is better,

      Xiph claims Theora might be able to compete, and everyone else in the world says Theora is horrid, and is light-years behind H.264. End of story.

      Sadly few have realized (despite it being the main focus of most of those articles, but hey, who reads those) that quality will not be the merit to win this battle.

      Quality has been one of the top two central points from the very beginning, right behind patent concerns, and I fully believe the fight would have been much closer if Theora's quality was even close to competitive. Honestly, at this point the fight has been decided, so none of it matters, but quality is as important as any other issue (if not, why not use good old MPEG-2?).

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    13. Re:Before someone posts only the xiph link by TheTurtlesMoves · · Score: 1

      Thats funny. Most of the xiph folks think h264 is better under many of its profiles (search the recent posts on the mailing list). However most also think that at youtube quality the difference (if any) is not worth the license issues.

      And licensing is far more about what you have to sign than pay. Everyone cries bloody murder with the nvidia binary blobs bundled with a linux distribution. Yet the fact is that in some countries having h264 bundled is illegal and redistribution terms from 3rd parties (aka GPL) is a license that MPEG-LA will never ever issue.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    14. Re:Before someone posts only the xiph link by makomk · · Score: 1

      I personally detest it because it compares H.264 and H.263 in the same page, so people who skim the article look at the smaller images and say 'look how much better Theora is!' And they're right, Theora is better than H.263.

      Recall that a H.263 variant is what Youtube was using for video for a long time, and this rebuttal was aimed at them...

    15. Re:Before someone posts only the xiph link by hairyfeet · · Score: 1

      Uhhhh....that is what I said dude. Theora is comparable to H.263 but gets stomped by H.264. As far as Vorbis? Doesn't matter is it makes your music sound like angls farting because a good 95% of the PMPs out there don't support it.

      Personally I think this whole discussion is moot anyway, as H.264 has already won the game, as MP3 did in the audio field. Working as a PC builder and repairman I can honestly tell you that with all the boxes coming across my desks, nearly all of which the customers ask me to back up their tunes, not once have I seen Vorbis in the wild. Not Vorbis nor FLAC nor APE. What I see is a good 75% MP3, 20% WMA, and the rest are Apple AAC. And in videos, at least the sites my customers are using, I see the same thing-75% FLV H.26x, 15-20% MP4, and a smattering of .WMV.

      But I honestly believe lack of hardware acceleration has made Theora a non starter. More and more I see folks surfing on cell phones, netbooks, all these little underpowered devices that without hardware acceleration you would get a slideshow if you are lucky. And nearly every device I see coming out has H.26x hardware acceleration, whereas Theora doesn't even have it for the big three PC GPU manufacturers. Personally I think Theora has done missed the boat and will be a tiny niche like Vorbis and FLAC. Sorry, just calling it as I see it.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    16. Re:Before someone posts only the xiph link by arose · · Score: 1

      Well, sorry to say, but with that phrasing Xiph is closer to the thruth. Current H.264 encoders are better, but let's not forget that we are more or less constrained to Baseline Profile sue to mobile devices. No sane person is claiming order of magnitude differences. Both have room to grow. Few expect H.264 encoders to become orders of magnitudes better.

      Therefore "horrid" and "light-years behind" are fanboy (don't ask me why there are codec fanboys) exaggerations.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    17. Re:Before someone posts only the xiph link by evilviper · · Score: 1

      Well, sorry to say, but with that phrasing Xiph is closer to the thruth.

      Not at all true. Xiph has heavily stack the deck to get the answer they wanted.

      we are more or less constrained to Baseline Profile sue to mobile devices

      Baseline H.264 is much simpler than Theora. Comparing baseline H.264 to full-fledged Theora is utterly unfair.

      No sane person is claiming order of magnitude differences.

      A) Such simplistic terms of comparison will always be inaccurate.
      B) Since when is an order of magnitude difference required? 2X - 4X is realistic, and means a huge difference in file sizes, and required bandwidth.
      C) For high quality, it's MORE THAN AN ORDER OF MAGNITUDE difference. Theora can't do high quality at ANY bitrate, so the bitrate difference is actually INFINITE.

      Therefore "horrid" and "light-years behind" are fanboy (don't ask me why there are codec fanboys) exaggerations.

      The fact that you're calling me a "fanboy" for telling the truth, based on my years of codec development, just demonstrates that YOU are the one who has a problem with the truth.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    18. Re:Before someone posts only the xiph link by arose · · Score: 1

      Baseline H.264 is much simpler than Theora. Comparing baseline H.264 to full-fledged Theora is utterly unfair.

      Not according to the x.264 guys, they say Baseline trounces Theora and Xiph says Theora is less computationally intense then Baseline. If you are going to argue with them then a simple statement is not enough.

      Incidentally it is also the only fair comparison in context of HTML5, because H.264 is always praised for it's embedded support. Guess what, most of the embedded H.264 decoders are Baseline only. If we are to compare Theora to anything, but baseline, then people should shut up about embedded penetration being the holy grail.

      Since when is an order of magnitude difference required?

      Every time someone brings phrases like "horrid" and "light-years behind" into the discussion.

      2X - 4X is realistic, and means a huge difference in file sizes, and required bandwidth.

      2x - 4x hasn't been demonstrated for generally used bitrates, to the best of my knowledge. Feel free to link me up. For high quality, it's MORE THAN AN ORDER OF MAGNITUDE difference. Theora can't do high quality at ANY bitrate, so the bitrate difference is actually INFINITE.

      That's a bold claim, let's start simple. Define "high quality" in quantifiable terms, then we'll see if you can present proof.

      The fact that you're calling me a "fanboy" for telling the truth, based on my years of codec development, just demonstrates that YOU are the one who has a problem with the truth.

      Years of codec development or not, keep your statements this side of the stratosphere. "Light years" might be appropriate between MJPEG and a modern codec, not between a modern codec and a state of the art codec.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  6. these don't seem like strong arguments by YesIAmAScript · · Score: 4, Insightful

    In the first part, he takes Gruber's working (submarine patents) too literally. Gruber didn't mean literally patents that are applied for earlier but not granted yet. Gruber misspoke himself. Instead, he means companies who have patents that are already granted and they later will decide applies to new situation and then sue. If Theora becomes successful, it will meet with plenty of these, just as any other software success does now.

    In the second part, oddly, given that he rails against strawmen, the argument creates a strawman.

    The quoted response veers rapidly from addressing facts (whether Theora is within patent guidelines) to making a prediction 'I predict that MPEG LA may counter that they know groups have been pressured into licensing patents in order to use Theora.' Then it shoots down the prediction and thus claims to counter the argument. But that prediction is just a prediction, it isn't the issue at hand. And countering prediction you made up yourself doesn't necessary counter the actual argument which is that H.264 has a patent defense pool and Theora doesn't.

    --
    http://lkml.org/lkml/2005/8/20/95
    1. Re:these don't seem like strong arguments by TheTurtlesMoves · · Score: 1

      H.264 does not have a patent defense pool. Just a list of known patents that are group licensed from the MPEG-LA. One of the terms of the license is that MPEG-LA makes *no* claims that other patents outside their portfolio may also be need to be licensed and they are in no way liable or responsible for any such "forth party" patent license agreement/court cost etc.

      Guess how many patent claims have been made against h.264? How many against Theora?

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    2. Re:these don't seem like strong arguments by nutshell42 · · Score: 1
      Yeah, but h.264 is in everything. High-end Blu-Ray players, low end Chinese crap DVD-players, cellphones, smartphones, iPods, iPod-clones, clones of iPod-clones, MIDs, picture frames and toasters.

      If a patent troll sues over Theora there will just be an inofficial hack job of html5 to enable other codecs. Code is cheap, browsers are free and everything that renders that web page already supports h.264 anyway. For h.264, take the largest 50 electronics corporations. Every one of those either produces a chip that decodes h.264 in hardware or sells a device that includes such a chip.

      They have a vested interest in h.264 and if something threatens the core of the standard, *cough* The Thousand Corporations of the MPEG LA Descend Upon You. Their Lawyers Will Blot Out the Sun. *cough*

      --
      Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
    3. Re:these don't seem like strong arguments by Anonymous Coward · · Score: 0

      You're completely right.

      Another point is that the MPEG LA has absolutely no incentive to "report" to Theora which patents they are infringing. In fact they have a vested interest in not doing so - by forcing Theora to do the necessary patent research themselves they increase their costs. Theora's strategy of "allowing" patent holders to report issues is naively unrealistic, for this reason. It proves nothing.

      Now, Theora's rhetoric may well be enough to convince a Linux desktop user that the codec doesn't have patent issues, but convincing (say) YouTube that they will never be sued by a 3rd-party for using Theora is a completely different ballgame. MPEG-LA has a far, far better story on this front, and if the worst happens I suspect a judge would look more kindly on a company that has paid royalties in good faith to a licensing organization, versus one that has avoided paying royalties based on weak assurances from a developer.

  7. Who cares? by Jorl17 · · Score: 0, Troll

    I do, and so should you.

    --
    Have you heard about SoylentNews?
  8. Thom is a jackass. by carlhaagen · · Score: 3, Insightful

    There. I said it. Why? Because he counters Gruber's arguments with identical retorts, completely failing to see beyond his own nose, failing to realize and admit that all he is doing is just pulling his end of the rope in this tug of war, instead of coming up with anything worthwhile to consider in the choice of h.264 v theora.

    1. Re:Thom is a jackass. by Anonymous Coward · · Score: 0

      So what else is new ? I stopped going to OSNews when it turned into Thom's blog. There's plenty of interesting blogs out there by people who can actually write and whose opinions are backed by real experience.

  9. It's been said, but it's important by Endymion · · Score: 5, Insightful

    I love Free Software. I really do. I normally piss-off people with my fairly hard-line GNU/RMS attitude towards software. In most cases, I will drop features so I can run the Free version of something, and all of my code is GPL3.

    But in this case, the so-called Free solution is the wrong choice to make. H.264 has won, and it won years ago. Now, an argument can be made that making a stand is important. But in this case, there is a pragmatic and strategic reason not to: taking a moral stand with Theora will damage other things, namely HTML5 and potentially Firefox itself.

    PNG won out in the end over GIF, mostly, because it had better features. But what enabled that win was that they could both be used at the same time. If early Mozilla branches simply removed GIF support, the browser would have been dead in the water. Nobody would use it, because the images people already have were in GIF format. Only because both formats were supported could Mozilla be even considered by most people.

    Today, people have data in H.264 format. A lot of data. A long list of hardware devices are made that support it directly. This data is not going to vanish, and people will want to play it. Firefox can choose to support that, or they can choose to become less relevant over time. Chrome is getting surprisingly strong uptake, and IE (ack) is getting much less offensive as time goes on. (aside: this competition is pretty awesome - browsers were starting to stagnate for a few years, and the rush for new features has been revived)

    Playing people's data and being compatible with most modern and future hardware is the pragmatic reason to support H.264; the strategic reason is that the moral stand is not about video codecs! It's about removing Flash and related proprietary solutions. Playing the SAME video stream (a .mp4 in H.264 format) in flash or the <video> tag is neutral as far as codecs go, but it opens up the idea of a Free player.

    The battle over codes needs to be left for another day.

    As for how to actually implement it, Mozilla et al needs to take a cue from how distros handle MP3 and other patented codecs - foreign "non-free" repositories. The details on how you do that are highly flexible. Mozilla seems to like over-engineering things, so I'm sure they can come up with a Clever Codec Plugin Scheme to automate this, as long as the actual codec is 1) a separate project, and 2) developed outside the org.

    Please - I love firefox, and this video issue is the one issue that could break them in the long-run. People like their YouTube.

    --
    Ce n'est pas une signature automatique.
    1. Re:It's been said, but it's important by timmarhy · · Score: 1
      this is it's a massive fail when people try to mix their morals with their software. what software i use isn't a moral issue, it's a technical one.

      i'm sure the hardcore OSS crowd won't listen as usually, and will happily continue to hang onto their 2% market share, year of the linux desktop this year and all that....

      --
      If you mod me down, I will become more powerful than you can imagine....
    2. Re:It's been said, but it's important by Endymion · · Score: 1

      The thing is, I am one of those moralistic "hardcore OSS crowd" people. And what Mozilla and the Theora-or-nothing crowd are missing is that even staying with Evil H.264, the video-tag/HTML5 is still a huge moral win over Evil Proprietary Flash.

      --
      Ce n'est pas une signature automatique.
    3. Re:It's been said, but it's important by diamondsw · · Score: 1

      How I wish the debate could end with this lengthy and insightful comment. Firefox's stand amounts to sound and fury.

      --
      I don't know what kind of crack I was on, but I suspect it was decaf.
    4. Re:It's been said, but it's important by Qubit · · Score: 1

      even staying with Evil H.264, the video-tag/HTML5 is still a huge moral win over Evil Proprietary Flash.

      I agree that using the video tag would be preferable to using Flash, at least for just an online movie player (ala YouTube), but I largely believe in taking a multi-pronged approach here.

      First, there's a huge quantity of Flash content out there and people developing using Flash. Free Software enthusiasts can't even play that stuff unless they have some kind of tool, and that's why stuff like Gnash and Lightspark must be important parts of our overall roadmap.

      For web video we need to start pushing the video tag in conjunction with free formats. Ogg Theora is one possibility, trying to get Google to open the vp8 codec for YouTube is another. I think that there's still a hope (small, but possible) to get widespread support for Ogg Theora alongside widespread support for H.264.

      And of course there's the software patent front: We need to chug forward and get the courts (or legislature, if necessary) to get rid of software patents once and for all. Getting rid of software patents would make codec support possible for thing such as H.264, mp3, Sorenson Spark, and vp6, and would remove the threat of shakedowns from companies like Microsoft for things like the FAT patents.

      We need to push forward on all of these fronts if we want to make real progress towards our twin goals of free and open formats on the web and the ability for FOSS browsers to implement all relevant technologies without fear of patent litigation.

      --

      coding is life /* the rest is */
    5. Re:It's been said, but it's important by _Sprocket_ · · Score: 1

      Today, people have data in H.264 format. A lot of data.

      Today, there is even more data wrapped up by Flash. I suppose we should just be pragmatic about it all and keep using that. Right?

    6. Re:It's been said, but it's important by WrongSizeGlass · · Score: 1

      But in this case, the so-called Free solution is the wrong choice to make.

      Will the aliens (or Apple personnel) who have kidnapped please return him unharmed.

    7. Re:It's been said, but it's important by mqduck · · Score: 1

      Mozilla support for a GStreamer backend is being written. Doesn't that solve the issue of H.264 support?

      --
      Property is theft.
    8. Re:It's been said, but it's important by Endymion · · Score: 1

      The multi-pronged approach is a very good idea, and you achieve that by separating the issues.

      Promote HTML5 as an alternative to propriety Flash video.
      Promote Gnash (others?) as an alternative to flash itself for games, maybe?
      Promote Theora as an alternative to H.264.
      Promote general software patent reform, etc, by just using all of the above and accepting the consequences as Civil Disobedience.

      By binding them together, a failure in one area also means a failure in the others.

      --
      Ce n'est pas une signature automatique.
    9. Re:It's been said, but it's important by rattaroaz · · Score: 1

      Apples and oranges. Technical is what you are physically capable of doing. Moral is what you can physically do, but what others will not allow you to do so. That is why Free software is more of a moral issue than a technical one. Theora could be technically better, but because they have to work around patents, it isn't.

    10. Re:It's been said, but it's important by Vellmont · · Score: 2, Insightful

      I see a lot of statements in your post, but not a lot of argument or information.

      Why is this about H.264 OR Theora? Why isn't it about H.264 AND Theora? Like PNG vs Gif, why do we have to pick one or the other?

      You seem to think H.264 having "won" is a forgone conclusion. Your only arguments seems to be hardware support, and the "lots of data" point. How is that a sustainable situation? Hardware support is nice and all, but every other format the hardware support has become largely irrelevant as processors have gotten faster.

      No, the big issue here is the stupid software patents. Arguing about which one is less likely to anger the patent trolls misses the point. When patent trolls are holding everyone hostage don't start arguing about which hostage is least likely to be taken out and shot first.

      --
      AccountKiller
    11. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      Today, people have data in H.264 format. A lot of data. A long list of hardware devices are made that support it directly. This data is not going to vanish, and people will want to play it. Firefox can choose to support that, or they can choose to become less relevant over time.

      The often made assumption is that H.264 is ubiquitous. But it really isn't. H.264 usage, particularly on the web, is highly concentrated. If YouTube said tomorrow that they were going to move to VP8 for all new videos, 70% of all new web video would be in VP8. The change would happen over night. When you've got such large amounts of content managed by so few players (YouTube, Vimeo, etc) it's very easy to force large change very quickly. Certainly Google's press release after the acquisition of On2 seems to indicate that is exactly their plan:

      http://investor.google.com/releases/20100219.html

      It's worth reading Mozilla's Robert O'Callahan's response to John Gruber:

      http://weblogs.mozillazine.org/roc/archives/2010/03/amor_robustum.html

      Really the only pragmatic choice is not to compromise on open web standards. Every time it's happened historically, it's been a problem that wasn't worth having in the first place.

    12. Re:It's been said, but it's important by Endymion · · Score: 1

      No, because that is only for (last I saw) the Fennec mobile-branch. It's explicitly removed from the normal Firefox branch because of the moral issues.

      Which to me, amounts to Mozilla saying that they support flash and people should keep using it, as that's what people will do.

      --
      Ce n'est pas une signature automatique.
    13. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      Everyone seems to forget that HTML5 is more than just video. Much more. With things like Canvas and other HTML5 technologies, almost anything that can be done with Flash can be done with HTML5. Not saying everyone should just immediately drop Flash (since there's a lot of stuff out there already using it), but just to the people who say "Flash is more than just video" ... well, HTML5 is more than just video too.

    14. Re:It's been said, but it's important by Endymion · · Score: 1

      It is a forgone conclusion that H.264 "won", because hardware manufacturers have come to that conclusion and are building all the new hardware with H.264 support. They are not developing Theora players. Those manufacturers are so certain of that bet, that they are committing a very large sum of money to R&D in the form of all these new mobile devices that play H.264.

      As I recommended up-thread, the side-by-side method is far better, much like PNG vs GIF. That doesn't change the fact that not supporting H.264 is to take yourself out of the running, as H.264 already has enough inertia to have "won".

      --
      Ce n'est pas une signature automatique.
    15. Re:It's been said, but it's important by Endymion · · Score: 1

      Which is why I stake the stance that Mozilla shouldn't sacrifice all of those other cool new features in an effort to make a moral stand about video. Ignoring the codec issue by punting it outside the browser is a pragmatic solution, that is still a huge win because they get to entrench all the cool new features like Canvas, new DOM manipulation, SVG (?), etc.

      That said, SVG+Canvas+Javascript/etc isn't feature-complete yet, when compared to Flash. It's missing some notable things. But that probably doesn't matter, as those features can be added later as HTML5 gets more popular.

      --
      Ce n'est pas une signature automatique.
    16. Re:It's been said, but it's important by ducomputergeek · · Score: 1

      This is what so many have failed to see: for Theora to gain any traction it has to be BETTER than H.264. Right now it's not. H.264 is technically superior and the licensing terms aren't outrageous. It's been a couple years, but the cap was about $3M per year. The mozilla foundation had revenues last year of $70M. I'm not sure where they spend all their money, but this may be case where they're going to put up or shut up.

      People only care that their browser if free (in as beer) and works with all the popular sites. The moment that FireFox no longer works for Youtube, the average users will rapidly replace it with Chrome.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    17. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      wrong. PNG won over GIF exactly because GIF was patent encumbered. Nobody had any problems using GIF until the patent problems appeared.

      You could just have easily said "the war was over with GIF, since its already used everywhere", yet now who uses it?

    18. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      It is a forgone conclusion that H.264 "won", because hardware manufacturers have come to that conclusion and are building all the new hardware with H.264 support. They are not developing Theora players. Those manufacturers are so certain of that bet, that they are committing a very large sum of money to R&D in the form of all these new mobile devices that play H.264.

      This is not very persuasive. Maybe hardware solutions to H.264 are general purpose DSPs which can just as easily be purposed to Theora acceleration. Millions of devices in use today have that capability. In general, the "must have hardware" support line is rather short sighted. By that reasoning there would never be any change in video codecs.

    19. Re:It's been said, but it's important by tepples · · Score: 1

      Like PNG vs Gif, why do we have to pick one or the other?

      Because it's impossible to create a free software distribution containing a browser that plays both H.264 and Theora and distribute copies in Slashdot's home country.

      every other format the hardware support has become largely irrelevant as processors have gotten faster.

      Consider this: MPEG-2 is still relevant because all the advances in DVD players' processors have gone into upscaling.

    20. Re:It's been said, but it's important by Endymion · · Score: 1

      So prove me wrong. Show me mobile devices that play Theora. Show me any little bit of a trend that firmware is magically being written for this hardware.

      Managers don't care, as MPEG is popular and "official sounding", while Theora is "just noise from those free-software hippies".

      --
      Ce n'est pas une signature automatique.
    21. Re:It's been said, but it's important by Billly+Gates · · Score: 1

      No it has not won.

      Youtube and others still use h.263 and there will be hell to pay if I have to pay $10.99 for Firefox for each time I install Ubuntu just so I can be a part of the world.

      We need to stand together and oppose h.264 as it will not be free starting at the end of the year.

    22. Re:It's been said, but it's important by Vellmont · · Score: 1

      It is a forgone conclusion that H.264 "won", because hardware manufacturers have come to that conclusion and are building all the new hardware with H.264 support. They are not developing Theora players.

      Meh. Hardware is essentially disposable. Tomorrow it'll all be obsolete and you'll have to buy the NEW super-great hardware. Sorry, I just don't find this argument very compelling. The idea that one format "wins" and the other "loses" is simply not accurate. Formats live and die, not win or lose.

      --
      AccountKiller
    23. Re:It's been said, but it's important by mqduck · · Score: 1

      Well, the way I read the discussion, it's being worked on for Fennec because Fennec is where things are happening in Mozilla browserland today. If/When GStreamer support in the Fennec branch becomes mature, desktop Firefox support will be extremely likely, unofficially at worst.

      --
      Property is theft.
    24. Re:It's been said, but it's important by cheesybagel · · Score: 1

      Two reasons. Unisys did not ask non-commercial and non-profit applications to pay GIF (actually LZW) patent royalties. Also, a free software library, libungif, was available for decompression which did not infringe in the patents. A browser only needs to decompress the files. Either reason made Mozilla non-liable for patent royalties. This is not the case with H.264. Best they could do would be to support some generic plugin format or system codec facility.

    25. Re:It's been said, but it's important by cheesybagel · · Score: 1

      False. Being worse in features does not mean it is less likely to be adopted. One case is BMP. There were a zillion better image file formats but support for it is common because Microsoft made it standard with Windows.

    26. Re:It's been said, but it's important by Anonymous Coward · · Score: 1, Interesting

      I don't think you love free software at all. You keep droning on the same fatalistic "H.264 is already more popular, the battle is already lost, so the entire computing world should just bend over and take it in the ass, with all the disadvantages that brings" argument.

      Trying to skirt around the issue by letting the end-users violate the patent on their own is an excellent way of turning open source into just the kind of patent bomb that proprietary vendors love to pretend it is to dissuade their customers from choosing it.

      In the long term, the only way to stop this racketeering is a better patent system. Shorter term, there are things people can do to take responsibility;
      - Distribute your videos in an open format. There's lots of content yet to be made, a small head start means little.
      - Make more devices support open formats. Write codecs for platforms that lack them.
      - Improve the open formats. There's open source encoders, and there's still years of work to be done on them.

    27. Re:It's been said, but it's important by jonwil · · Score: 1

      BMP came about as a way to store data on disk (and in the resources of exe files) that could easily be rendered directly through windows GDI.
      You can take the BMP data and feed it straight into GDI to display.

    28. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      Today, people have data in H.264 format. A lot of data. A long list of hardware devices are made that support it directly. This data is not going to vanish, and people will want to play it.

      No-one is saying that you must never, ever use anything but the One True Codec. What is being said is that, FOR THE WEB, there should be a codec, and that codec should be patent-free.

      And as for all of that data in H.264 format right now? It's not on the web (in the sense that people talking about codecs for the HTML5 mean). Nothing is lost, by using another codec. Theora is not fighting to remove the entrenched H.264 from all of existence; it is competing with H.264 in an arena where neither are anywhere near entrenched, and neither more than the other. Horses for courses.

      If Theora "won" and became the de jure standard (AND that standard was obeyed), then eventually, yeah, H.264 might - after a decade or so - vanish from everywhere. Simply because of the benefits of sticking with one format over multiple.

      And as for your "non-free repositories" idea; that's exactly what we have now. You want to decode QuickTime? Install QuickTime. You want Windows Media? Install Windows Media Player. You're missing the point entirely, because having no universal standard is the same has having no standard - that's what standard means!

    29. Re:It's been said, but it's important by Nakor+BlueRider · · Score: 1

      Just a point of correction, it's been made free (as in beer) until the end of 2015. I do agree that using a codec that will eventually cost money seems like a terrible idea however. Unfortunately it's a matter of convincing the majority of browser makers and sites like YouTube of that; otherwise without H.264 support FireFox will be irrelevant long before the cost of the codec becomes an issue.

    30. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      Firefox's whole existence was sound and fury. They should have just stuck with IE 6. If it wasn't for firefox, there really wouldn't have been all this compatibility mess on the web, or the need to deprecate IE 6 in general. I guess they actually cared about freedom and progress in the beginning despite the overwhelming use of IE. Jerks.

    31. Re:It's been said, but it's important by Paul+Jakma · · Score: 1

      +1 to this.

      HTML5 even with H.264, is much much better than the situation today where Flash is used to deliver video. Essentially there are *2* independent dimensions to this battle:

      A) The codec
      B) The delivery technology

      With Flash, you've got unfree, proprietary technology for both dimensions. With HTML5 you fix at least one of these dimensions, regardless of the codec.

      These are mostly separate battles and it's a huge, *huge*, **huge** mistake for any free software and/or open web advocates to delay or hinder HTML5 implementation because of the codecs. And that includes nobbling your HTML5 implementation by not making it easy to support H.264 (e.g. not using an underlying video playing system that at least supports codec plugins). All this does is perpetuate Flash, and hence further entrench H.264 - which is often used as the codec for flash-delivered video.

      Get HTML5 out now, and make sure it can avail of as many, if not all, of the video codecs your users' systems support. Any delay on principles relating to codecs is a massive own goal.

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    32. Re:It's been said, but it's important by brandished · · Score: 1

      But in this case, the so-called Free solution is the wrong choice to make. H.264 has won, and it won years ago.

      Won what? These are two sets of compression algorithms, not two people in a race to the finish. What your saying is equivalent to "the hammer has won, there's no need to use the screwdriver anymore". Each codec has it's uses, there are areas where h264 would be a better choice then theora, and areas where theora would be a better choice then h264, both have there pluses and minuses.

      Also, what makes you think the race is over or will ever end? The MPEG-LA members themselves are still researching newer compression algorithms, they didn't stop when MPEG-1 was released, when MPEG-2 was, nor when MPEG-4 Part 2 was (DivX/XviD), why do think they stopped with h264 (MPEG-4 Part 10)?

      Today, people have data in H.264 format. A lot of data. A long list of hardware devices are made that support it directly. This data is not going to vanish, and people will want to play it.

      This same argument could used for dozens of other formats, most people aren't rushing out to upgrade their DVD (MPEG-2) players or "DivX Certified" devices, vendors have yet to stop producing these devices either.

      it opens up the idea of a Free player

      No it doesn't, have you ever even tried to install Linux or BSD? No "free" installs I've ever come across included an h264 or DivX/XviD decoder by default, I've always had to go to an "unofficial repository" to get one, or look for one of Adobe's flash builds and cross my fingers. MPEG-LA's members have no intentions of giving up their patents or rights to enforce them. Who will support this "free player" if/when an MPEG-LA member sues them into oblivion? Just because they haven't yet doesn't mean they won't or haven't threatened to. The official XviD.org site has refused to host compiled XviD encoder/decoder binaries for years due to threats of litigation.

    33. Re:It's been said, but it's important by shutdown+-p+now · · Score: 1

      As for how to actually implement it, Mozilla et al needs to take a cue from how distros handle MP3 and other patented codecs - foreign "non-free" repositories. The details on how you do that are highly flexible. Mozilla seems to like over-engineering things, so I'm sure they can come up with a Clever Codec Plugin Scheme to automate this, as long as the actual codec is 1) a separate project, and 2) developed outside the org.

      There is a patch that enables loading of video codecs via GStreamer for Firefox, the same way Opera (10.50+) does it. This is a solution in a sense that browser can ship with a legal Theora implementation out of the box, but users (and, more importantly, distros) can plug in other "unfree" codecs if they like them, or if they cannot avoid them.

      So what's the problem with the patch? They don't want it in the mainline tree. Apparently, giving users a choice on what codec they'd like to use (even if it's tilted towards Theora, which is supplied out of the box) is not in accordance with Mozilla's stance on "unfree" codecs. They've got too big of an axe to grind, and they don't want to give up on that, either.

    34. Re:It's been said, but it's important by shutdown+-p+now · · Score: 1

      I don't think you love free software at all. You keep droning on the same fatalistic "H.264 is already more popular, the battle is already lost, so the entire computing world should just bend over and take it in the ass, with all the disadvantages that brings" argument.

      He's a realist. Your camp needs some of them if it is to have any hope of succeeding. To put it in perspective, pure, unabashed idealists are the guys who keep trying to write GNU/Hurd. We all know how well that goes.

      And realists? They are the guys who make it so that a newbie can install (proprietary) NVidia drivers, WiFi drivers, Flash etc on Linux with a single click, ensuring that Linux actually gets some actual use on the desktop outside of hardcore ubergeek community.

      Trying to skirt around the issue by letting the end-users violate the patent on their own

      There are many countries out there in which the format is not patented (because software patents are not valid in such countries).

      Even in U.S., end users can use such a scheme absolutely legally - they just need to buy the licensed codec (Fluendo sells them for Linux/GStreamer).

      Some (probably a lot) Linux users don't want to shell out the cash, and might make the choice to break the law. But it should be their choice to make, not yours.

      Distribute your videos in an open format. There's lots of content yet to be made, a small head start means little.

      YouTube is a "small head start", really?

      Make more devices support open formats.

      And who in the FOSS crowd is in the position to do that?

      Write codecs for platforms that lack them.

      Not an issue so far as I know. Ogg and Theora libraries are ANSI C - if gcc targets some platform, they are there. You might need to wrap them as codecs for a particular framework on desktop systems (DirectShow, QuickTime) - but this was done long ago.

      On devices, though, the problem is hardware accelerated decoding. On which see the point above.

      Improve the open formats. There's open source encoders, and there's still years of work to be done on them.

      The trick here is improving on them without stepping onto the same patents that make H.264 so good. Why'd you think Theora still sucks in terms of quality/bitrate? Various techniques of getting it better (much better even) are widely known for quite some time. It's just that they're all patented.

    35. Re:It's been said, but it's important by TheTurtlesMoves · · Score: 1

      No its not free. Its free to *provide* content in h.264 till 2015. Originally you would have to pay to provide a h.264 movie on your website starting next year. But the decoders and encoders must be licensed and have never been free. This license is not free. In fact for something like firefox you *can't* get a license because MPEG-LA do not provide a license that permits "redistribution".

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    36. Re:It's been said, but it's important by TheTurtlesMoves · · Score: 1

      ... make a moral stand about video.

      They cannot provide H.264 support legally in some countries. Its less of a moral stand that perhaps you think. Also "linking" to something that you know isn't licensed etc can also be a problem legally. Hell the GPL loonies think that by linking to a lib your software is a derivative product (Take that Disney!).

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    37. Re:It's been said, but it's important by DrXym · · Score: 1
      As for how to actually implement it, Mozilla et al needs to take a cue from how distros handle MP3 and other patented codecs - foreign "non-free" repositories. The details on how you do that are highly flexible. Mozilla seems to like over-engineering things, so I'm sure they can come up with a Clever Codec Plugin Scheme to automate this, as long as the actual codec is 1) a separate project, and 2) developed outside the org.

      A video tag is just a specialised object tag. It should be relatively straightforward for Mozilla to define a video plugin as a specialised NPAPI plugin that implements a nsIVideoPlayer interface, declares in some way what codecs & containers it supports, and fires media events through some kind of listener callback.

      Their current stance of hardcoding to theora doesn't make much sense. IE, Safari and Chrome will all natively support h264. Flash and Silverlight already support it. Mozilla will just find itself marginalised if it doesn't do the pragmatic thing and open up the tag to other formats or at least the defacto standard.

    38. Re:It's been said, but it's important by Paul+Jakma · · Score: 1

      With HTML5 you fix at least one of these dimensions, regardless of the codec

      Should really be:

      With HTML5 you fix at least one of these dimensions, and you make it easier to tackle problems in the other.

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    39. Re:It's been said, but it's important by TheRaven64 · · Score: 1

      So prove me wrong. Show me mobile devices that play Theora. Show me any little bit of a trend that firmware is magically being written for this hardware.

      Okay. This is an implementation (in progress, but with good results so far) for the C64x series of DSPs used in TI's OMAP series, which are used in most popular smartphones. It currently doesn't use the any of the built-in video acceleration at all, because it's undocumented, but it wouldn't be too difficult to offload some parts of the CODEC to the VPU in the OMAP given the documentation.

      Most mobile devices don't actually come with a hardware H.264 implementation, they come with hardware implementations of the most processor-intensive steps in H.264. A lot of these steps are also used in other video CODECs.

      --
      I am TheRaven on Soylent News
    40. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      [...] h.264 [...] will not be free starting at the end of the year.

      They changed that: "On February 2, 2010 MPEG LA announced that H.264-encoded Internet Video that is free to end users would continue to be exempt from royalty fees until at least December 31, 2015.", from Wikipedia.

    41. Re:It's been said, but it's important by Anonymous Coward · · Score: 0

      Yes, but Richard Stallman says the precise opposite to what you (and I) think, and he is God around here, so watch what you say :)

      Personally I think his basic premises are ridiculous, but there you go.

    42. Re:It's been said, but it's important by pv2b · · Score: 1

      An important factor is that PNG is technically superior to GIF. The most glaring deficiency in GIF is that it only supports 256 colors.

      PNG also brings alpha channel transparency to the plate (though it wasn't supported in IE6.)

      The only thing GIF does better than PNG is animations. PNG has a companion format, MNG, for animations, but it is not supported by IE for example, so nobody uses it outside of cute tech demos. So, there's still a niche for GIF out there - lightweight animation without loading a browser plugin or a java appet.

      PNG was simply a better solution for lossless compression than GIF ever was. The same cannot be said for Theora vs H.264, unfortunately, so the same situation does not apply.

    43. Re:It's been said, but it's important by WWWWolf · · Score: 1

      the so-called Free solution is the wrong choice to make. H.264 has won, and it won years ago.

      All right, all right, H.264 won the war.

      Now that there's a winner, it's extremely important that everyone implements it. That's the bad side of the having a standard. It's not worth anything until everyone implements it.

      So, now, oh victorious winner, please answer this question: How the hell can open source browsers implement H.264?

      You see, this debate is not about who "won" the war. It's about which standard can be implemented.

      Yes, we know H.264 is superior. Thank you for telling us that over and over. But H.264 proponents have so far failed to explain how the hell can we implement H.264 in any shape or form without requiring weird legal trickery and mysterious booby traps from MPEG-LA's direction.

      So quit harping about better quality and hardware support. We already know those things are true. Tell us how we can implement it so we can get over this ridiculous debate already.

      Mozilla folks aren't "making a stand". They're just puzzled by the H.264 requirements and can't proceed until they have a clear and unambiguous solution. So please, tell them how they can implement H.264 while complying with both their own license terms and H.264's license terms. Surely now that you have the technical superiority issue settled, you can devote energy on this little legal matter, right?

      taking a moral stand with Theora will damage other things, namely HTML5 and potentially Firefox itself.

      And taking a pragmatic stance with H.264 will damage the ability of people who are unable to take the same pragmatic stance to implement the standard. Hence, HTML5 will not be implementable uniformly, so the standard suffers. Firefox will be damaged by not being able to implement H.264 anyway, because it's incompatible with their licensing.

      PNG won out in the end over GIF, mostly, because it had better features. But what enabled that win was that they could both be used at the same time. If early Mozilla branches simply removed GIF support, the browser would have been dead in the water.

      Because the GIF license allowed it to be implemented if you only decode images. Had they not allowed it to be used anyway, as is the case with H.264, well...

      The battle over codes needs to be left for another day.

      "Let's just use what works now, and spend next 20 years living with that mistake. Everyone else is doing it, why not we?"

      As for how to actually implement it, Mozilla et al needs to take a cue from how distros handle MP3 and other patented codecs - foreign "non-free" repositories.

      Also known as "swept under the carpet" repositories. Also known as "download it here and we pretend we look away" repositories. Also known as "this code is for research purposes only, wink wink, nudge nudge, if you know what I mean" repositories. Also known as "we pretend that the license problem doesn't exist and sincerely hope MPEG-LA won't get greedy" repositories. Also known as "servers which cannot be hosted in some countries, thus very much building user confidence" repositories. Also known as "the user gets a big ugly disclaimer upon installation and is told that they're using these components under THEIR financial and legal risk" repositories.

      So your solution is to just treat this whole thing as a skunkworks problem. "This problem cannot be solved legally, so we have to solve it illegally and let the users take the risk." This is hardly an optimal solution, and will likely blow up in someone's face - be it users, developers or the Mozilla Foundation. Anything better in mind?

    44. Re:It's been said, but it's important by arose · · Score: 1

      So prove me wrong.

      He did, you just shifted the goalposts. Hardware support will come if there is demand, if HTML5 would have picked Theora for a baseline codec (I hope Apple chokes on their patent royalties) hardware support wouldn't have taken long. This is about creating demand not going with the patent stream.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    45. Re:It's been said, but it's important by arose · · Score: 1

      The trick here is improving on them without stepping onto the same patents that make H.264 so good. Why'd you think Theora still sucks in terms of quality/bitrate? Various techniques of getting it better (much better even) are widely known for quite some time. It's just that they're all patented.

      It's much easier to do with encoder improvements, which is what parent meant. Thusnelda was a significant improvement over 1.0, Ptalarbvorm seems to have even more in the works. It's improving, and it doesn't really suck, it's just not as good. The Xiph guys know at least a few ways to easily improve the format without violating any patents, contrary to your claims, the real reason not to do it is compatibility.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    46. Re:It's been said, but it's important by Macka · · Score: 1

      The battle over codes needs to be left for another day

      I totally agree. There are two battles to be won here in order to win the war. The first battle (flash .vs. HTML5) has to be fought and won first to get rid of flash. This sets the stage for the next fight. The second (Theora .vs. H.264) can only be fought if enough browsers in circulation at the time have built in support for Theora as well as H.264.

      If Mozilla refuse to support H.264 then one of two things will happen:

      1) In order to support the Firefox customer base, content providers will stick to using H.264 based Flash video. The HTML5 video tag doesn't get used much and Theora doesn't even get a sniff.

      2) Content providers don't give a fig about supporting Firefox and move with the times to HTML5 video. Windows users who've switched from IE to Firefox will look elsewhere when they discover they can't view the content they want and the Firefox customer base will shrink. Some of those will go to Chrome, but IE9 looks like it could be a strong contender and is likely to grab some back. The number of Theora capable browsers in circulation will go down and Theora won't stand a chance.

      The best solution is for Mozilla to support H.264 at this time and strive for a situation where Firefox + Chrome + Opera market share is sufficient that using Theora becomes a viable option for content providers. If Mozilla don't do this Theora is sunk.

      as long as the actual codec is 1) a separate project, and 2) developed outside the org

      Or they could just buy a license. It's not like they don't have the money.

    47. Re:It's been said, but it's important by cffrost · · Score: 1

      Like PNG, "Gif" should be all-caps; it's an acronym for "Graphics Interchange Format."

      --
      Thank you, Edward Snowden.

      "Arguments from authority are worthless." —Carl Sagan
  10. Nope. by Anonymous Coward · · Score: 1, Insightful

    So this person thinks just because it, like any other technology, has the capacity to be sued by patent trolls makes it worse?

    Look, it's plain and simple: web technologies should be open and free. H.264 is not, despite all claims of "people can use it" and "well, it's better". That means nothing. Ogg Theora is open and free, H.264 is not. End of discussion, period.

    Anyone that disagrees either does not understand the importance of using open and free technologies to power the Internet (imagine what would happen if HTML was patent-encumbered as H.264 is!) or a simple troll that has a motivation for him and/or his company to control the web.

    This is a simple, solved issue, but the problem is that the misinformed and the greedy people are dragging it out. End this, make a stand, Ogg Vorbis or you don't get to play. Period.

    AC because mods on /. are largely the people I describe, and I don't want these people to drag my karma down just because they don't like the truth.

    1. Re:Nope. by Endymion · · Score: 1

      And what will you do, when Firefox use starts dropping because IE and Chrome and Safari can all play CoolNewVideoSite's stuff in high-quality full-screen, on many devices because the hardware-support is there? Normal people don't ask about codecs and Free Software issues. They want youtube, hulu, etc to work. They want the videos they captured off their cheap H.264-only camera to play without extra effort, like it will in other browsers.

      People won't see that problem and say "oh, my videos are in a bad format, let's convert" - they will say "oh, Firefox is broken, so I'll use Chrome/IE/Safari/etc"

      --
      Ce n'est pas une signature automatique.
    2. Re:Nope. by Anonymous Coward · · Score: 0

      argh, Ogg Theora, I meant in the last bit. I use so many audio files in Ogg Vorbis format that when I type Ogg it's hard to type out Theora over Vorbis.

    3. Re:Nope. by Anonymous Coward · · Score: 0

      Ahh -- the typical "open zealot" response -- let's talk about how things "should be" so that we can avoid discussions about how things are.

    4. Re:Nope. by Anonymous Coward · · Score: 0

      You're right, we should all make an effort to use free and open formats whenever possible so that won't happen.

    5. Re:Nope. by Anonymous Coward · · Score: 0

      Ogg Theora is open and free, H.264 is not. End of discussion, period.

      Ogg Theora is complete market failure that nobody actually uses for anything. End of discussion, period.

      One thing you GNU hippies are too stupid to understand is that you cannot use standards to dictate your extremely unpopular software on end users. Until there is some sort of natural userbase for Theora, the format is going nowhere -- the internet will simply route around your brain damage.

    6. Re:Nope. by ThrowAwaySociety · · Score: 1

      ... End this, make a stand, Ogg Vorbis or you don't get to play. Period.

      The problem is, I'm afraid you'll get your wish. The Mozilla Foundation is going whole-hog on Ogg (Theora, not Vorbis, whatever) and will die for its principles.

      And it will die. Because Theora has already lost, at least for the foreseeable future. YouTube and Vimeo are already going with h.264. Other browsers are going with h.264. Firefox will be all alone on its moral high ground, and users (who care little for philosophy or religion in software) will desert it. Firefox simply does not have enough influence to carry the entire web along with it in this fight.

      The Mozilla Foundation needs to find a way to live with a world of h.264 video. Maybe a separate library that's a an "optional" install, whatever, but come up with a plan. Otherwise, Firefox will become an irrelevant project, and the FOSS community will lose its most visible and influential citizen.

      If Mozilla.org sacrifices Firefox on the altar of video codecs, it would do far more damage to the idea of a free and open Internet than the proliferation of h.264 will

    7. Re:Nope. by WrongSizeGlass · · Score: 1

      Anyone that disagrees either does not understand the importance of using open and free technologies to power the Internet (imagine what would happen if HTML was patent-encumbered as H.264 is!) or a simple troll that has a motivation for him and/or his company to control the web.

      So if I disagree I'm either stupid or greedy? I'm all for open software, but until the zealots make their software as good as their arguments are aggressive it's not going to come close to commercial software. Not everyone is willing to go without just so open software can seem equal.

      There is a lot of very good open source software, and a lot of mediocre and incomplete open source software, too. If 'open and free' was enough then open source software would be king and commercial software would be trying to catch up, but that's just not the case.

      The issue may be solved for you, but for most of the rest of the world things aren't as black & white.

    8. Re:Nope. by DJRumpy · · Score: 1

      You do realize how silly your argument sounds?

      "H.264 is not, despite all claims of "people can use it" and "well, it's better". That means nothing. Ogg Theora is open and free, H.264 is not."

      I don't recall an H.264 fee when I bought my computer. Neither will end users. The simple truth is that H.264 IS better in quality than Ogg, which is closer in compression ratios to MPEG-2. It takes less bitrate with H.264 to get the same result. That is a huge boon to streaming media sites, AND important to end users. Just because something is free doesn't mean it's better "end of discussion". If the value gained is worth the price, your argument becomes meaningless. I can't speak for others, but H.264 is definitely worth the 'hidden price' given what it allows me to do on my mobile devices and the limited storage available on them. If the cost to me is a few dollars tacked on to the device or OS I purchased, then it's an excellent value.

    9. Re:Nope. by im_thatoneguy · · Score: 1

      Can we please mod down anyone who uses any derivative of: "I'm going to be modded down because of this but..."

      Do as they ask. Keep them modded at 0. I'm so tired of people playing such whiny victims on here. I've never seen one of them actually modded down. /rant.

    10. Re:Nope. by Anonymous Coward · · Score: 1, Insightful

      YouTube and Vimeo are already going with h.264.

      If Google was only interested in going with H.264, then they wouldn't have spent a hundred million dollars on On2 Technologies.

      Other browsers are going with h.264.

      No they aren't. Firefox has gone with Theora. Opera has gone with Theora. Chrome also supports Theora. Safari goes with the QuickTime framework and will play whatever QuickTime plays. Similarly, IE9 will go with the Media Foundation framework and will play whatever it plays. Right now you can reach 100% of HTML5 browsers using Theora and that will remain true once IE9 is released.

      In the end, this isn't about Theora versus H.264. It's about open video versus closed video. If Google releases VP8 as an open codec with Vorbis for audio, everyone will follow pretty quickly.

    11. Re:Nope. by Anonymous Coward · · Score: 0

      I love how every single reply to my original post has been exactly the kind of people I described: people who have no clue about how important it is to have a free, open technology for the internet and people who are probably being paid to rally against a free, open technology so they can control content.

      You should all be ashamed of yourselves. You blame me and others for being "idealists" or "going against what is popular" and all that bull, but when you are promoting an unpopular idea that is *right*, it's important to be that way. I hate to bring up some unrelated thing as a point of comparison, but slavery was pretty popular back in the day. It was wrong. It was unpopular in many circles to discuss getting rid of it. But still it had to be done because it was *wrong*.

      I'm not going to pretend that one should equate the importance of the abolition of slavery to a codec choice, but it IS important to the future of the web. If you don't understand why, or believe that it isn't, then I'm sorry, you're wrong. I'm sorry to say this, but you don't need to have an opinion on the matter. Not every "opinion" is valid when your "opinion" is based on bad information and/or ignorance and can be proven wrong very simply. So just stop. Seriously, your opinion is invalid here, because it's wrong.

      Now that you know this, get out of the way and let Ogg Theora become the single video standard for the web. You want your video to be something else to play it another way? There are converters EVERYWHERE to change Ogg Theora to ANYTHING YOU WANT. So there is NO excuse for you to hate it, at all.

      And to the person I'm replying to: once mods figure out the difference in someone stating what has to be said with facts to back them up and actual, real trolls, we can do that. Until then, those of us that have to relay the fucking TRUTH have to hide behind AC.

    12. Re:Nope. by timmarhy · · Score: 1
      The issue isn't that theora isn't avalible on browsers (thanks for tackeling a total non issue) it's that the big providers like youtube are only going with h.264 as far as they have announced. speculate all you want but your a fool if you make decisions based on such speculation as googles work with vp8

      firefox only has 30% of the market at best, and people will very quickly change once they see they can't play the lastest HD content with it.

      --
      If you mod me down, I will become more powerful than you can imagine....
    13. Re:Nope. by Anonymous Coward · · Score: 0

      >>I don't recall an H.264 fee when I bought my computer. Neither will end users. You will pay where you are getting your content. That me be increased fees or more ads at Youtube or wherever. >>The simple truth is that H.264 IS better in quality than Ogg, which is closer in compression ratios to MPEG-2. That is crap. Look at this: http://people.xiph.org/~greg/video/ytcompare/comparison.html Then go download Opera and Chrome. Opera uses Theora and Chrome uses H.265. Go find some sites that use h.264 like Youtube. It looks horrible. Now go find some sites that use Theora they look awesome.

    14. Re:Nope. by macro187 · · Score: 1

      Ahh -- the typical "open zealot" response -- let's talk about how things "should be" so that we can avoid discussions about how things are.

      Ahh, the typical "serf" response: Be content with the lease your lord offers you.

    15. Re:Nope. by Anonymous Coward · · Score: 0

      You seem to assume that everyone wants to install Theora (completely untrue, I've had it with the dozens of different CODECs) or that everyone can install Theora (iPhone, iPod touch, iPad, BlackBerry, etc).

      Theora is dead from the start, H.264 is already everywhere that matters. Yes, I just said that Firefox doesn't matter. There's alternatives for computers and on mobile platforms it's either Safari or Opera.

    16. Re:Nope. by Anonymous Coward · · Score: 0

      Here, lets try something a little more scientific, shall we?

      http://keyj.s2000.ws/?p=356

    17. Re:Nope. by Anonymous Coward · · Score: 0

      That and the video choice on the xiph.org is low complexity (low motion) and CGI at that (no noise). About the easiest type of video to encode. Throw anything 'normal' at it, and Theora will choke.

      The keyj.s2000.ws link is more representative of real world applications.

    18. Re:Nope. by Anonymous Coward · · Score: 0

      People won't see that problem and say "oh, my videos are in a bad format, let's convert" - they will say "oh, Firefox is broken, so I'll use Chrome/IE/Safari/etc"

      Sorry, but converting a lossy format to another lossy format is always a big NO NO. If it was captured in H.264 you should never under any circumstance change the format.

    19. Re:Nope. by arose · · Score: 1

      Ogg Theora is complete market failure that nobody actually uses for anything. End of discussion, period.

      You can't end a discussion with false assertions, Theora isn't in widespread use. But it is used in Firefox, Opera, Chrome, Wikipedia, Dailymotion, and a small number (for now) of comercial games. Thus the "nobody actually uses for anything" part is demonstratively wrong and you can go back under the bridge.

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

      (thanks for tackeling a total non issue)

      Thanks for ignoring the needs of content providers who aren't Google an Vimeo. You might only care about end users, Mozilla also cares about web developers who aren't comfortable with the 2016 deadline or who want to charge for content, but aren't big enough to pay MPEG LA for the privilege. If being used by Youtube is your definition of winning then H.264 has indeed won, but for many people finish line is default support in all common browsers, because we care about being able to publish our own videos more then playing Youtube's.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    21. Re:Nope. by im_thatoneguy · · Score: 1

      I'll take you seriously when you step out from anonymity. Messiah complex much? Unlike you my identity is extremely easy to determine, down to my address and phone number if you're so inclined. So if you want to accuse me of "being paid to rally against a free, open technology so they can control content" then why don't you find you? Answer: No I'm not payed a penny nor do I have any interest in the debate except in which delivers the best quality.

      By the time H264 free ride ends H264 will be horrifically out of date. It already is. It would be like complaining that MPEG1 or Real videos are no longer patent free online.

      I'm perfectly happy to say unpopular crap online and let my Karma take the hit. You know what, it rarely does. You've got some serious perceived victimization issues.

  11. addendum by Endymion · · Score: 4, Insightful

    None of what I just said should be taken as a reason to not use Theora in addition to H.264. Push the Free solution, of course, but in parallel like what happened with PNG.

    --
    Ce n'est pas une signature automatique.
    1. Re:addendum by onefriedrice · · Score: 0

      None of what I just said should be taken as a reason to not use Theora in addition to H.264. Push the Free solution, of course, but in parallel like what happened with PNG.

      There's no reason for a browser not to use any video format the OS has a codec for. As for what will/should be used (h.264 or theora), I'm not sure why we keep getting these articles as if this is still a war that is being waged. The war is over, h.264 is the winner.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    2. Re:addendum by Hurricane78 · · Score: 1

      But without making false dichotomies and suggesting fights till death, how are they going to pull bullshit “stories” out of their asses?

      Besides: PNG is vastly superior to GIF. Theora isn’t superior to H.264. Not even close. That’s the problem here.
      But I would (have to) use it on a website where there would be a danger of getting sued...

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
  12. At what point.. by nurb432 · · Score: 1

    Is *everything* caught up in a patent fight and we cant do anything at all?

    --
    ---- Booth was a patriot ----
    1. Re:At what point.. by funkatron · · Score: 1

      We're already past the point where it doesn't matter. Like all other spooky voodoo, lawyering is safe to ignore. Patent lawyering doubly so.

      --
      "Welcome to our world. We are the wasted youth. And we are the future too." Yes, I know these are stupid lyrics.
    2. Re:At what point.. by funkatron · · Score: 1

      Small correction "Like all other spooky voodoo, ip lawyering is safe to ignore."

      --
      "Welcome to our world. We are the wasted youth. And we are the future too." Yes, I know these are stupid lyrics.
  13. Dirac by Anonymous Coward · · Score: 0

    What ever happened to Dirac?

  14. Firefox could actually be blind-sided by this by MikeRT · · Score: 3, Interesting

    One of my fears here is that Firefox will be hit as hard by IE 9 as Netscape was with IE 4. Mozilla seems largely oblivious to how ambitious IE 9 is. A hardware-accelerated, multi-process, significantly more standards-compliant browser that supports H.264 out of the box would be just the thing for Microsoft to potentially stop Mozilla dead in its tracks on Firefox adoption.

    1. Re:Firefox could actually be blind-sided by this by Matt+Perry · · Score: 2, Insightful

      Except for that "only runs on a single OS" problem.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    2. Re:Firefox could actually be blind-sided by this by Anonymous Coward · · Score: 0

      It wasn't really IE4 being fantastic that allowed it to curb stomp netscape (though feature wise it was certainly better), it was that Netscape sucked so hard that even the most ardent supporter felt embaressed to recommend it, it was an embaressing pile of poo at release of 4. firefox while in a potentially dangerous position where it could still rapidly sink into obscurity is at least not a buggy piece of shit that forces users to abandon it like netscape was.

    3. Re:Firefox could actually be blind-sided by this by Endymion · · Score: 1

      "Pride comes before a fall"

      It is the height of hubris to think mozilla has the power to order around IE, Chrome, Safari, etc, with only ~47% (or is it only 25% and already falling ?)

      --
      Ce n'est pas une signature automatique.
    4. Re:Firefox could actually be blind-sided by this by Anonymous Coward · · Score: 0

      Install DivX Plus Web Player or Flash and Firefox also has H.264.

      IE9 looks like it's going to be a significant upgrade but it still suffers from the problem that made many people switch away in the first place: Patch Tuesday.

    5. Re:Firefox could actually be blind-sided by this by Matt+Perry · · Score: 1

      You're only thinking about desktop operating systems. You're forgetting about tablets, phones, and who-knows-what kind of devices that we'll see in the next several years. IE only runs on Windows. Safari, Opera, Firefox, and Chrome all run on multiple platforms including desktop and mobile platforms.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    6. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      One of my fears here...

      I also am curious if this'll happen myself, but I take a pretty zen approach. Don't fear it. I don't think we're in much danger of going back to a completely IE-dominated webscape (sorry for that word) like we had 10 years ago or whenever it was. Non-PC browsers (read: "smartphones") are increasingly popular. Macs are increasingly popular. On Windows, Chrome is increasingly popular.

      If Firefox stagnates, the other browsers will continue forward. Either that will be a kick in the pants for Firefox and it'll catch back up (like the last 5+ years have been to IE, if IE9 is actually decent again), or Firefox will fall away like so many pieces of software have before. If the latter happens, in part it'll be sad, but at the same time I don't really go "man, it's too bad Netscape isn't around" or anything like that.

      If Firefox dies, something else will rise to take its place. Maybe they could call it Phoenix. :-)

    7. Re:Firefox could actually be blind-sided by this by ducomputergeek · · Score: 1

      It's more like FireFox risks becoming the IE6 of internet video. H.264 is supported by IE, Safari, Chrome, and Opera. My guess is that fair number of non-/. FF users are going to go to Chrome rather than IE.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    8. Re:Firefox could actually be blind-sided by this by Anonymous Coward · · Score: 0

      What? I remember Netscape 4 being not too bad. Netscape 6 was the flaming pile, and the only reason it was better than Netscape 5 was because they skipped 5. Everything produced thereafter was garbage. In fact, I think Netscape's source code donation will forever be remembered as the largest single contribution to a non-profit organization, the entirety of which was thrown directly into the fucking trash. Posted Anonymously because I was 11.

    9. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      It's more like FireFox risks becoming the IE6 of internet video. H.264 is supported by IE, Safari, Chrome, and Opera.

      That's not true, at least according to my installation of Opera 10.50, as well as the couple searches I've done.

    10. Re:Firefox could actually be blind-sided by this by tepples · · Score: 1

      You're forgetting about tablets

      Apple's tablet uses digital signatures to block any browser other than Safari.

      phones

      Smartphones tend to use Safari (iPhone), Chrome (Android), or IE 7 (Windows Phone 7 Series). Maemo phones have essentially zero market share in the United States, home of Slashdot.

      and who-knows-what kind of devices

      "Devices" are more likely to use digital signatures to block third-party software than PCs are.

    11. Re:Firefox could actually be blind-sided by this by Billly+Gates · · Score: 1

      "One of my fears here [codemonkeyramblings.com] is that Firefox will be hit as hard by IE 9 as Netscape was with IE 4. Mozilla seems largely oblivious to how ambitious IE 9 is. A hardware-accelerated, multi-process, significantly more standards-compliant browser that supports H.264 out of the box would be just the thing for Microsoft to potentially stop Mozilla dead in its tracks on Firefox adoption."

      Ok then. Please pay me $10.99 for your Firefox license and drmed closed source Linux kernel module? What you do not want to pay? I own it. Oh and the license says it must be a drmed system so I guess you have to use Windows or use a drmed version of Linux sorry.

      But hey H.264 is better and you wanted Firefox to support it so stop complaining and pay me.

    12. Re:Firefox could actually be blind-sided by this by cheesybagel · · Score: 1

      Mozilla has both those features (hardware acceleration and sandboxing) in the development branch in case you did not notice.

    13. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      Ok then. Please pay me $10.99 for your Firefox license and drmed closed source Linux kernel module? What you do not want to pay? I own it. Oh and the license says it must be a drmed system so I guess you have to use Windows or use a drmed version of Linux sorry.

      Right, because those are the only two options, and something like a generic Gstreamer-like "let's use the OS's codec" solution isn't possible. </sarcasm>

    14. Re:Firefox could actually be blind-sided by this by jonwil · · Score: 1

      Netscape 4.x had the WORST HTML rendering engine of ANY browser I have ever used.
      Which is why they threw it away and wrote the Gecko rendering engine.

    15. Re:Firefox could actually be blind-sided by this by jonwil · · Score: 1

      What do you do for all the users of Windows XP who dont have OS support for H.264? Or all the people who are using a distro that doesn't ship patented codecs?

    16. Re:Firefox could actually be blind-sided by this by Matt+Perry · · Score: 1

      Apple's tablet uses digital signatures to block any browser other than Safari.

      Apple isn't the only tablet maker. They don't even have a shipping product.

      Smartphones tend to use Safari (iPhone), Chrome (Android), or IE 7 (Windows Phone 7 Series). Maemo phones have essentially zero market share in the United States, home of Slashdot.

      Exactly.

      "Devices" are more likely to use digital signatures to block third-party software than PCs are.

      Mere speculation. There's no telling what future devices will be capable of.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    17. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      What do you do for all the users of Windows XP who dont have OS support for H.264?

      Either the same thing they will do now (with FF not supporting H.264 at all), which is either continue to use Flash or switch to a browser that does support H.264, or they'll go download a third-party H.264 codec.

      (What did all the Linux people do to watch DVDs before there was a licensed DVD player for the platform? And probably the situation wouldn't be that dire.)

    18. Re:Firefox could actually be blind-sided by this by dangitman · · Score: 2, Insightful

      Except for that "only runs on a single OS" problem.

      And which platform does the vast majority of Firefox installations run on, again? Remember, Mac OS X and Linux already have other browsers that support H.264 (Chrome and Safari). This leaves Firefox as the odd one out.

      When video hosting sites switch to H.264 and don't offer a Theora fallback, what do you think people will do? Stop using those video sites, or switch to IE9, Chrome or Safari?

      --
      ... and then they built the supercollider.
    19. Re:Firefox could actually be blind-sided by this by bloodhawk · · Score: 1

      No browser since the advent of browsers was as bad as the initial release of 4, It rendered badly, It was slugish, it was buggy, it was unstable, it leaked memory so fast and so badly it was hard to believe anyone could write code that badly without actually trying. It wasn't just bad it was bloody awefull. Netscape 6 by comparison is a pristine diamond.

    20. Re:Firefox could actually be blind-sided by this by shutdown+-p+now · · Score: 1

      It's not supported out of the box. However, since Opera uses GStreamer, such support can be added by the user.

      In fact, in a bit of irony there, the Linux version of Opera has it best - since it uses the system-wide GStreamer libraries and codec repository, if you have gstreamer0.10-ffmpeg (or whatever it's called in your distro's repositories - this particular name is for Debian/Ubuntu), it will just pick it up and play H.264 just fine - though you may still run into websites trying to do browser sniffing to detect H.264 support.

      On Windows and OS X, Opera uses its own local copy of GStreamer, which only has Vorbis & Theora codecs, so you'll need to compile gstreamer-ffmpeg yourself.

    21. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      Wow, I did not know that; this is the first I've heard of it. Interesting.

      On Windows and OS X, Opera uses its own local copy of GStreamer, which only has Vorbis & Theora codecs, so you'll need to compile gstreamer-ffmpeg yourself.

      Do you happen to know of a HOWTO or anything for doing this and integrating it with Opera? If you don't have one handy don't bother looking or anything, I just thought you might have run across one. A very quick and cursory Google search didn't turn up anything that looks immediately promising to me.

    22. Re:Firefox could actually be blind-sided by this by Anonymous Coward · · Score: 0

      Do you happen to know of a HOWTO or anything for doing this and integrating it with Opera? If you don't have one handy don't bother looking or anything, I just thought you might have run across one. A very quick and cursory Google search didn't turn up anything that looks immediately promising to me.

      I don't know of anyone who has done it so far. I've wasted several hours trying to get DirectShow GStreamer wrapper working (it's in gst-plugins-bad), but that didn't lead me anywhere. Now that I've found out that it's ffmpeg, I might want to try again.

      The problem there is that they use their own GStreamer build, which seems to be built with library names (e.g. gstreamer.dll rather than libgstreamer.dll), compiler switches etc not compatible with stock Win32 builds from http://gstreamer.net/ - so you can't just download ffmpeg binaries from the latter and drop them in. You need to get Opera's version and makefiles first, and then compile ffmpeg within that.

      If/when I get that working, I'll share it (I'm residing in Canada, so there should be no need to worry about software patents for me).

    23. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      If/when I get that working, I'll share it (I'm residing in Canada, so there should be no need to worry about software patents for me).

      Awesome, thanks.

      You might want to put up a page somewhere; if you submit it to /. as a story, I at least hope it'd be posted. If you don't have hosting, let me know.

    24. Re:Firefox could actually be blind-sided by this by Anonymous Coward · · Score: 0

      Yeah because the majority of the fucking idiots out there aren't running that single OS..

    25. Re:Firefox could actually be blind-sided by this by oh2 · · Score: 1

      IE9 will most likely be a big, complex monster like IE8 is. Chrome is the future of browsers IMO, small, fast and unbloated.

      --

      Now the world has gone to bed, Darkness won't engulf my head, I can see by infra-red, How I hate the night.

    26. Re:Firefox could actually be blind-sided by this by Ant+P. · · Score: 1

      When video hosting sites switch to H.264 and don't offer a Theora fallback, what do you think people will do?

      If they do that, the bandwidth used by complainers in their forum will totally eclipse the amount used by their videos.

    27. Re:Firefox could actually be blind-sided by this by tepples · · Score: 1

      What did all the Linux people do to watch DVDs before there was a licensed DVD player for the platform?

      At the time, it involved an SDTV monitor and an $80 DVD player bought at a local WAL*MART. This workaround doesn't apply as well to H.264 because H.264 isn't exclusively for physical media.

    28. Re:Firefox could actually be blind-sided by this by dangitman · · Score: 1

      If they do that, the bandwidth used by complainers in their forum will totally eclipse the amount used by their videos.

      Unlikely.

      --
      ... and then they built the supercollider.
    29. Re:Firefox could actually be blind-sided by this by Bent+Mind · · Score: 1

      I'd have to find the current stats. However, I don't think it is Windows 7. More likely, it is Windows XP. IE9 won't run on that operating system.

      --
      Request a Linux Shockwave player here: http://www.macromedia.com/support/email/wishform/
    30. Re:Firefox could actually be blind-sided by this by Anonymous Coward · · Score: 0

      Right except for that "only runs on a single OS" that 92.57% of the world runs problem. Source: http://en.wikipedia.org/wiki/Microsoft_Windows#Early_versions

    31. Re:Firefox could actually be blind-sided by this by arose · · Score: 1

      Considering the vast majority of OS X surfers use Safari

      Can you back that up with some numbers (that aren't made up on the spot)?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    32. Re:Firefox could actually be blind-sided by this by EvanED · · Score: 1

      At the time, it involved an SDTV monitor and an $80 DVD player bought at a local WAL*MART.

      For most Linux users who wanted to watch DVDs, I suspect you're BSing yourself; it involved libdecss.

    33. Re:Firefox could actually be blind-sided by this by dangitman · · Score: 1

      IE9 won't run on that operating system.

      Well, Safari and Chrome will.

      --
      ... and then they built the supercollider.
  15. When h.264 isn't h.264. by Anonymous Coward · · Score: 1, Informative

    "Today, people have data in H.264 format. A lot of data. "

    And a lot of it totally useless. You see-- full h.264 is so gobsmackingly processor intensive that even a high end multi-core desktop with hardware assist can have a decently hard time of keeping up with it. More importantly some of the features in h.264 are incredibly hostile to fast hardware implementation: For example, the arithmetic coder is purely serial and can't be made to operate in parallel, so the only way to make it fast is to run it at a high clock speed and high clock speed means high power.

    Because of this many "h.264" devices, like the iphone, only support an exceptionally watered down profile called baseline. Most of the technical features h264 has over theora are gone in baseline, b-frames and multiple references, the arithmetic coder, adaptive quantization, 8x8 transform, etc.

    So when you have a "h.264" file you really have no clue when it will play... and if its a "well encoded" file it probably will not play in many places.

    1. Re:When h.264 isn't h.264. by Endymion · · Score: 3, Insightful

      Yes, I am well familiar with the mess that makes up the technical features of "H.264", or more precisely, "MPEG 4, Part 10 AVC", the Part 2 variants ("XVID").

      None of these technical features matter, as most people won't have any idea what you mean. What does matter is that people are currently buying cameras that capture video in Baseline profile, that magically works on a surprisingly number of devices. What matters is that many current devices, and most future devices support High Profile in hardware.

      At no point does Theora enter into it. No devices make it, and no* devices play it (in hardware).

      [*] Almost none. Exception are minimal and not significant enough to matter.

      --
      Ce n'est pas une signature automatique.
    2. Re:When h.264 isn't h.264. by camcorder · · Score: 1

      Please mod AC up. A very good summary of what's broken with H.264. With Theora you have only single profile, which is very efficient, and way better than H.264 baseline technically. Just because patent lobby enforces a codec, it does not make their trap magically superior to others. There're facts, proof of concept videos comparing both H.264 and Theora. How come people are so blind, and parroting FUD of how H.264 is so cool and Theora lost the race. There's no race, and there's a usable, well implemented codec. I'm pretty sure if IE, Chrome and Opera support Theora on them, in less than five years amount of time, Theora content on the Internet will outnumber any other video codecs exist online.

    3. Re:When h.264 isn't h.264. by Anonymous Coward · · Score: 0

      full h.264 is so gobsmackingly processor intensive that even a high end multi-core desktop with hardware assist can have a decently hard time of keeping up with it

      Not true... recent AMD and nvidia cards do full decoding of h264. In fact, my friend's 1.6 GHz Atom system, with the nvidia ion chipset, has no trouble playing 1080p h264, with only about 9% CPU usage. With my own GTX260 card, I can play 1080p with 0-1% CPU usage. I have a large collection of videos from widely varying sources, and I've yet to come across any yet that don't play just fine using a player that supports my 260's hardware acceleration.

      So while h264 certainly IS very CPU-intensive, you're just dead wrong when it comes to hardware-assist.

    4. Re:When h.264 isn't h.264. by Anonymous Coward · · Score: 0

      H.264 is usually identified with the h.264 baseline profile. That's what hardware players play, that's what GPU accelerated codecs play, that's what all your files are. But h.264 is more than just the baseline profile and if you came across a file which used advanced features beyond the baseline profile, your codec would either refuse to play it at all or fall back to software mode and choke on it.

    5. Re:When h.264 isn't h.264. by cheesybagel · · Score: 1

      Most cameras used to support DV25 on DV tape media. Things change. The Chinese hardware manufacturers have tried pushing their own video formats several times so they could refrain from having to pay royalties. If a good free format was available, you would eventually see a lot of hardware supporting it (it is amazing how many hardware devices today have Vorbis and OGG support for example). Why is why the MPEG LA is scared they will lose their revenue source and keep threatening to sue anyone who uses Theora.

    6. Re:When h.264 isn't h.264. by Endymion · · Score: 1

      NVidia hardware plays High Profile stuff just fine, at like 0.1% cpu usage on my system, even with the crazy-extreme b-frame settings I use.

      In practice, though, yes, we me Baseline profile with most of this argument. That is, the "I want to play it on my iPhone/other-mobile/netbook/micro" requests, that are only getting more numerous as time goes on.

      --
      Ce n'est pas une signature automatique.
    7. Re:When h.264 isn't h.264. by Anonymous Coward · · Score: 0

      "At no point does Theora enter into it. No devices make it, and no* devices play it (in hardware)."

      They don't _need_ to play it in hardware because theora is cheap to decode. Jailbroken Iphone 3gs decodes full screen theora at 100fps.

    8. Re:When h.264 isn't h.264. by Anonymous Coward · · Score: 0

      That's the way it goes with big money: they can buy their way in. What's more, then can buy their competitors out.
      There's not much free alternatives can do to prevent it, is there?

      Should competitors just roll over and play dead after some players bought the market for themselves? Hell no. Theora should stay as a contender, an alternative.

    9. Re:When h.264 isn't h.264. by arose · · Score: 1

      None of these technical features matter, as most people won't have any idea what you mean.

      Well I'll be damned, I thought people who do know what the fuck is going on should decide how we should use HTML5, then again with all the absurd claims of H.264 being in the feature while Theora is in the stone age...

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    10. Re:When h.264 isn't h.264. by arose · · Score: 1

      In practice you want to claim both the incredible complexity of H.264 (there is room to grow!) and and the embedded capability (it just works on the iPhone!*)

      * Only baseline profile witch doesn't have as much room to grow. Additional restrictions such as a maximum resolution of 640x480 may apply.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  16. A moral win? by KingSkippus · · Score: 5, Insightful

    And what Mozilla and the Theora-or-nothing crowd are missing is that even staying with Evil H.264, the video-tag/HTML5 is still a huge moral win over Evil Proprietary Flash.

    I'm sorry, but I just plain don't see it that way. It is simply substituting one proprietary format with another. In fact, using the "technically better is better, period" argument of the poster above you, because Flash includes more features than simple video, we should be striving against having a video tag and just continue using Flash.

    The GIF argument just isn't applicable. When everyone standardized on GIF, there really wasn't a viable alternative that worked nearly as well. There is a viable alternative to H.264. Also, keep in mind that when GIF became a de facto standard, the legal environment surrounding patents was much different. It was a time when there was question over whether a compression algorithm could even be patented, and the chance that anyone would actually sue over it was virtually nil. Now, the sue 'em all strategy is actually a lucrative business model.

    Come to think of it, didn't we go through many of these same arguments around 10 years after GIF became the de facto standard? Wasn't the questionability of the patent-encumbering of it a primary driver behind the development of the free PNG format? Didn't it take around like two friggin' decades for PNG to be as widely supported because we didn't really know better in making GIF the de facto format?

    Don't you agree it's pretty damned stupid to repeat that exact mistake yet again under the whole "fool me once, fool me twice" tenet?

    1. Re:A moral win? by Endymion · · Score: 5, Insightful

      You act like H.264 and Theora are both new, and therefore one equal footing, and so there is a choice.

      There isn't. MPEG video is already entrenched. It won so long ago, that hardware manufacturers are now assuming H.264 in most every device. Your "choice" is that we should somehow make the entire hardware and software industry magically switch away from the last few years of work they did, all the current and upcoming products they are releasing, etc.

      Yes, I wish this wasn't the case, and I wish that a patent-free format was used instead. But wishing for things that fly in the face of reality is the attitude of religious nuts, not engineers.

      My argument is that any patents in any of these formats, and all technical features, are 100% irrelevant. Normal people don't care. What they do care about is if they go to the local electronics Big-Box retailer and buy a camera, that they can post the video on the net. And that video will be in H.264 format. They care about watching youtube/etc. Which is H.26{3,4} format.

      If a moral stand is desired, which it should be, it should be done by:
          1) Promoting the proper solution, patent-free, as an alternative
          2) Dodging the problem so you don't drive people away from your cause. ("make the codec separate from the browser")
          3) Use H.264 anyway, and accept the patent lawsuits as a proper form of Civil Disobedience, and get patent law changed.

      The path Mozilla is taking is to going to cause normal users to say one thing and only one thing:
          "Hmm. I browse to $cool_new_video_site and it doesn't work. It does work in IE and Chrome. Firefox must be broken, so I'll use IE instead."

      How is driving people away a win? The scope here is greater than a video codec.

      --
      Ce n'est pas une signature automatique.
    2. Re:A moral win? by IntlHarvester · · Score: 1

      Don't you agree it's pretty damned stupid to repeat that exact mistake yet again under the whole "fool me once, fool me twice" tenet?

      Endymion's argument (which I agree with) is that it's too late. H.264 is already an established de facto standard, completely aside from whatever format people use for HTML5 video. The "mistake" (as you call it) has already been made, support for H.264 is already baked into a zillion software packages and hardware devices. At this point you guys seem like you're pissing into the wind.

      It also seems like you haven't thought through what it means to be a "de facto standard" - the point of the term is such standards arise from a collective process, there is no single entity that can stop them. Bitching about H.264 being a de facto standard accomplishes nothing. The only course of action at this point is the PNG route - the hard work of establishing Theora or something else as an alternate "de facto standard".

      --
      Business. Numbers. Money. People. Computer World.
    3. Re:A moral win? by timmarhy · · Score: 1
      H.264 and jpeg are vastly different situations though - the licensing terms on H.264 are so forgiving and the technology so good.

      you could come up with 100 paranoid hypotheatical's showing how the evil mpeg group could trap us, but i say IF that happens (didn't happen with any of their other techologies) THEN we look at an alternative.

      theora's technology is not as good, and it's got virtually no support. let it go.

      --
      If you mod me down, I will become more powerful than you can imagine....
    4. Re:A moral win? by IntlHarvester · · Score: 1

      The licencing on GIF was extremely forgiving. There were no restrictions on writing a decoder, and an encoder required a one time fee that was trivial for any real software company. (IIRC it was $20K.)

      This was the main reason that GIF as a de facto standard was no issue for most users. It only really affected small timers and free software types who were writing image processing libraries.

      --
      Business. Numbers. Money. People. Computer World.
    5. Re:A moral win? by Paul+Jakma · · Score: 1

      No, the codec and the delivery technology are 2 different, orthogonal things. Regardless of the codec situation, there is an opportunity to at least "free" the delivery tech used on the web, by making HTML5 video widely available.

      Decoupling different parts of the problem from each other allows it to be attacked in parallel, and it allows progress to be made in one area even when there is little progress in another area. Conversely, shackling together sub-problems just gives you a much larger problem, and makes it much more likely you'll fail as you have to overcome all the problems at once.

      See my other post too.

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    6. Re:A moral win? by evilviper · · Score: 1

      The GIF argument just isn't applicable. When everyone standardized on GIF, there really wasn't a viable alternative that worked nearly as well. There is a viable alternative to H.264.

      Theora is NOT a viable alternative to H.264. You might as well say uncompressed video is a viable alternative, too... Or maybe good old MJPEG... Or are you suggesting we should switch to LPs, since they are a viable alternative to patented CD technology?

      Theora's quality is horrendous, and that's simply not going to change. H.264's quality is top of the line. The implementation is terrible, and the standard is horrible. Even if the codec wasn't so bad, requiring a horrid Ogg container is a nightmare.

      H.264 can deliver watchable video in less than 1/2 the bitrate...
      H.264 can deliver high quality video (at higher bitrates) that Theora can't match AT ANY RATE.
      H.264 can be decoded on innumerable devices.
      There are numerous implementations of H.264, and just 1 of Theora.
      H.264 is developing and improving quickly, while Theora continues to stagnate.
      The ONLY THING to come out of Theora is this endless whining politics of utterly irrational idiots, and those naive enough to believe their bullshit.

      Don't you agree it's pretty damned stupid to repeat that exact mistake yet again under the whole "fool me once, fool me twice" tenet?

      PNG caught on, eventually, not because it was patent free, but because it was superior. If it had performed worse than GIF, it would have gone nowhere, patents or no.

      Secondly, GIFs were a problem because nobody knew they needed a license for 15 odd years, and then they got retroactively sued. With H.264, the licensing is up-front, RAND, etc.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    7. Re:A moral win? by SavTM · · Score: 1

      If a moral stand is desired, which it should be, it should be done by: 1) Promoting the proper solution, patent-free, as an alternative 2) Dodging the problem so you don't drive people away from your cause. ("make the codec separate from the browser") 3) Use H.264 anyway, and accept the patent lawsuits as a proper form of Civil Disobedience, and get patent law changed.

      The path Mozilla is taking is to going to cause normal users to say one thing and only one thing: "Hmm. I browse to $cool_new_video_site and it doesn't work. It does work in IE and Chrome. Firefox must be broken, so I'll use IE instead."

      How is driving people away a win? The scope here is greater than a video codec.

      I really don't understand why people feel Mozilla needs to be on board. Yeah, it wouldn't be terrible if H.264 vendors were guaranteed more major browser coverage, but Theora will get better, too. Mobile hardware will improve software decoding to the point that H.264 no longer has a performance edge, even. It's a promise from Moore's Law, even.

      I really don't see your "driving people away" perspective at all, though. Back when IE was the champion of breaking web standards, I would be forced to open a few sites in the other browser - often because the site's owner took especial pride in being "Best Viewed in IE." And what I think everyone remembers from that era is how needlessly frustrating they made, what should have been, very simple things for every web developer in the world seeking to convey a consistent experience.

      As a plugin to play H.264 codecs, it's fine. As a special way to sneak proprietary crap into the HTML5 standard, there is really no reason to pretend the market will be more loyal to Mozilla or serve them better if the same thing is available in three other browsers and still isn't standards-compliant with browsers like Opera.

    8. Re:A moral win? by Anonymous Coward · · Score: 0

      There isn't. MPEG video is already entrenched. It won so long ago, that hardware manufacturers are now assuming H.264 in most every device. Your "choice" is that we should somehow make the entire hardware and software industry magically switch away from the last few years of work they did, all the current and upcoming products they are releasing, etc.

      Uh huh. So what comes after H.264? If we're to go by your "entrenched" metric, then there will never be any change in video codecs. I find this to be a short sighted point of view.

    9. Re:A moral win? by WWWWolf · · Score: 1

      "Hmm. I browse to $cool_new_video_site and it doesn't work. It does work in IE and Chrome. Firefox must be broken, so I'll use IE instead."

      How is driving people away a win? The scope here is greater than a video codec.

      Yeah! And let's implement ActiveX too! That thing has been driving people to IE for so long, under this exact same line of thought! This is vital for interoperability and future of the Web! Microsoft is behind it, so it's bound to become the new standard any day now!

    10. Re:A moral win? by Draek · · Score: 2, Interesting

      "Normal people" are irrelevant here, writing a script to transcode a video from one format to another is trivial. What matters are "normal webmasters", y'know, those that'll go broke trying to pay MPEG-LA's exorbitant fees and close down their websites as result, or will simply refuse to host any sort of video at all and, as such, the entire 'online video' market will be relegated to already-established multinationals, essentially turning it into something as "interactive" and "diverse" as regular TV.

      The World Wide Web was made for the explicit purpose of allowing anyone and everyone to participate. Requiring payment of MPEG-LA's patents is the most blantant rape of that idea that you could possibly make.

      --
      No problem is insoluble in all conceivable circumstances.
    11. Re:A moral win? by arose · · Score: 1

      Theora is NOT a viable alternative to H.264. You might as well say uncompressed video is a viable alternative, too... Or maybe good old MJPEG...

      Hyperbole much? None of what you said there has any truth to it, why should we read the rest?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    12. Re:A moral win? by Anonymous Coward · · Score: 0

      I'm sorry, but I just plain don't see it that way. It is simply substituting one proprietary format with another. In fact, using the "technically better is better, period" argument of the poster above you, because Flash includes more features than simple video, we should be striving against having a video tag and just continue using Flash.

      BY THE SEVEN MAD HELLS, NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!

      Ok, the adrenaline's back to near-human levels, so I'll try to restate that a touch more eloquently:
      More features doesn't automatically make something technically superior, in fact the reverse is more nearly true in practice.

      Specifically, for the limited goal of playing video (not for its original goal of low-bandwidth v
      vector animations, and current uses in games and punch-the-monkey ads), Flash has too many features -- it inspires every site to set up their own player, with different UI and potentially CPU-leeching randomness in their code, and no ability for the user to replace it easily. This use is like if web browsers were JREs, and every site was programmed in Java. Text-mode browsing? only with a custom hack for each site to actually get the text out of the jar, or maybe a sandboxed JRE with all input streams captured. script-blocking? No way! User CSS? Hells no! The technical term for all this is "evil", BTW.

      Flash also sucks because there are basically three implementations: Adobe's Windows implementation (technically good, binary-only), Adobe's Linux implementation (technically bad (inefficient, CPU-hogging, etc.), also binary-only), and GNU gnash (technically bad, open source) -- there are/used to be a couple more OSS options, but I think they've all died or merged -- and then I suppose there's also one or more Mac options, but I'm unfamiliar with that side, and whether it's good like Windows or bad like Linux.

      The Windows runtime is just fine, for what it is -- it's still technically bad, as overkill for the purpose of playing videos, but it's a decent implementation of what it is, definitely competitive with java in their common purposes of animated greeting cards etc..

      On Linux, however, or on BSDs with Linux emulation, there's a horrible problem: Linux marketshare is big enough Macromedia had to put out a Linux runtime to avoid people choosing Java (even though it was kinda slow back then, it was their main competition) for cross-platform reasons, and Adobe has continued to keep it more-or-less updated. But Linux marketshare is not enough for Adobe to put any real effort in optimizing the Linux version, so it works, sort of.

      There's free/open-source replacements, but they're always small projects that never get much support, because Adobe's plug-in is beer-free and still works better -- why waste time playing catch-up? So the only ones working on a free implementation are the zealots (and only the ones who don't hate Flash itself, just the closed runtime), and those who want ports to other platforms -- barely enough effort to keep up with new features as Adobe adds them, they're making very little headway on compatibility, let alone sitting back and optimizing it. And since Adobe's version is binary-only, there's no way to modify it to fix the inefficiencies, even though there are thousands of Linux guys who could do it if Adobe released source.

      Result: Adobe's Linux release sucks and doesn't improve, free replacements suck even harder and barely improve. When it's easier to use flashblock on your netbook and write greasemonkey scripts to rip youtube videos into a temporary folder and watch them with mplayer, something tells me that HTML5's video tag can't help being a huge technical win.

    13. Re:A moral win? by evilviper · · Score: 1

      None of what you said there has any truth to it

      No. No truth... Just facts...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    14. Re:A moral win? by Anonymous Coward · · Score: 0

      "Hmm. I browse to $cool_new_video_site and it doesn't work. It does work in IE and Chrome. Firefox must be broken, so I'll use IE instead."

      How is driving people away a win? The scope here is greater than a video codec.

      Those people are fucking idiots. Let them get on with being idiots somewhere else, out of my way. Win.

    15. Re:A moral win? by arose · · Score: 1

      Facts are not things you state, it's things you show. Show us how Theora stacks up to MJPEG instead of implying that they are basically the same.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    16. Re:A moral win? by Anonymous Coward · · Score: 0

      MPEG video is already entrenched. It won so long ago, that hardware manufacturers are now assuming H.264 in most every device. Your "choice" is that we should somehow make the entire hardware and software industry magically switch away from the last few years of work they did, all the current and upcoming products they are releasing, etc.

      Yes. and VHS won before that. And DVD won once. And cassette tapes, and 8-track tapes and LP72s.

      Do you seriously suggest that we are stuck with H.264 forever now? We can never change again?

      The story of media is that we must not be rigidly stuck on anything. Closed, proprietary solutions are too sticky. Open, free solutions are less sticky and easier to migrate away from.

      Wishing for things that fly in the face of reality is the attitude of religious nuts, not engineers.

      Luckily, the engineers on the Brooklyn bridge didn't think so. Aviation pioneers didn't think so. Linus didn't think so.

      And what's wrong with being a religious nut? MLK wished (and dreamed) for things that flew in the face of reality--1960s reality. Other non-realistic "wishers": Thomas Jefferson? Winston Churchill? Gandhi? George Mallory?

      These people were wishers. But they did more than wish.

      Likewise, supporters of free and open codecs are doing more than wishing.

      George Bernard Shaw said it well:

      The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.

    17. Re:A moral win? by Macka · · Score: 1

      And how does it help "normal webmasters" who want to display their video in Theora when Mozilla's customer base shrinks to nothing because the "normal people" migrate off Firefox? That's what will happen if Mozilla don't support H.264: and good chunk go back to using IE. Mozilla's actions will end up shrinking the number of Theora capable browsers in circulation, will cede market share and power to Microsoft and harm Theora's chances.

      Sometimes you need to know when to retreat from a battle in order to win the war.

    18. Re:A moral win? by Macka · · Score: 1

      Well the parent hasn't replied, so I will. Here is your first comparison to look at, and here is your second. Both found H.264 to be superior.

      Oh, and here's some crow for you to snack on while you're reading.

    19. Re:A moral win? by arose · · Score: 1

      He claims that Theora is more comparable to MJPEG, then H.264. I ask for a comparison demonstrating this, as in, the fact that Theora and MJPEG are comparable. You link to a H.264 vs Theora comparison and act all smug that H.264 came ahead, even if I never disputed it would. What?

      With that out of the way, why should a take a comparison that encodes from a H.264 source and gives different frames for comparison without explaining why? And, heck, at least use x264, no need to handicap H.264.

      You might have missed that whole embedded device playback debate, so if you want to impress me with H.264 results (I'm quite familiar with them however, it's good), link to something that uses baseline profile as that's what people will have to use in HTML5 for it to play on the iPhones of this world.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    20. Re:A moral win? by Draek · · Score: 1

      The same way that it helps normal power users who want to use their ATI and Intel cards on 64-bit OSes when Linux's customer base shrinks to nothing because the "normal people" migrate to Windows due to their refusal to ship closed-source drivers with the kernel.

      Taking a stand will always alienate some people, but surrendering will similarly always hurt your chances of success. The key is in knowing when to do which one, and I (along with the Mozilla guys and a good portion of the F/OSS community) believe it's time for the former. You don't? fork Firefox and add h.264 support yourself, or just move to IE if that's what you want.

      --
      No problem is insoluble in all conceivable circumstances.
    21. Re:A moral win? by Macka · · Score: 1

      The same way that it helps normal power users who want to use their ATI and Intel cards on 64-bit OSes when Linux's customer base shrinks to nothing because the "normal people" migrate to Windows due to their refusal to ship closed-source drivers with the kernel

      Unfortunately that doesn't aid your argument one bit, as it's Windows Firefox users that are the relevant demographic here. Last October Phoronix reported on a question and answer session with NVIDIA's Andy Ritger who leads the user-space side of the NVIDIA UNIX Graphics Driver team, where he stated that their linux driver download rate is 0.5% the size of their Windows driver downloads. Kind of puts things in perspective eh!

      Taking a stand will always alienate some people, but surrendering will similarly always hurt your chances of success. The key is in knowing when to do which one, and I (along with the Mozilla guys and a good portion of the F/OSS community) believe it's time for the former.

      No one who advocates including H.264 in Firefox today is talking about surrender. If you must, then think of it as a strategic retreat in order to regroup for a battle to come, because now is not the right time. Getting Theora friendly browser installs out there in sufficient numbers before making a big push for change is essential for success. If you can't see that then I'm sorry for you, cos you're wrong. As for a good portion of the F/OSS community supporting your position, I don't think you have a majority on this at all. There are a lot of hard core F/OSS supporter out there who are speaking against against Mozilla on this one because we believe it's tantamount to cutting off your nose to spite your face.

      You don't? fork Firefox and add h.264 support yourself, or just move to IE if that's what you want

      Not possible for me as I don't run Windows (only Mac OS X and Linux). I've already made my choice (to eat my own dog food) and switched to Chrome/Chromium on both of them. And this is why your argument (and Mozilla's) is so weak: why should I make the effort to fork and hack Firefox when competitors (Google and Opera) have already done the hard work for me? For a Windows user who doesn't give a flying fig about F/OSS and just wants to view their content the choice is even easier: IE, Safari, Chrome or Opera. Firefox will be the least attractive option because functionally it will appear broken.

      As for me, well you can serve me H.264 or Theora and I'm covered thank you very much.

    22. Re:A moral win? by Macka · · Score: 1

      He claims that Theora is more comparable to MJPEG, then H.264

      No he didn't. What he said was:

      You might as well say uncompressed video is a viable alternative, too... Or maybe good old MJPEG

      He was being sarcastic! My response was to refocus on the rest of his message: you know, the bulk of it that you ignored where he weighed H.264 against Theora.

      With that out of the way, why should a take a comparison that encodes from a H.264 source and gives different frames for comparison without explaining why? And, heck, at least use x264, no need to handicap H.264.

      You should have taken a closer look at my second link where Martin Fiedler (KeyJ) does the encoder comparison. He is using x264. Try reading it.
       

  17. Its the codecs that make flash non-free by Anonymous Coward · · Score: 0

    Adobe has graciously released every single part of flash under a royalty free perpetual license complete with open documentation, and source code for many of the core components (like the virtual machine).

    Adobe doesn't make a dime directly off flash, they make money selling authoring tools. Their ability to do so is not diminished at all by freeing flash further.

    The codecs are what are keeping flash itself proprietary, because they are the only part that adobe doesn't have the authority to free. ... and the codec patent holders don't share adobe's second-market interest, so they have nothing to gain by freeing the codecs.

  18. White text overlay. by Anonymous Coward · · Score: 0

    You mean like this?
    Theora
    H.264

    Let me guess, you're viewing the videos with VLC?

    1. Re:White text overlay. by EvanED · · Score: 1

      Let me guess, you're viewing the videos with VLC?

      I'm guessing there's some reason that you bring this up? I went through that comparison during the last H264 vs Theora story, and came to the same conclusion that the guy you're replying to did: the H264 version is way better. Right down to the compression artifacts around the text. (I also pointed out some time marks where artifacts were visible in other cases too, and I didn't really notice anything that bad during the H264 video.)

      However, I did my comparison with VLC. Is there something about VLC that makes it an unfair vehicle for comparison? What would you suggest as software for Windows for viewing Theora at ideal quality?

    2. Re:White text overlay. by TheRaven64 · · Score: 1

      Actually, I'd expect the opposite. VLC doesn't seem to do a very good job of decoding H.264. If you grab some H.264 from iPlayer, for example, the BBC logo in the corner is crisp and clear with QuickTime but a blurry blob of white with VLC. It may be that VLC also fails to do some post processing with Theora. Theora relies a lot on post processing to get anything approaching good quality.

      That said, in a lot of cases, Theora is good enough. If you watch a TV show on DVD that was filmed on video tape, you're lot losing anything from the DVD quality. Watch the same thing on BluRay and you won't see a difference: the source material is simply not good enough for it to make a difference. A huge amount of streamed content is recorded on cheap consumer-grade equipment and transcoded a couple of times. Both H.264 and Theora will give reasonable, but not great, quality for this kind of content because the bottleneck is not the CODEC.

      --
      I am TheRaven on Soylent News
    3. Re:White text overlay. by Anonymous Coward · · Score: 0

      VLC has a bug which causing Theora to show up very blurred, it's been fixed in development versions of VLC but not released versions.

      I found this out here, after making an ass of myself when I tried to make fun of Theora.

      If your output doesn't look like those screenshots by nullc than there something is wrong with your software.

      As far as recommended tools: Firefox 3.5/3.6 is the best cross platform recommendation I've heard.

      I don't know where the below comment about postprocessing is coming from. Very few tools enable post-processing for Theora. Theora has in-loop deblocking, making it less reliant on post-processing than just about any other codec except H.264.

      What theora needs for good quality is sufficient bitrate. It can take less bitrate before falling down than mpeg2 or xvid, but H.264 is still better for very low rates. With sufficient bitrate Theora looks excellent, and anyone who says otherwise is a liar.

    4. Re:White text overlay. by EvanED · · Score: 1

      As far as recommended tools: Firefox 3.5/3.6 is the best cross platform recommendation I've heard.

      I don't care about cross platform, and I can't make either Firefox or Opera display the video full-screen, which means I can't fairly test it.

  19. Re:Who is Thom Holwerda? by neuroklinik · · Score: 0, Troll

    Thom... stop the astroturfing. Sheesh.

    Oh.. and OSNews is a shitty site. So pbhbhtptpbhh.

  20. Re:Who is Thom Holwerda? by WrongSizeGlass · · Score: 1

    When Thom Holwerda speaks, I LISTEN.

    I had no idea you, um, he was related to E. F. Hutton. Thanks for the update.

  21. they never said any such thing by YesIAmAScript · · Score: 1

    They said it will be free to end users and net streamers until 2016. They have not said what happens in 2016. Specifically, they did not say they will seek all users to buy a license in 2016.

    The last time the free (end-user) license period ended was in 2010 and they extended it then. They could do the same again. Or maybe not. No one can be sure.

    --
    http://lkml.org/lkml/2005/8/20/95
    1. Re:they never said any such thing by peragrin · · Score: 1

      If they think they can make a lot of money by strong arming people to pay for it do you think they would? Remember greed rules businesses.

      The only reason they didn't now is because HTML5 isn't set and there are competing products out there ready to step in. if in 2016 there is no current competition then they just might start charging people.

      --
      i thought once I was found, but it was only a dream.
    2. Re:they never said any such thing by Rockoon · · Score: 1

      Wrong. The only reason they did it now is because almost 100% of end users ALREADY HAVE A LICENSE.

      Period. It the American Linux users players H.264 that have something to worry about.. but there is just not enough of them to make a stink about their illegal ways.

      --
      "His name was James Damore."
  22. Regardless of the actual fact of the matter by NemosomeN · · Score: 1

    That was a fairly piss-poor rebuttal, especially the opening paragraph, where he sidesteps the claims of outside patent holders. Submarine patents are still possible, they are just less effective. One could stall the application until infringing usage is found, then scurry it along to give grounds for suit. Personally, I don't care. From what I've seen/heard, Ogg Vorbis/Theora are wastes of CPU cycles. Can anyone name any formats that have had issues with patent encumbrances in the past? Oh wait, I can. MP3 and GIF (LZW not RLE). It's too bad that those were crushed by patent suits, they could have had some promise.

    --
    I hate grammar Nazi's.
    1. Re:Regardless of the actual fact of the matter by NemosomeN · · Score: 1

      Hate to reply to myself, but my bullshitometer just went off. "Some submarine patents had a "hidden" time of 40 years (see footnote 27 on page 9)." This is an outright lie, if you look at the source he quotes. The patent in question was delayed by the PTO, not the submitter, due to national security concerns (Valid or not). This would be a case of a patent submitter being marginalized, not using underhanded tactics.

      --
      I hate grammar Nazi's.
    2. Re:Regardless of the actual fact of the matter by cheesybagel · · Score: 1

      All current browsers support PNG (including transparency) in case you did not notice.

    3. Re:Regardless of the actual fact of the matter by NemosomeN · · Score: 1

      What? I don't get the relevance.

      --
      I hate grammar Nazi's.
    4. Re:Regardless of the actual fact of the matter by sowth · · Score: 1

      MP3 and gif were both bad examples in that case. People knew (or should have known) they were violating patents when they used those formats.

      Audio MPEG is similar to MPEG-LA in that they are both based on the work of a for-profit consortium who has patents on them. Anyone doing work on an mp3 encoder probably would have known they were violating a patent, they just may have thought no one would try to enforce the patents against open source developers because they were giving away the programs for free. Many companies who had patents would say they were free for non-profit and educational use.

      GIF was created by compuserv in the '80s. They specifically stated LZW in the spec, so they did not just come up with a compression scheme on their own and it happened to be the same as a patented one. They had to know it was patented.

      From what I understand of Theora, a company designed the codec (VP3) which they sold for a while, then decided to donate it to the ogg project. Most undoubtedly, they must have had at least a few lawyers and patent experts verify they weren't violating anyone's patents. On2 also explicitly released any patent claims they have to VP3, so I don't see how there are any worries there.

      The only possibility would be if some patent troll produces a patent which they "creatively reinterpret" into a claim which Theora violates, and they have to spend a half million to defend themselves. How is any other codec safe from such claims? How is anything safe from such claims? Even a wheel. Which is why the current patent system is shit.

    5. Re:Regardless of the actual fact of the matter by NemosomeN · · Score: 1

      My point was that even formats that were known to be used in violation of patents flourished because of technical superiority. I'm not saying no alternatives existed, but there's no doubt that in their niches, MP3 and GIF were/are king (though GIF has lost some ground, I don't know or care how much). People will use the "best" choice regardless of patents.

      --
      I hate grammar Nazi's.
  23. Mr. Horn, you're mucking FUD & I'm calling you by Qubit · · Score: 3, Insightful

    According to the article here, MPEG LA CEO Larry Horn said this (emphasis mine):

    In addition, no one in the market should be under the misimpression that other codecs such as Theora are patent-free. Virtually all codecs are based on patented technology, and many of the essential patents may be the same as those that are essential to AVC/H.264. Therefore, users should be aware that a license and payment of applicable royalties is likely required to use these technologies developed by others, too.

    When asked directly about the MPEG patent holders:

    Ozer: It sounds like you are saying that some of your patent holders own patents that are used in Ogg. Is that correct?

    Horn: We believe that there are patent holders who do.

    Okay, Horn: Who are the patent holders and what the patent numbers?

    Ozer: It sounds like you’ll be coming out and basically saying that to use Ogg, you need to license it from MPEG LA. Is that correct?

    Horn: That is not what we said. We said no one in the market should be under the misimpression that other codecs such as Theora are patent-free.

    Ummmm... You're just spreading FUD and trying to be coy about it. But you just look like a smarmy used-car salesman. I call bullshit.

    I have a good deal of respect for people like Monty who get this kind of shit thrown at them day-in and day-out from whatever weak-willed, money-over-morals, cardboard-cutout figurehead the MPEG-LA props up today to go and do their dirty work.

    Mr. Horn, your arguments are hollow and your acts of fear-mongering are unbecoming of any man. I'm not sure I'd go so far as to call your actions reprehensible had you not graduated from Yale and then gone on to get a J.D. from Columbia. I mean, honestly, is the quantity of cash they're throwing at you so large that you can pile it on top of your morals like steel weights in a flower press, keeping your inner sense of honor pressed down so it doesn't jump up and kick your ass for being a manipulative and deceitful businessman?

    Show us the patents or shut up.

    --

    coding is life /* the rest is */
  24. Re:Who is Thom Holwerda? by Anonymous Coward · · Score: 0

    It really kicks ass when Thom bitches about how horrible software patents are while he makes money from Google's patented software ad network. The excuses he makes for Apple doesn't help his image much either.

  25. A monastery administrator named Art invented those by tepples · · Score: 1

    And guess what: both of the lossless video codecs you mentioned have prior art. But explaining how would only serve to kill the joke.

  26. Encoding vs. decoding by tepples · · Score: 2, Interesting

    If early Mozilla branches simply removed GIF support, the browser would have been dead in the water. Nobody would use it, because the images people already have were in GIF format.

    It wouldn't have been necessary. The LZW patent under GIF was believed to apply only to encoding, not decoding. The editors of the H.264 patents were far more careful in this respect.

  27. Vector animation by tepples · · Score: 1

    Today, there is even more data wrapped up by Flash.

    True, OGV is an alternative to H.26x video in Flash containers. But what alternative to Flash do you offer for making vector animations like Badger Badger Badger and most of what's on Newgrounds? True, one can hack something together with JavaScript and SVG, but nobody has made authoring tools for that.

    1. Re:Vector animation by TheRaven64 · · Score: 1

      You'd probably use the canvas tag rather than SVG. There are already some impressive games using this combination. I suspect that the best authoring tools will end up coming from Adobe in the end. For them, the Flash player is a money sink. It exists solely for one purpose: to encourage people to buy the Flash authoring tools. If browsers support everything that Flash does (something Adobe encouraged by donating the JIT / VM from the Flash plugin to the Mozilla project) then they can ditch the Flash player and just target the browser directly.

      --
      I am TheRaven on Soylent News
  28. Pet peeve: use of "IP" by tepples · · Score: 1

    "Internet Protocol lawyering"? You didn't need to correct yourself because "intellectual property" is already not a specific area of law. Patent law is as different from trademark law as it is from real estate law.

  29. Compression? Who needs it? by itsybitsy · · Score: 3, Funny

    Soon lossy compression will be irrelevant.

    I demand full resolution video without lossy compression. Screw the compressors.

    Bandwidth and storage capacity will soon make lossy irrelevant even at HD * N scales.

    I want the FULL resolution that the cameras recorded.

    If you don't then enjoy your pixalated movies.

    1. Re:Compression? Who needs it? by Anonymous Coward · · Score: 0

      Are you implying that the cameras themselves at full resolution are not 'lossy'? If so, you have a lot to learn about how the human eye coupled to the brain compares to a camera and recording media. The only 'lossless' system for our evolved level of ocular perception is the eyeball and the brain, and only then if there are no genetic defects.

      Everything is 'lossy' to Superman!

    2. Re:Compression? Who needs it? by itsybitsy · · Score: 1

      Yes, the camera chips are lossless when they record the frame dude. Then they usually apply some horrific resolution losing algorithm. For example, the awesome Red Cameras (http://www.Red.com) apply a horrific Wavelet compression algorithm just to transmit the data to the computer storage unit. So by the time it's at the desktop RedCine it's already lost detail. Then it goes through all kinds of hellish algorithms and ad hoc magic to make a movie. By then it's lost, lost, and lost more detils. Then it gets put into the really horrifly low resolution of BlueRay HD 1080p which is sold as the best thing there is. So yes. I don't want a DCT encoded piece of crap that loses detail, give me RAW Uncompressed video! I demand it!

      By the way I write video compression algorithms, so I know of what I speak.

    3. Re:Compression? Who needs it? by Anonymous Coward · · Score: 0

      FYI, a typical HD camera can spit out 100MB per second, which would just about saturate a 1Gbps Ethernet link and fill a 1TB hard drive in 3 hours.

      dom

    4. Re:Compression? Who needs it? by Anonymous Coward · · Score: 0

      OK, the parent was probably joking, but there is a grain of truth: as more internet bandwidth becomes available, squeezing another 10% from the codec becomes less important; as more CPU becomes available, straightforward implementation can end up beating funky patented algorithms. In fact, we see that already with VoIP, which is slowly moving towards simple, free codecs.

    5. Re:Compression? Who needs it? by Zouden · · Score: 1

      give me RAW Uncompressed video! I demand it!

      By the way I write video compression algorithms, so I know of what I speak.

      Why do you write compression algorithms when all you want is uncompressed video?

      --
      "A week in the lab saves an hour in the library"
    6. Re:Compression? Who needs it? by Anonymous Coward · · Score: 0

      Yeah, and BMP will become the de-facto image standard of the web any day now!

    7. Re:Compression? Who needs it? by itsybitsy · · Score: 1

      "Why do you write compression algorithms when all you want is uncompressed video?"

      money. dah.

    8. Re:Compression? Who needs it? by itsybitsy · · Score: 1

      Actually I wasn't joking at all. I write lossy and lossless video compressors for a living. I can tell you that there is nothing like the original lossless video feed. Lossy video compression is just junk no matter how good they are. Lossy is lossy is lossy no matter how you slice it up.

      When people get fiber into the home slipping terabytes over for a video will be nothing of note.

    9. Re:Compression? Who needs it? by Anonymous Coward · · Score: 0

      try PNG

  30. Re:Mr. Horn, you're mucking FUD & I'm calling by YesIAmAScript · · Score: 1

    Show us the patents or shut up.

    I do agree it would be nice of the MPEG LA members who feel that their patents cover Theora would come out and talk about it, it is unlikely that Larry Horn has anything to do with this. MPEG LA only has to do with these patents in terms of licensing them for use with H.264. They almost certainly don't have any responsibilities (or freedom to talk about the situation) when it comes to Theora.

    So it's really up to the individual patent holders to come out. I wish they would do so.

    Also, "show us the patents" is probably off base too, because the patents are right here.

    http://www.mpegla.com/main/programs/avc/Documents/avc-att1.pdf

    What you seem to mean is show us where the infringement lies.

    --
    http://lkml.org/lkml/2005/8/20/95
  31. Good post ... by Anonymous Coward · · Score: 0

    Like the VHS vs. BetaMAX format war, quality has NOTHING to do with it. It has to do with how a technology is adopted in the marketplace. Whether you like it or not, 'superior' technologies die in the marketplace all the time (sticking with a media theme: record players, reel-to-reel tape decks, 8-tracks, etc.), or are supplanted by newer, superior technologies. Crying over it after it's happened is just pissing in the wind.

    Theora may be a really good codec for video, but it's not the end-all-be-all of video codecs, and neither is H.264 (MPEG-4). In a few years there will be a newer, more superior codec that will be introduced that will supplant BOTH of them and the pissing will begin all over again.

  32. Re:Mr. Horn, you're mucking FUD & I'm calling by Qubit · · Score: 1

    "show us the patents" is probably off base too, because the patents are right here. [link to MPEGLA]

    While it's possible that one of the patents listed on the MPEG website is what Mr. Horn is talking about, note that he only said that they (which I read as an official stance of the MPEG-LA) believe that some patent holders (which may be one of the MPEG partner groups) hold patents that Ogg infringes:

    Ozer: It sounds like you are saying that some of your patent holders own patents that are used in Ogg. Is that correct?

    Horn: We believe that there are patent holders who do.

    He was about as vague as possible there. Talk about FUDmongering.

    They almost certainly don't have any responsibilities (or freedom to talk about the situation)

    Sure, the constituent companies may keep him on a short leash, but he can't be stupid enough to believe that making vague statements about Ogg infringing patents isn't going to cast doubt on the use of Ogg, right?

    I mean if he just said "I can't legally talk about Ogg," or "I won't talk about Ogg because I can only talk about some aspects but not others," then at least he'd have a leg to stand on. He would have drawn a line about what he would talk about so that he wasn't in a position of bashing "the other guy's formats."

    But that's not what he did. He opened his mouth and made a comment about Ogg being infringing. And then later he (with the MPEG-LA) replied with "no comment". It just sounds like he's running away and hiding under the coattails of his organization.

    --

    coding is life /* the rest is */
  33. Re:Mr. Horn, you're mucking FUD & I'm calling by MobyDisk · · Score: 1

    I think you misread his stance. This isn't like saying <cue italian mafia accent> "Hey, if you sell our competitors products, you *might* find some trouble..." His point is simply that in today's age, all software encroaches on some patent somewhere. He is right about that. Should it scare people away from Theora? Probably not. Theora is still going to be less patent-encumbered than h.264, but it probably isn't 100%.

  34. Re:Mr. Horn, you're mucking FUD & I'm calling by mveloso · · Score: 1

    There are key facts that pop out in the article:

    * xiph sent letters and got no responses. They interpret the lack of response to mean a lack of violation. The real world doesn't work that way. Lawyers are deployed strategically, and it may not be in the patent holder's interest to respond to a letter.

    * MPEG-LA's credibility is low, because they license patents. However, you could just as easily say that theora's credibility is just as low, because they have just as much incentive to denigrate the claims of the MPEG-LA.

    * why the reference to Apple? It's like a gratuitous call-out to apple h8trs. The MPEG-LA is more than Apple. Is Apple really the new M$?

    The validity of patents are determined in the courts. You can send all the letters you want, but it's in the courtroom where the rubber meets the road. Your belief, or lack of belief, has no bearing on the validity or lack of validity of a patent.

  35. Re:Mr. Horn, you're mucking FUD & I'm calling by YesIAmAScript · · Score: 1

    I see what you mean that he doesn't say it's MPEG LA people who say they have patents on Theora.

    As to the 2nd part, I agree him opening his mouth is to line his pockets and MPEG LAs.

    --
    http://lkml.org/lkml/2005/8/20/95
  36. What a fucked up summary! by Anonymous Coward · · Score: 0

    Had to read it like 3 times to figure it out... Slashdot editors are the shit all right.

  37. Re:Mr. Horn, you're mucking FUD & I'm calling by Anonymous Coward · · Score: 0

    Show us the patents or shut up.

    This is one of the big things that needs to change about the patent system. Patent holders are under no obligation to either enforce, or even show, their patents, which lets them get into e-penis fights over IP. It lets them go with non-enforcement of their technology so that it can be better adopted by being free-as-in-beer (you can even give out free-as-in-freedom code for reference implementations, as with what happened with MP3).. then when entire industries require the use of said technology, start litigating and requiring license fees, which people and businesses will have to pay or risk being sued into bankruptcy.

    Hell, the MPEG-LA has already even said this will be their strategy.. they won't enforce the H.264 patents for a couple years so it can get better usage among the web, then they'll start requiring license fees. Any system implementer that doesn't pay will be unable to display the majority of video online, making such systems much less viable in the consumer marketplace. It's tantamount to extortion, really.

    In addition, they can make FUD claims like "Ogg is patented by us", without giving any proof, so they can get license fees for someone else's work. It's not like Xiph.org can prove it isn't patented (you can't prove a negative), and there's way too many patents to even attempt to look through to even try to break through people's doubt. That's just all kinds of fucked up.

    IMO, patent holders should be required to enforce their patents when they're made aware of violations (as is the case with copyright), and any violators need to be shown the exact patent(s) that are being violated. If they don't, then they lose the patent.

    The other big thing that needs to change, IMO, is to make it so patents are not transferable. You invent the technology, it's your patent. The "highest bidder" should have no claims at all to those patents, even if you die.

  38. interesting... by hitmark · · Score: 2, Interesting

    as i am sure at least one person affiliated with osnews would be yelling the typical "h264 should/must be used, as its the codec that produces the best quality video"...

    --
    comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    1. Re:interesting... by Anonymous Coward · · Score: 0

      for me, this one person cost osnews its credibility.

      Being accused of posting a personal non-news related rant on a supposed-to-be news site, Thom Holwerda answered

      "This IS our own site. WE decide what gets posted here. If you want control, start your own website or go to Digg.com. It's quite silly to tell us what to do with OUR website. I won't tell you what to do with yours either."

      So IMHO the site doesn't deserve any more credibility than the next-best ranting blog.

  39. Youtube with html5 works in epiphany. by Anonymous Coward · · Score: 0

    Epiphany has been able to play HTML5 videos in youtube for several months now, and I never understood why firefox was lagging behind. Is the epiphany project vulnerable to law suits? Is the gstreamer project vulnerable to law suits? Which project is breaking the patent?

  40. PSNR and SSIM by emanem · · Score: 1

    Hi guys, I've use this software qpsnr to measure PSNR/SSIM of different encodings.
    I thought this could be good to share!
    Cheers,

  41. Can't we just watch videos and not care, please by Anonymous Coward · · Score: 0

    All I care is price and if Theora's free nature translates to end product prices like less ads on pages where it's used, then I'll probably watch more Theora content.

    If I want better quality, I use higher bitrates regardless of the codec I'm using.

  42. Luis Villa's reply to Thom by formal_entity · · Score: 1

    Luis Villa (lawyer who works for Mozilla) also wrote an important rebuttal to Thom's post: http://tieguy.org/blog/2010/03/26/more-patent-101-and-some-patent-licensing-201-advanced-class/

  43. Re:Who is Thom Holwerda? by TheRaven64 · · Score: 1

    They know their subject, and they know it well

    They used to know their subject. Over the past couple of years, they've posted a lot of uninformed drivel, mostly authored by Thom Holwerda. It used to be a site I'd check daily. Now I don't even bother with the RSS feed.

    --
    I am TheRaven on Soylent News
  44. Reality is far more than the maths we use by Anonymous Coward · · Score: 0

    Reality is far more than the maths we use. When you make a REAL HARDWARE object you have to use maths to see if it will work and help design, but the maths you use are not reality and you have to work around the reality that stops your model from being 100%.

    In software, the reality IS the maths. You do not have to work around the parasitc stiction forces of your gearbox, you just increase the divisor to change the "gearing" of your software engine.

    Software is maths and your attempts to say "there is less difference between maths and sort-of-maths" does not apply.

    When rubber hits road in reality, there are things you never modelled and never COULD model that rear up and put the kybosh on your idea. In software, this never happens.

  45. Re:Mr. Horn, you're mucking FUD & I'm calling by Anonymous Coward · · Score: 0

    Apple is important because they are the authors of Safari and they refuse to support Theora.

  46. Newsflash by Anonymous Coward · · Score: 0

    This is the only site on the Internet that still believes there is a debate here. H.264 has won, and Theora has lost. If your software's licensing scheme doesn't allow you to play H.264 video, it sounds like you have a choice to make:

    a) continue running said software (and lack video features), or
    b) use different software.

    If Internet video is as important to you as you seem to imply it is, I think you'll choose (b) above. Otherwise... have a coke and a smile and shut the fuck up.

  47. OSS is always in the wrong by Anonymous Coward · · Score: 0

    Whether it is linux vs os x, gimp vs photoshop, oggvorbis vs mp3, oggtheora vs h264, the list is endless but the reality is clear: open source as a software development methodology is broken. It produces inferior software and does not support nearly as diverse or health a corporate ecosystem.

  48. You're selectively reading by pem · · Score: 1
    "One is simulated based on math and the other is a very expensive working / failing product"

    That's silly. All the design work and running the simulations together winds up being more expensive that the mask in a lot of cases. (A large part of the expense of the first run of silicon is the lost time to market when you get it wrong.)

    Also, you missed the part where I said the risk approached zero because the non-patentable prior art of the simulation showed that the expensive hardware was going to work.

    You also missed the part where I said that you can put the exact same "code" (Verilog or VHDL RTL) into an FPGA (and you can buy general-purpose FPGA boards that can be reprogrammed over and over, just like computers can be programmed over and over with software) or into a hard coded chip. Using the FPGA is NOT a simulation; NOT pure math, because you can hook it up to other devices and make it do physical things. Now, you have three implementations -- simulation, implementation in an FPGA via a bitstream that looks just like software, and implementation in gates. (Oh, btw, the tiny little patented part is very small and could be implemented on a multi-chip shuttle run for a couple of thousand dollars in a non-bleeding edge technology.) Oh, and by the way, there is a fourth implementation. You can take either the RTL you are simulating in the computer, and actually hook the computer up to other parts of the final circuit, and now the computer itself (which may be very fast these days compared to the requirements for the hardware you are building) is an actual part of a physical process.

    Now, which of these four implementations is or isn't patentable, and why?

  49. Re:Mr. Horn, you're mucking FUD & I'm calling by /dev/trash · · Score: 1

    We'll come out when the money is good enough.

  50. Dancing kitten : Does quality really matters ? by DrYak · · Score: 1

    ...and both codecs will be basically used to post on Youtube and Dailymotion:
    recordings of dancing kittens, taken with camera-phone, and which have gone through several stage of destructive re-compression set at atrociously low quality levels.
    To the point that the result is filled with artefacts. And MPEG-1 could have achieved a good-enough quality on similar bitrate.

    In my opinion, the whole debate about codec quality is irrelevant given the current main usage of videos.
    It will only become important once HD TV channels streaming HD contents on their websites get *really* widespread.

    By then, I really, really hope that some newer, disruptively better and patent free codec emerges. Big supporters of open web such as Google have the technical and financial capability of making such thing happen. I'm still looking in the general direction of wavelets, but perhaps there are other better stuff.

    Until then Theora is a good enough stop-gag measure, that will provide a nice alternative for the subset of the market which specifically needs a patent-free solution. Even if that means storing 2 copies of the video media (most websites actually store much more different versions). Even if the second Theora copy is actually at *lower bitrate* than the first "HQ H.264" copy.
    Bad quality video (of dancing kittens) is better than no video at all or continued reliance on 3rd party closed software for the open-source crowd.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  51. Re:Who is Thom Holwerda? by Anonymous Coward · · Score: 0

    He's just some random, snot-nosed kid.

  52. Ad absurdam by pslam · · Score: 1

    None of this is true:

    • H.264 can deliver watchable video in less than 1/2 the bitrate...

      A fair comparison is more like 10-30% less, depending on the content. The comparisons which show 1/2 the bitrate are for an H.264 profile that most devices can't play (e.g iPhones), and that's not useful.

    • H.264 can deliver high quality video (at higher bitrates) that Theora can't match AT ANY RATE.

      Where did you get that from? Of course it can. Unless you mean truncation artifacts? I'm guessing you didn't

    • H.264 can be decoded on innumerable devices.

      So can Theora. You don't need hardware to decode a VGA 30fps Theora stream on modern smartphones. It'll manage it fine entirely in software.

    • There are numerous implementations of H.264, and just 1 of Theora.

      Is this a point in favor or against? There is only one implementation of gcc. There is only one implementation of Vorbis (actually, I've written another myself). There is only one implementation of WebKit, but hey that powers a large fraction of browsers in the world. What is this supposed to demonstrate?

    • H.264 is developing and improving quickly, while Theora continues to stagnate.

      The H.264 specification is set in stone and won't change. Implementations for both are being actively developed. The Theora spec could change (minor or major version upgrade) just like it could for H.264. This is surely just your opinion and not fact.