Slashdot Mirror


Hardware-Accelerated Ogg Theora For Firefox Mobile

An anonymous reader writes "Matthew Gregan is working on bringing David Schleef's DSP accelerated port of Theora to Firefox Mobile. He writes on his blog: 'The C64x+ DSP is often found in systems built upon TI's OMAP3 SoC, such as the Palm Pre, Motorola Droid, and Nokia N900. Last year, Mozilla funded a port, named Leonora, of Xiph's Theora video codec to the TI C64x+ DSP. David Schleef conducted the port impressively quickly and published his results. The intention of this project was to provide a high-quality set of royalty-free media codecs for a common mobile computing platform. The initial focus is Firefox Mobile on the N900, so I am working on integrating David's work into Firefox. To experiment with other facilities Firefox could use to accelerate video playback, and test integration, I've been hacking on a branch of a stand-alone Ogg Theora and Vorbis player originally written by Chris Double called plogg.'"

176 comments

  1. Give it up, Mozilla :) by carlhaagen · · Score: 0, Troll

    Just... let it die. I know free/open is awesome, but Theora is just bad bad bad on top of awesome. If you refuse to look towards H.264, then at least now you can look towards Google and VP8 now. Bury Theora.

    1. Re:Give it up, Mozilla :) by wisnoskij · · Score: 1

      But even if it is bad now because it is free/open and being used, is it not very likely to improve in the future?
      But I know very little about the format, maybe it is just fundamentally flawed.

      --
      Troll is not a replacement for I disagree.
    2. Re:Give it up, Mozilla :) by carlhaagen · · Score: 1

      It is fundamentally flawed. And, sure, the encoder might improve (even if this does not solve the fundamental problems), but with time passing by, people embracing Theora will be stuck with a lesser and thinner experience, while the rest of the world plays grande ball with the H.264 format and the superior encoders available for it, while Theora falls behind and Firefox loses ground.

    3. Re:Give it up, Mozilla :) by Ash-Fox · · Score: 1

      Just... let it die. I know free/open is awesome, but Theora is just bad bad bad on top of awesome. If you refuse to look towards H.264, then at least now you can look towards Google and VP8 now. Bury Theora.

      I can't tell if you're being serious or trolling.

      --
      Change is certain; progress is not obligatory.
    4. Re:Give it up, Mozilla :) by TheRaven64 · · Score: 4, Insightful

      Theora isn't bad. It's better than MPEG-1 and a MPEG-2, and similar quality to MPEG-4 part 2. It's not as good as H.264, VC-1, or Dirac, but that's not the same as being bad. It's perfectly acceptable for a lot of uses.

      --
      I am TheRaven on Soylent News
    5. Re:Give it up, Mozilla :) by sopssa · · Score: 1, Redundant

      I think he is serious, and so am I.

      Theora is a shitty format. I wrote a long post about it before, but like the parent stated, it's fundamentally flawed. You can't improve it because of the initial design and its limitations.

      If we want a open source codec, it's way better to support VP8. You do know that Theora is based on VP2, right?

    6. Re:Give it up, Mozilla :) by imroy · · Score: 4, Insightful

      I'll admit that Theora isn't the greatest video codec. But it's been explained many times that Mozilla simply can't use MPEG-4 AVC/h.264 because of the patents involved.

      Mozilla and wider Open Source world has three options: (not mutually exclusive)

      • Work to kill software patents so they can use AVC/h.264 and other codecs that come after it.
      • Make Theora better.
      • Make something better than Theora, but free of patents.

      But no amount of whinging will make them use AVC/h.264. It's simply not an option at the moment.

    7. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 1, Informative

      VP3. One bigger.

    8. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      You do know that Theora is based on VP2, right?

      No it isn't.

    9. Re:Give it up, Mozilla :) by Ash-Fox · · Score: 2, Informative

      I still don't understand his comment, because if we do what he suggest, and look towards Google:
      http://mobile.slashdot.org/story/10/04/10/1147254/Google-Funds-Ogg-Theora-For-Mobile?art_pos=8

      Seems Google's view opposes his.

      --
      Change is certain; progress is not obligatory.
    10. Re:Give it up, Mozilla :) by sopssa · · Score: 1, Redundant

      Mozilla can use AVC/H.264. They just need to do it via the OS, like I think IE and Safari will do, and Opera already does. H.264 is already directly supported on Windows 7 and Mac OSX. Linux users need to do their tricks, like with MP3.

    11. Re:Give it up, Mozilla :) by Trepidity · · Score: 1

      That sounds like the worst possible solution, because then you'd have Firefox working differently on different platforms. I sure don't want to go back to the Bad Old Days where FF on Linux couldn't view the same media as FF on Windows.

    12. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      it would display the same media, if the right codecs were installed.

      surely it is a better solution than playing no videos with HTML5 at all because mozilla refuse to provide a way to decode the files?

    13. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 2, Informative

      Mozilla can use AVC/H.264. They just need to do it via the OS, like I think IE and Safari will do, and Opera already does. H.264 is already directly supported on Windows 7 and Mac OSX. Linux users need to do their tricks, like with MP3.

      They only way they can do as you suggest is by severely compromising Firefox. This has been answered exhaustively many times. See Mike Shaver's blog post about it. To quote:

      People have raised questions about using existing support for H.264 (or other formats) that may already be installed on the user’s computer. There are issues there related to principle (fragmentation of format under the guise of standardized HTML), to effectiveness (about 60% of our users are on Windows XP, which provides no H.264 codec), to security (exposure of arbitrary codecs to hostile content), and to user experience (mapping the full and growing capabilities of to the system APIs provided); I’ll post next week about those in more detail, if others don’t beat me to it.

      Security is not to be underestimated. It's worth noting that IE9 will not support all media formats supported on the host operating system, purely to limit the attack vector surface area available. See this comment by Microsoft's Frank Olivier on the IE blog. He's talking about image formats but the same applies to video formats:

      We've not heard many requests for additional image types - to limit the attack surface in a web browser, it is a good idea to not expose more decoders.

      See also Chris Blizzard's blog post about the decision to only support open video in Firefox. And most importantly of all, don't worry about. Open video is the way forward for video on the web. Theora is here now, VP8 may be joining it next month, and Dirac may join both in the future.

    14. Re:Give it up, Mozilla :) by imroy · · Score: 5, Informative

      I sure don't want to go back to the Bad Old Days where FF on Linux couldn't view the same media as FF on Windows.

      That's currently the situation with plugins. They're pieces of object code, so you're dependent on the plugin developer to provide you with a version for your OS/architecture. For example, Flash (something that HTML 5 and the video tag could replace) is (AFAIK) only available on three mainstream platforms - Win/x86, OSX/x86, and Linux/x86. There's a beta version for x86-64 and special versions (Lite?) for embedded devices, but that's pretty much it. As for the Quicktime plugin, there's no Linux or *BSD support at all (mainly because there's no QT on those platforms), although there's plugins that use VLC or totem, etc instead.

      Now, lets look at Firefox. The Debian iceweasel package (Firefox without the branding) is listed as being available for 14 architectures (not counting the unofficial 68k port that languishes at 2.0). That includes x86-64 for your latest AMD64/Intel64 machines, armel for your portable ARM devices, powerpc for your old G3/G4/G5 PowerMacs, and a bunch of other architectures too. None of those are supported by Adobe or the many other companies that have, over the years, tried to lock us into their proprietary software with binary-only plugins. So I'm siding with Mozilla for some very practical reasons. Theora's not the best out there, but I'd prefer the web to be open to all.

    15. Re:Give it up, Mozilla :) by Qzukk · · Score: 2, Insightful

      the rest of the world plays grande ball with the H.264 format and the superior encoders available for it

      Up until Dec 31, 2010 when the patent holders have stated that they're ending the royalty-free period and it becomes the GIF of the video world.

      You can bet that with all the money youtube loses now, Google ain't going to pay for millions of H.264 videos and H.264 will literally disappear overnight. I'm sure Google is working overtime on getting that shiny new codec they just bought into chrome, if not firefox. Perhaps they'll write a flash player for it too.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    16. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      Theora's not the best out there, but I'd prefer the web to be open to all.

      when every website has H.264 videos the web will be closed to all who use firefox, what a great result...

    17. Re:Give it up, Mozilla :) by Nadaka · · Score: 2, Informative

      VP8 is RUMORED to be made open source sometime in the near future.

      We do not know for sure.

      Theora isn't very good, but that doesn't mean that it is utter crap.

      At youtube video quality it uses somewhere around 10% more bandwidth than h.264. It gets less efficient with HD content.

    18. Re:Give it up, Mozilla :) by Jenming · · Score: 2, Informative

      That is not correct.
      http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf

      (DENVER, CO, US – 2 February 2010) – MPEG LA announced today that its AVC Patent Portfolio License will continue not to charge royalties for Internet Video that is free to end users (known as Internet Broadcast AVC Video) during the next License term from January 1, 2011 to December 31, 2015. Products and services other than Internet Broadcast AVC Video continue to be royalty-bearing, and royalties to apply during the next term will be announced before the end of 2010.

      --
      Morpheus, God of Dreams.
    19. Re:Give it up, Mozilla :) by arose · · Score: 3, Insightful

      And Microsoft and Apple CAN implement Theora, then we can have a nice baseline and H.264 fans can still use it if they wish to.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    20. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 2, Interesting

      No, that's a stupid idea.

      Not all systems have an h.264 codec installed. Mac OS X does (via QuickTime). Windows 7 has an included h.264 codec, but neither Windows Vista nor Windows XP do. The only available h.264 codecs for Windows Vista and Windows XP are either commercial (which nearly nobody will have installed) or unlicensed. On Linux, there is exactly one licensed h.264 codec (Fluendo's GStreamer plugin), which virtually nobody has installed.

      So this doesn't solve the problem at all. It also has some rather bad side-effects.

      First, it makes the browser behave differently depending on which OS you're using. Mac OS X can basically only play h.264 and MPEG-4 ASP out of the box, and only in the MPEG-4 / QuickTime container format. Windows XP and Vista can play a couple of useless, outdated codecs in the AVI container, or one of several versions of WMV. Oh, and Windows XP didn't ship with a WMV9 codec. On Linux... anything can happen - GStreamer may or may not be available, and what codecs it actually contains varies widely (although it almost always includes Theora). What about embedded systems that don't even have their own codecs? What about embedded systems which have their own codecs, but provide no way to install new ones?

      It also increases the attack surface, which will cause more security vulnerabilities. Say you just let DirectShow handle any media type. You've not only exposed Windows' h.264 decoder, but also every other decoder and parser available through DirectShow. Some of those are from the mid to late 90's. More likely than not, they're full of security vulnerabilities.

      To put it another way:

      IE9 ships with it's own h.264 decoder. It's the only way to support h.264 on Vista, and it limits the attack surface. Silverlight ships with it's own h.264 decoder, for exactly the same reasons. So does Flash. Safari on Windows effectively ships with it's own h.264 decoder (via QuickTime). It only uses the OS supplied codecs on a Mac, where Apple control the entire platform anyway. Chrome includes it's own h.264 and Theora decoders on all platforms. Opera includes it's own Theora decoder, via an included version of GStreamer. Firefox includes it's own Theora decoder.

    21. Re:Give it up, Mozilla :) by 99BottlesOfBeerInMyF · · Score: 1

      They only way they can do as you suggest is by severely compromising Firefox. This has been answered exhaustively many times. See Mike Shaver's blog post about it [off.net]. To quote:

      People have raised questions about using existing support for H.264 (or other formats) that may already be installed on the user’s computer. There are issues there related to principle (fragmentation of format under the guise of standardized HTML), to effectiveness (about 60% of our users are on Windows XP, which provides no H.264 codec), to security (exposure of arbitrary codecs to hostile content), and to user experience (mapping the full and growing capabilities of to the system APIs provided); I’ll post next week about those in more detail, if others don’t beat me to it.

      We've all read the arguments (I hope), we just don't buy them. I'm sorry but the OS should be handling video codecs for applications. Too many different applications such as video players, teleconferencing, browsers, and editing software all need to use codecs and the OS handling them on behalf of applications is simply the right way to engineer things. I can use Theora in my browser right now using HTML5 tags because I gave the OS a codec and my browser can use any codec I have installed. In practice I don't use it though.

      See also Chris Blizzard's blog post [0xdeadbeef.com] about the decision to only support open video in Firefox. And most importantly of all, don't worry about. Open video is the way forward for video on the web. Theora is here now, VP8 may be joining it next month, and Dirac may join both in the future.

      As I said, I can use Theora, but I don't... because there are basically no Theora streams in any of the mainstream video sites I use. Theora may be here, but you'd never notice. To a whole lot of us this the refusal of Firefox to build in support for the OS's video codecs (and yes there are plenty of h.264 codec available for WinXP via WMP) means Firefox just can't watch some of the video on the Web without reverting back to a Flash plug-in. Great job promoting security there guys. I feel so much safer.

      You say don't worry about Firefox's open video. I'm not, I'm worried about it's ability to play mainstream video securely, because it sure as hell can't do so today like other browsers can. I don't know if they're trying to get people to fork Firefox or if they think Firefox has too much market share and they're determined to get people to switch to Chrome. It looks like pigheaded ideology being put before users to me.

    22. Re:Give it up, Mozilla :) by evilviper · · Score: 1

      As for the Quicktime plugin, there's no Linux or *BSD support at all (mainly because there's no QT on those platforms), although there's plugins that use VLC or totem, etc instead.

      Now you're on to something...!

      That's right, since Quicktime uses standard H.264 with AAC, there were plugins for nearly every system on the planet since day 1.

      The problem with flash isn't that it's a big bad plugin. The problem is that it's proprietary. H.264 is NOT proprietary. It just happens to be patented.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    23. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      I'll admit that Theora isn't the greatest video codec. But it's been explained many times that Mozilla simply can't use MPEG-4 AVC/h.264 because of the patents involved.

      And has been explained many times before, that's complete, utter bullshit.

      All Firefox needs to do is use a generic video decoding pipeline for it's backend. GStreamer and DirectShow come to mind (interesting sidebar, they're *already doing this with Fennec*, they just refuse to backport the changes to Firefox for idiotic political reasons). Then, Firefox can immediately use *any* codec those pipelines support, and given the video tag is supposed to be codec agnostic, that's a good thing, as it gives the web developer a choice of a wide variety of codecs to target. And if the user happens to have installed an h264 codec for one of those pipelines, then voila, Firefox immediately gets H.264 support without ever shipping any patented code.

      Honestly, how is the hard to understand? The simple fact is, there are *no technical or legal arguments for not supporting H.264*. None. Zero. Nada. The only reason to refuse is for political or ideological reasons.

    24. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 0, Troll

      That sounds like the worst possible solution, because then you'd have Firefox working differently on different platforms.

      Oh please, I can't believe this bullshit. All you need to do is put up a little box that says "Sorry, you don't have that codec installed. Go install it", just like they already do for plugins.

      Honestly, this must be the worst excuse yet. The Mozilla defenders sure seem to be getting desperate...

    25. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 2, Insightful

      They only way they can do as you suggest is by severely compromising Firefox.

      Utter garbage. Firefox is *already* subject to any bugs in the underlying OS on an incredibly wide range of issues. Hell, just a few years back, Firefox was compromised thanks to an image rendering bug in GDI on Windows. So, what, *now* they've suddenly decided they're going to reimplement OS-supplied services for fear of security issues? Please.

      On the bright side, at least the Mozilla devs *tried* to invent a technical excuse for not supporting H.264, now that people have realized there are no legal barriers to doing so. Of course, it's a stupid, irrelevant, indefensible technical excuse. But, hey, kudos for trying, guys.

    26. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      >The Mozilla defenders sure seem to be getting desperate...

      What exactly are you trying to imply with that? From what I saw, the desperation was from the h.264 brigade. So now theora isn't in the HTML5 spec; well guess what, neither is h.264 and its egregious licensing!

    27. Re:Give it up, Mozilla :) by msclrhd · · Score: 1

      If Firefox uses something like DirectShow on Windows:
          1/ they will need to have codec support for theora (not necessarily installed);
          2/ the H.264 codec is only available on Windows 7 and later, and they cannot legally ship a H.264 codec for XP/Vista;
          3/ they need to ensure that the DirectShow output works with the layers/svg/smil infrastructure as well as DirectWrite/Direct2D on Windows 7 -- e.g. does having a rotating, scaling video in a smil/svg file work;
          4/ they need to ensure that the audio output works well with other audio content (e.g. playing a and object at the same time);
          5/ they would have to work around/live with any issues in the use of DirectShow/framework.

      Same for GStreamer (which may not necessarily be installed on all Linux platforms).

      In addition, you also need a multimedia layer in the browser to support all of the multimedia frameworks, in addition to the audio and graphics support layers required at the moment.

    28. Re:Give it up, Mozilla :) by allo · · Score: 1

      but its not a firefox issue anymore. the user needs to get his codecs, as he needs for other purposes, too.

    29. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      Utter garbage. Firefox is *already* subject to any bugs in the underlying OS on an incredibly wide range of issues. Hell, just a few years back, Firefox was compromised thanks to an image rendering bug in GDI on Windows. So, what, *now* they've suddenly decided they're going to reimplement OS-supplied services for fear of security issues? Please.

      Maybe you should read the comment again carefully. If video codec support can be treated as an "OS supplied service", why won't IE9 support all OS supplied codecs?

    30. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      Maybe you should read the comment again carefully. If video codec support can be treated as an "OS supplied service", why won't IE9 support all OS supplied codecs?

      They *are* using OS supplied codecs, they're just choosing to limit the options available to reduce the security footprint. Firefox could do exactly the same thing.

      Meanwhile, the MS statement was about image codecs. The OP was speculating they would do the same for video codecs, without any actual evidence to back that claim.

    31. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      1/ they will need to have codec support for theora (not necessarily installed);

      User problem.

      2/ the H.264 codec is only available on Windows 7 and later, and they cannot legally ship a H.264 codec for XP/Vista

      User problem.

      3/ they need to ensure that the DirectShow output works with the layers/svg/smil infrastructure as well as DirectWrite/Direct2D on Windows 7 -- e.g. does having a rotating, scaling video in a smil/svg file work;

      Yup, it's a technical challenge. But don't tell me it's a blocker, as other browsers are already using this approach.

      4/ they need to ensure that the audio output works well with other audio content (e.g. playing a and object at the same time);

      See above. And this one's far easier (what audio output framework doesn't support hardware mixing multiple output streams in this day and age?).

      5/ they would have to work around/live with any issues in the use of DirectShow/framework.

      Yup, they sure do.

      In addition, you also need a multimedia layer in the browser to support all of the multimedia frameworks,

      You mean kinda like how they already wrap the platform-specific GUI libraries, rendering, etc, etc?

      Sorry, *none* of these issues is a blocker. Not a single one. People are claiming Firefox *can't* support H.264, either for baseless legal reasons, or dubious technical reasons. But the reality is that Mozilla could add support if they wanted to. They *choose* not to because they took an ideological stance early, and now they don't want to back down, even if their choice is not in the best interests of their userbase.

    32. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      What exactly are you trying to imply with that?

      I'm not implying anything. I'm *saying* that defenders of Mozilla's ridiculous stance have tried to claim:

      1) Mozilla simply *can't* support H.264 for legal reasons. This is false, as there is no need for Mozilla to ship any codecs.
      2) Mozilla simply *can't* support H.264 using OS-provided codecs because it's, like, hard and stuff. This is just BS.
      3) Mozilla simply *can't* support H.264 using OS-provided codecs because of, like, security and stuff. As if Mozilla packaging it's own multimedia framework is suddenly so much better, and it's much wiser to not take advantage of OS-provided services that are regularly vetted and patched.

      And now Mozilla simply *can't* support H.264 because then Firefox would behave differently on different platforms. As if it doesn't do so already.

      In short, I'm saying, not implying, flat out stating, the people defending Mozilla's ridiculous position (either Mozilla staff themselves, or Mozilla fanbois) are now scraping around at the bottom of the barrel to come up with excuses to support their stance, instead of just admitting that the original choice was purely ideological, and their current stance is essentially an unwillingness to simply admit they were wrong.

    33. Re:Give it up, Mozilla :) by Pecisk · · Score: 1

      Chrome already supports Theora allright.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    34. Re:Give it up, Mozilla :) by Pecisk · · Score: 1

      I would argue that Youtube qualifies. But let's see. Also this claim is not binding. In fact, MP3 patent holders had a public pledge of not enforcing patent fees from free software/open source mp3 players, but later changed their mind. So I wouldn't sleep on it.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    35. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      They *are* using OS supplied codecs, they're just choosing to limit the options available to reduce the security footprint. Firefox could do exactly the same thing.

      Uh huh. And why doesn't Chrome? And what of the 60% of Windows users with no H.264 support in the OS? And what of other desktop platforms and mobile platforms?

      Your approach is a poor solution which limits cross platform deployment, which limits Firefox source distribution, which promotes closed formats, all of which limits competition and innovation with artificial barriers to entry for new developers and is ultimately bad for the web.

      Meanwhile, the MS statement was about image codecs. The OP was speculating they would do the same for video codecs, without any actual evidence to back that claim.

      Okaaay.. so you're suggesting that video codecs are somehow more secure that image codecs? I'd like to see that proof. It'd be spectacular. In any case, read here:

      http://blogs.msdn.com/ie/archive/2010/03/16/html5-hardware-accelerated-first-ie9-platform-preview-available-for-developers.aspx#9979730

      Microsoft doesn't even support WMV videos in IE9.

    36. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      Thank you for this deeply insightful evaluation.

    37. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      Uh huh. And why doesn't Chrome?

      Because Google decided to just package H.264 with Chrome, as they're apparently unconcerned about patents. Firefox is concerned, so they need another approach.

      And what of the 60% of Windows users with no H.264 support in the OS?

      They, uh, install the codec?

      And what of other desktop platforms and mobile platforms?

      Fennec is *already* moving to gstreamer for video support. Firefox just decided not to backport the implementation.

      Your approach is a poor solution which limits cross platform deployment,

      Bull. Shit. Gstreamer is already cross-platform. For those freak platforms with no gstreamer or DirectShow support, they can just use the existing Theora implementation.

      Okaaay.. so you're suggesting that video codecs are somehow more secure that image codecs?

      Yeah, that's exactly what I said.

      Or maybe I didn't say that at all, but you apparently felt like knocking down a strawman for kicks.

      So, allow me to elucidate: All I said was that the OP pointed to an article about image codecs. We have no idea what MS will do when it comes to the video element. Though I'll be very surprised if they don't use DirectShow as the decoder backend (though they may choose to limit the codecs they expose through the video element).

      Microsoft doesn't even support WMV videos in IE9.

      Well goodie for them. But I'll bet you they're using DirectShow or something similar, rather than building an entire new decoding pipeline specifically for IE. Why? Because they aren't fucking idiots.

    38. Re:Give it up, Mozilla :) by grcumb · · Score: 1

      In short, I'm saying, not implying, flat out stating, the people defending Mozilla's ridiculous position (either Mozilla staff themselves, or Mozilla fanbois) are now scraping around at the bottom of the barrel to come up with excuses to support their stance, instead of just admitting that the original choice was purely ideological, and their current stance is essentially an unwillingness to simply admit they were wrong.

      And you're completely mistaken. Not wrong, just mistaken.

      The decision by Mozilla not to integrate support for the H264 codec is only ideological if you define that term to mean 'respectful of the rule of law'.

      You keep talking about 'support' for the H264 codec. The issue is not support, per se - any 3rd party could do that via a plugin.

      The issue is that Mozilla cannot legally integrate an H264 codec into their code base and remain GPL-compliant.

      This kind of matters because of the way HTML5 removes the technical requirement for some 3rd party plugin to be able to view video content and because of the increasing presence of software running embedded on devices.

      Of course Firefox will be able to play H264 video. That's not the issue. The issue is that the legal framework is prejudiced against Mozilla and all FOSS software that wants to support this codec. The issue is equally that other major players on the Web seem perfectly happy to acquiesce to the promise (not the threat) of patent-driven royalties for all content producers down the road.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    39. Re:Give it up, Mozilla :) by BikeHelmet · · Score: 1

      You make an interesting point. Theora is particularly well suited for high bitrates, so DVDs would actually be a fine use. It's trivial for any modern device to decode theora in hardware - the software just has to exist, and be bundled in the firmware of the device.

      I feel H.264 or a codec like VP8 should win for streaming, simply because of the reduced bitrate. H.264 does exceptionally well at super low bitrates(256-512kbit), where other codecs would turn into a blurry mess. Because of the low bitrate, it's not that CPU/DSP intense.

      On the other hand, H.264 is very hard to decode at very high bitrates. At 25mbit, the quality gain over a codec like Theora probably isn't as significant as the increased decoding difficulty, which would prevent it from decoding at all on most devices.

    40. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      How can you claim that usign Theora "isn't an option"? It's free, it's as good as h.264 and it's already implemented. The only thing that is needed to become widespread is for sites such as youtube to fully implement HTML5 and offer Theora videos. The rest amounts to nothing more than whining.

    41. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      The issue is that Mozilla cannot legally integrate an H264 codec into their code base and remain GPL-compliant.

      Sorry, no, that's just false, legally and technically.

      All Firefox needs to do is integrate with a *generic* video backend. That backend can then provide H.264 support, and Firefox will be legally in the clear. It's just that simple.

      Firefox simply chooses not to do this. They've tried to invent a bunch of technical reasons why they don't want to, but alas, they're weak at best. No, the Firefox devs dug their heels in for ideological reasons early, and continue to dig their heels in because they're stubborn and don't give a crap about their users (as an aside, they also *massively* overestimate the impact they can have on the web, hilariously of the belief that Firefox making a stand will somehow stem the tide of H.264 video on the web... it'd be funny if it weren't so sad).

      The issue is that Mozilla cannot legally integrate an H264 codec into their code base and remain GPL-compliant.

      Good, they shouldn't be doing that in the first place.

    42. Re:Give it up, Mozilla :) by Billly+Gates · · Score: 1

      Screw you. I do not want to use IE and Windows in order to use the internet.

      Call me a commie all you want but I have a moral problem with creating a monopoly by abusing standards. Standards exist to prevent monopolies and encourage competition. H.264 is designed to create a monopoly in order to scew users over with drm and fees and lock people in.

      How can the web be a free platform when you can't develop media rich websites without proprietary $$$$ non free software due to patents and drm. Flash already killed the opportunity for any serious web developers to learn new skills without paying adobe $$$$. Html 5 is designed to open it back up again ... with the exception of h.264.

      Didn't the RIAA/MPAA want spyware on every pc sold? A forced plug in will be perfect.

      Good job Firefox! Keep up the work and with you refusing to support it the less likely webmasters will use h.264 over alternatives.

      if you like h.264 then use it but do not force it on the resut of us.

    43. Re:Give it up, Mozilla :) by twidarkling · · Score: 1

      And since everyone's moving to HD content, that makes it a WONDERFUL choice! Wait, no, that's not right...

      --
      Canada: The US's more awesome sibling.
    44. Re:Give it up, Mozilla :) by Goaway · · Score: 1

      Theora is particularly well suited for high bitrates

      Actually, Theora is bad at exactly that. Or no so much high bitrates as high resolutions, which is often the same thing.

    45. Re:Give it up, Mozilla :) by Goaway · · Score: 1

      If you hadn't noticed, Firefox already plays h.264 just fine. Through Flash.

    46. Re:Give it up, Mozilla :) by Goaway · · Score: 1

      So you do not use Flash, then?

    47. Re:Give it up, Mozilla :) by BikeHelmet · · Score: 1

      Actually, Theora is bad at exactly that. Or no so much high bitrates as high resolutions, which is often the same thing.

      Well then, what is Theora good at? I'm drawing a blank.

    48. Re:Give it up, Mozilla :) by drinkypoo · · Score: 1

      H.264 is open and yet proprietary. The patent holders own H.264. It's not Free, nor is it free, although various entities will pay on your behalf if you are a member of one of several common classes of computer user.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    49. Re:Give it up, Mozilla :) by Goaway · · Score: 1

      It's pretty fast.

    50. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      (as an aside, they also *massively* overestimate the impact they can have on the web, hilariously of the belief that Firefox making a stand will somehow stem the tide of H.264 video on the web... it'd be funny if it weren't so sad)

      I think you massively underestimate the impact Mozilla had and continues to have on the web. You should look at browser user agent strings sometime. IE, Safari, and Chrome and Opera all claim to be Mozilla implementations.

      Ultimately, you're on the losing end of this debate. Open video is where it's at. Google is the biggest video provider on the Internet and Google is all about the open web. In this regard, Mozilla and Google are in perfect alignment:

      http://google-opensource.blogspot.com/2010/04/interesting-times-for-video-on-web.html
      http://googleblog.blogspot.com/2009/12/meaning-of-open.html
      http://www.mercurynews.com/business-headlines/ci_14847976
      http://www.0xdeadbeef.com/weblog/2010/01/html5-video-and-h-264-what-history-tells-us-and-why-were-standing-with-the-web/

      This is how important Internet companies like Mozilla and like Google think. This is why YouTube will move to open video sooner rather than later. Join the 389 million people who have downloaded Firefox 3.6 so far:

      http://www.mozilla.com/en-US/firefox/firefox.html

      Use open video and be happy.

    51. Re:Give it up, Mozilla :) by Civil_Disobedient · · Score: 1

      For example, Flash (something that HTML 5 and the video tag could replace)

      Flash video .

      HTML5 will do nothing to replace embeddable TrueType fonts, vector animation, built-in MP3 and MP4 support, etc., etc., etc.

      You know... the 99% of stuff that Flash does that you failed to mention in your little deceptive aside. Well, deceptive or woefully ignorant.

    52. Re:Give it up, Mozilla :) by shutdown+-p+now · · Score: 1

      That's not Google's view, though. That's just a single guy, who's working independently from Google, but they finance his work. Their official stance with respect to backing H.264 for HTML5 didn't change - they're still opposed to standardizing on Theora.

      And VP8 rumors are just that, rumors - for now. We shall see later. In any case, if it goes ahead as rumored, it would be very different from Theora (which may in fact be why Google opposes standardizing HTML5 on the latter!).

    53. Re:Give it up, Mozilla :) by shutdown+-p+now · · Score: 1

      IE9 ships with it's own h.264 decoder.

      Er, how do you know that? So far all we saw is a "preview", which isn't even a proper browser!

      It's the only way to support h.264 on Vista

      This is rather obviously false. All it takes to support H.264 on Vista is to install an H.264 DirectShow codec.

    54. Re:Give it up, Mozilla :) by Blazewardog · · Score: 1

      It is easy to decode since it doesn't offer as many compression techniques. That is both its benefit and its downfall. It is the same thing that prevents MPEG-4/ASP from being usefull at HD resolutions

    55. Re:Give it up, Mozilla :) by shutdown+-p+now · · Score: 1

      They don't have to use DirectShow in particular, just any extensible framework.

      For example, Opera (10.5+) uses GStreamer on all platforms. On a Unix system, it'll just use the one that is already installed, and all the codecs therein, so adding H.264 support is trivial - you just install GStreamer wrapper for ffmpeg.

      On Windows and OS X, they simply package a private version of GStreamer with Opera itself, and add the baseline plugins (in their case, just Theora and Vorbis) there. It does not conflict with system in any way, nor does it expose any vulnerabilities other than those in the codecs they pick. But it is still proper GStreamer with dynamic loading of codecs - just from a private folder - so it can be extended if user wishes that.

      Or, better yet, use the system framework, but whitelist codecs - and let user edit the whitelist, adding codecs he wants to be supported as needed. This is perfectly implementable with DirectShow (no idea about QuickTime).

    56. Re:Give it up, Mozilla :) by shutdown+-p+now · · Score: 1

      they need to ensure that the DirectShow output works with the layers/svg/smil infrastructure as well as DirectWrite/Direct2D on Windows 7 -- e.g. does having a rotating, scaling video in a smil/svg file work;

      Yup, it's a technical challenge. But don't tell me it's a blocker, as other browsers are already using this approach.

      It's not even a challenge. In both GStreamer and DirectShow, the codec just outputs an image (usually YUV). The browser can scale/rotate/resize it as it sees fit. Yes, those frameworks also offer facilities for hardware-accelerated rendering of those images, but it doesn't have to be used (or it can only be used when image isn't rotated or partially obscured, etc).

      Heck, Opera already does it with GStreamer - cross-platform, and they support arbitrary rotation/translation/scaling of page elements or the entire page, including HTML5 video. You can see for yourself if you download Opera, go to any HTML5 video demo page (you'll need Theora-based ones, sine Opera doesn't come with H.264) - e.g. this will do - and then type the following in URL textbox:

      javascript:void(document.body.style.OTransform='rotate(-45deg)')

    57. Re:Give it up, Mozilla :) by Abcd1234 · · Score: 1

      IE, Safari, and Chrome and Opera all claim to be Mozilla implementations.

      ROFL! Wow, you honestly have absolutely *no idea* how modern web browsers came about, do you?

      Christ, the fact that you think "Mozilla" in a user agent string means they're trying to mimic modern Firefox demonstrates just how laughably ignorant you must be.

      Honestly, that must be one of the funnier things I've read in some time. Well done!

      Ultimately, you're on the losing end of this debate. Open video is where it's at.

      No. It's really not. Theora looks worse, requires more bits, doesn't yet have hardware acceleration (though that may be changing soon, we'll see), streams poorly (though that's Ogg's fault)... it's *only* advantage is on the patent issue, and the content providers have already paid for their licenses, and the users simply don't give a shit.

      Meanwhile, Google, Vimeo, and basically every other major content provider has already standardized on H.264, largely because it's backwards compatible with their existing Flash-based players while also working in the video element.

      No, Theora lost before the race ever began. The only question now, is, will Firefox finally relent before HTML5 really starts to make it big, and Firefox is left in the dust by browsers run by people who aren't blind ideologues with delusions of grandeur.

    58. Re:Give it up, Mozilla :) by Ash-Fox · · Score: 1

      That's not Google's view, though. That's just a single guy, who's working independently from Google, but they finance his work. Their official stance with respect to backing H.264 for HTML5 didn't change - they're still opposed to standardizing on Theora.

      Oh, I remember this guy. See: http://people.xiph.org/~greg/video/ytcompare/comparison.html

      I doubt this person speaks for all of Google too, considering other departments are doing the opposite as shown before.

      --
      Change is certain; progress is not obligatory.
    59. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      At the current state of Dirac, Theora is better than Dirac except at very high bitrates. See http://lwn.net/Articles/326830/ and the current shootout that everybody cites but I'm too lazy to search for.

    60. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      All of you who are so desperate to see H.264 <video> in Firefox, why don't you write a plugin?

    61. Re:Give it up, Mozilla :) by evilviper · · Score: 1

      H.264 is open and yet proprietary

      No. It is not proprietary in any sense of the word. You really need to look up the definition before you speak.

      Theora has more claim to being proprietary, as one single organization defined it and continues to change it however they see fit. That has been expressed as one of the reasons companies refuse to accept Theora... Not that the quality and installed-base issue isn't overwhelmingly paramount, though.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    62. Re:Give it up, Mozilla :) by supssa · · Score: 1

      Sopssa expert of all things! I'm so glad you have weighed in on this issue so informedly as usual! Thanks for the same trolling insight you always have good sir!

      --
      Hatin' on products I don't like and getting modded up talking about tech I totally don't understand like it was 2005!
    63. Re:Give it up, Mozilla :) by BZ · · Score: 1

      > HTML5 will do nothing to replace embeddable TrueType fonts

      No, but CSS fonts do.

      > vector animation

      SVG or canvas depending on whether you want retained mode or immediate. Granted, SVG is a bit of a pain to work with.

      > built-in MP3 and MP4 support,

      This is tougher, since it has the patent issues we're discussing right now, right?

      > etc., etc., etc.

      Details?

      The fact is, the general web standards push right now seems to be in the "make Flash irrelevant" direction.

    64. Re:Give it up, Mozilla :) by Anonymous Coward · · Score: 0

      Mozilla simply *can't* support H.264 using OS-provided codecs because of, like, security and stuff. As if Mozilla packaging it's own multimedia framework is suddenly so much better, and it's much wiser to not take advantage of OS-provided services that are regularly vetted and patched.

      Most of your other points are ok, but this one is not. The OS-provided services you refer to are the components with the worst track record in security. Apple patches an average of six exploits in Quicktime every security update. Microsoft removed DirectShow's third-party codec support in Win7 (it's now Windows Media Framework) because third-party codecs for DirectShow were 99% malware. "Mozilla packaging their own security framework" is infinitely better to them, since they can see the source and patch it, rather rely on two other companies (who also happen to be its chief rivals). Mozilla cannot "regularly vet and patch" Qucktime or Media Framework because they are not open source.

  2. Re:Firefox by sopssa · · Score: 2, Interesting

    I have no idea why Firefox still fights against the giant and loses money and time on it. Great, they got hw-accelerated Theora to one single mobile phone. What about all the televisions, other mobile phones, computers, airplanes, PS3, 360, and everything else under the sun that has H.264 hw supported? It's a lost battle.

    If I were them, I would seriously start concentrating on the next generation of video codecs. It might be closed H.264 for now, but if you want to get an open source product out there, you have to make it technically better, make sure (and contact!) companies to support it in their products, and just do marketing and PR.

    Open source has some advantages, but if it's technically lesser and doesn't work with companies, it's not going to win.

  3. Hardware Accelerated? by Anonymous Coward · · Score: 3, Interesting

    In my mind, hardware accelerated means using fixed-function, special purpose functional blocks in silicon. Saying that using a DSP is hardware acceleration for video codecs is like saying that software is hardware accelerated by the execution units of a CPU.

    1. Re:Hardware Accelerated? by X0563511 · · Score: 4, Informative

      Your mind is wrong.

      Lets look at graphics cards. A DSP is the same "thing" as a GPU is, in that it's a special purpose processing unit (ie, Graphics Processing Unit, Digital Signal Processor...). Rendering with a GPU is a hell of a lot faster than with a general CPU. Likewise, processing digital signals is a hell of a lot faster in a DSP than with a general CPU.

      So, to reiterate: you are wrong.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    2. Re:Hardware Accelerated? by Anonymous Coward · · Score: 0

      So then all the software codecs that use SSE, NEON, and AltiVec are also hardware accelerated? Sweet!

    3. Re:Hardware Accelerated? by X0563511 · · Score: 1

      Yes. Unless you are using some weird definition for Hardware Accelerated, because SSE (and I assume NEON and AltiVec, since I've never heard of them) are hardware-specific accelerations.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    4. Re:Hardware Accelerated? by chill · · Score: 3, Informative

      FYI: NEON is ARM and AltiVec is PPC. They're the other processor equivalents to SSE.

      --
      Learning HOW to think is more important than learning WHAT to think.
    5. Re:Hardware Accelerated? by O'Nazareth · · Score: 3, Informative

      DSP is hardware acceleration for signal processing (this is the name). A video frame is a 2D signal. So yes, this is hardware acceleration.

    6. Re:Hardware Accelerated? by Anonymous Coward · · Score: 0

      OK, fine. My sarcasm was too subtle. Notice how the submission title reads "hardware-accelerated" and the summary reads "DSP accelerated." There IS a difference. The submission title was written specifically to fool people into thinking (if only for long enough to click the link) that someone had designed a synthesizable block for the express purpose of decoding Theora (among others) at minimal power draw. That would be a real game changer. Porting the decode routine to OMAP DSPs really isn't.

    7. Re:Hardware Accelerated? by arose · · Score: 2, Insightful

      Wow, so doing the same thing as H.264 isn't good enough? Now you demand silicon for Theora where H.264 uses DSPs?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    8. Re:Hardware Accelerated? by zippthorne · · Score: 0

      Ahh, but the real game-changer would be the ability to use the *same* DSPs as H.264 in a way that existing devices could take advantage of.

      --
      Can you be Even More Awesome?!
    9. Re:Hardware Accelerated? by Anonymous Coward · · Score: 1, Informative

      This IS using the same DSPs!

      Does no one read TFA?

      The code uses the c64x DSP used by the entire OMAP platform, so it will also not be just Nokia and its N900 that will benefit from this.

    10. Re:Hardware Accelerated? by arose · · Score: 2, Insightful

      Just to add to the other reply... Did you think that mobile devices just have random DSPs included for the purpose of eventual Theora support?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    11. Re:Hardware Accelerated? by TheRaven64 · · Score: 2, Informative

      One of the blobs on the OMAP chip's block diagram is the IVA (Image, Video, Audio) coprocessor. This includes a DSP (the C64x), a DMA engine, and a couple of other features. All of the video CODECs that are hardware accelerated on the OMAP (H.264, RealVideo, and WMV) use the IVA part, and now Theora does too.

      The C64x is found in most of TI's ARM SoCs, being omitted from only the very cheapest. This means that the implementation of Theora there could relatively easily be deployed on any handheld computer or telephone containing a TI OMAP chip, which is a lot of them.

      Unlike some of the earlier DSPs included in this sort of chip, recent OMAPs (maybe older ones; not sure) have an MMU attached to the DSP, so the kernel can restrict the memory that a program using the DSP can use.

      --
      I am TheRaven on Soylent News
    12. Re:Hardware Accelerated? by Joce640k · · Score: 1

      Yep, by this definition *all software* is hardware accelerated, even software running on an emulator (the emulator is hardware accelerated, just not optimized for that instruction set).

      --
      No sig today...
    13. Re:Hardware Accelerated? by Anonymous Coward · · Score: 0

      If the DSP can decode Theora with minimal power draw, and that DSP is already in a lot of mobile hardware, why is it not just as much (if not more) of a game changer?

  4. Battery life? by TheRaven64 · · Score: 4, Interesting

    It's great seeing the benchmarks showing the CPU usage dropping from 99% to 1%, but at the same time the DSP and GPU usage is going up by some unstated amount. It would be really great to see some comparison of how this effects the battery life. Playing MP3s on the C64x can be done in a bit under 15mW, but Theora is a lot more complex and doing the colourspace conversions and compositing on the GPU is going to add a bit too. I'd expect the power usage to be lower than doing it on the CPU, but maybe not by a huge amount.

    Either way, it's great that they can free up the CPU to do other stuff. 0.4% of the ARM core isn't really enough to run the scripts that typically accompany a web page that uses the video tag, 99% almost certainly is.

    --
    I am TheRaven on Soylent News
    1. Re:Battery life? by X0563511 · · Score: 3, Interesting

      Looking at the datasheets for a few TI C64 DSPs, we are looking at supply voltages under 2v and current draws measured in microamps (yes, micro, smaller than milli).

      The power draw for these special-purpose devices is teeeny tiny compared to the other hardware.

      http://www.ti.com/lit/gpn/tms320c6424 (PDF) - Page 127 lists electrical characteristics in the normal operating temperature range.

      More models listed here:
      http://focus.ti.com/paramsearch/docs/parametricsearch.tsp?family=dsp&sectionId=2&tabId=217&familyId=477

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    2. Re:Battery life? by Anonymous Coward · · Score: 1, Informative

      Looking at the datasheets for a few TI C64 DSPs, we are looking at supply voltages under 2v and current draws measured in microamps (yes, micro, smaller than milli).

      The power draw for these special-purpose devices is teeeny tiny compared to the other hardware.

      http://www.ti.com/lit/gpn/tms320c6424 (PDF) - Page 127 lists electrical characteristics in the normal operating temperature range.

      More models listed here:
      http://focus.ti.com/paramsearch/docs/parametricsearch.tsp?family=dsp&sectionId=2&tabId=217&familyId=477

      Supply current is definitely not microamps, with PLL, I/O, and core consumption during encoding you're looking at closer to 1A.

    3. Re:Battery life? by X0563511 · · Score: 1

      Aaah, I see. Though it's more like 0.5A. Still. My gaming desktop only uses like 3A...

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    4. Re:Battery life? by Anonymous Coward · · Score: 0

      Aaah, I see. Though it's more like 0.5A. Still. My gaming desktop only uses like 3A...

      :) 3Amps at 120V? versus .5-1A @ 1.2-2.0V?

    5. Re:Battery life? by X0563511 · · Score: 1

      OK yea. I should stop half-thinking. heh.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    6. Re:Battery life? by Anonymous Coward · · Score: 1, Informative

      OK yea. I should stop half-thinking. heh.

      No worries, to put it in current-independent terms:

      My beagleboard running a custom DVI output app will use 2-3 Watts compared to ~180 watts for my i7 machine at idle!

      Not bad for a nice little board.

    7. Re:Battery life? by X0563511 · · Score: 1

      Not bad at all. That's half or less the wattage most devices use _in_standby_

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  5. Open systems drive innovation by human+spam+filter · · Score: 3, Interesting

    This is a good example how open systems drive innovation. Allowing people to tinker with the device (root access, access to the DSP) attracts hackers, which in this case lead to DSP accelerated Theora video decoding. It's quite fitting that Apple is resisting Theora in HTML 5, mainly because their devices don't have accelerated Theora decoding (this is what I assume). While at the same time the restrictions imposed by Apple make it impossible to develop something like this for their iCrap devices (apart from not having root access, no API for accessing the DSP, it would also violate the developer agreement.. since you need some DSP assembly, which is not an approved language).

    1. Re:Open systems drive innovation by Anonymous Coward · · Score: 1, Interesting

      Apple has so many resources at their disposal that it would be trivial for them to code a hardware-accelerated Theora decoder. (For comparison: one individual hacker made the decoder in TFA.) The reason Apple is against Theora in HTML 5 is that it would lower the barriers to entry for anyone coding a browser, particularly in the mobile market. If we have an internet with Theora, anyone is able to implement that without patent issues. Apple would much rather have a locked-down internet, where no one can code a functional web browser unless they have the money to license H.264.

    2. Re:Open systems drive innovation by hedwards · · Score: 1

      Apple has kind of a tough time there, the way that they keep things stable is by not having people screwing around with the internals and drivers, but in order to do something like this one has to screw around with the internals. Meaning that they've bet on stability and reliability at a cost of having this sort of community involvement. Hard to say whether they'll come out ahead or behind in the long run.

    3. Re:Open systems drive innovation by Anonymous Coward · · Score: 0

      I thought Apple were claiming potential, but currently unknown, patent issues with Theora. I guess h.264 is okay because there can't be any unknown patents that apply to it, can there.

  6. VP8? by Anonymous Coward · · Score: 1, Interesting

    Will this work be adaptable to the VP8 codecs should Google open source them?

  7. Re:Firefox by HeikkiK · · Score: 3, Funny

    We need a backup in the case H.264 patent owners start collecting some money when H.264 is spread everywhere. If I understood right, the current permission to use H.264 freely in free web content is just temporary and ending December 31 2010! Developing and optimizing these codecs take time, so better start working now. In fact we should hurry!

    Also the situation is very similar to using OpenOffice-threat to blackmail discounts for Microsoft Office. So even if you happen to like H.264 more than Theora, this development is a win for you (unless you happen to be H.264 patent owner).

    One phone is a good start. If you carefully read the introduction, it says that C64x DSP is quite common. The optimization just have to be taken into use. N900 just happens to be the most open phone right now so it is a natural first target.

    Also well working and hardware optimized codec brings some pressure to hardware optimize also H.264 for common platforms.

  8. Yes you have no idea by Nicolas+MONNET · · Score: 4, Informative

    They made their point quite clearly.

    They can't embed the codec and remain truly Free software.

    Second, while they could link to platform-provided codecs, it's a support nightmare.

    Third, it would legitimize patented crap.

    1. Re:Yes you have no idea by larry+bagina · · Score: 1, Troll

      Firefox isn't FREE software. Both the name and icon are closed source. If you modify, recompile, and redistribute your own version of the firefox code, you need to give it a different name and a different icon (cf Ice Weasel, Ice Cat).

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    2. Re:Yes you have no idea by someSnarkyBastard · · Score: 5, Informative

      No, the name and icon are not closed-source, they are trademarked. There is a difference between the two. Linux is trademarked by Linus Torvalds, but to claim that makes it closed-source is patently ridiculous. Trademark only means that other parties cannot use your brand to advance their own products without permission, aka diluting your brand. The fact that you can point to Libre derivative forks of Firefox disproves your claim that Firefox is closed-source.

    3. Re:Yes you have no idea by Anonymous Coward · · Score: 0

      How the fuck can a name be "closed source"? What does the source code look like?

    4. Re:Yes you have no idea by Goaway · · Score: 2, Interesting

      You know, Firefox already plays h.264 just fine.

      By using Flash.

      Refusing to support h.264 in HTML5 is not going to stop anyone using h.264, it's going to stop people using HTML5 since they'll just use Flash instead.

      And so, Mozilla loses twice.

    5. Re:Yes you have no idea by drinkypoo · · Score: 1

      The fact that you can point to Libre derivative forks of Firefox disproves your claim that Firefox is closed-source.

      The fact that the GP only said that the name and the icon are closed invalidates your entire comment. Open Source means that you can get the source code, that is it. Free Software means that the software provides the user with certain freedoms, like the freedom to modify and redistribute. You don't have the right to redistribute your changed version as Firefox, therefore it can be argued that it is not Free Software. Nowhere did the GP claim that Firefox's code was not Open Source.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Yes you have no idea by shutdown+-p+now · · Score: 1

      Second, while they could link to platform-provided codecs, it's a support nightmare.

      Others (proprietary, no less) browsers seem to be doing fine with that model - e.g. Opera. What's "nightmarish" about it?

      For codecs that they want to support no matter what (i.e. Theora), they just ship them in the box, and bypass platform services for them. For everything else, let the user make his own choices, mmkay?

      Third, it would legitimize patented crap.

      It's already "legitimized" wide enough that Theora is, frankly, irrelevant in comparison.

    7. Re:Yes you have no idea by hedwards · · Score: 1

      Umm, Flash is exactly why this needs to not happen. Flash isn't well supported on _any_ platform. Even on Windows which is the primary focus it sucks. The problem is that people don't all want to use Windows or Mac, even adding in Linux users you still don't hit everybody.

      If Firefox requires Flash to play h.264, then it's not supported. I can't install flash properly on my FreeBSD install without a lot of shenanigans, even then it doesn't really work very well.

    8. Re:Yes you have no idea by Goaway · · Score: 1

      Yes, Flash is horrible, but it is widely supported. And if you hate it, which you have every reason to, you should be unhappy about the way Mozilla is helping it thrive by refusing to use h.264.

    9. Re:Yes you have no idea by someSnarkyBastard · · Score: 1

      Actually you do have the right to distribute your modified version of Firefox, you just can't call it Firefox I could say the same thing about Linux, if you wanted you could fork your own Linux kernel and modify it to your heart's content, you just can't call it Linux or use a slightly rotund penguin as a mascot. You are still perfectly free to use the code as you wish, you just can't use the IMAGE attached to a particular party's version of the code. That was the difference I was trying to point out.

  9. sopssa, maybe because FIREFOX has constant bugs? by Anonymous Coward · · Score: 0

    sopssa you back the wrong source, see inside

    "But the 3.6.2 update was ALREADY released WELL BEFORE the story was posted (Tuesday March 23, @02:51AM Eastern): https://developer.mozilla.org/devnews/index.php/2010/03/22/firefox-3-6-2-update-now-available-as-free-download/ Firefox 3.6.2 update now available as free download Version 3.6.2 was released THE DAY BEFORE this story even posted! Once again you are caught in your BOLD-FACED LIES, LOL! - by clone53421 (1310749) on Monday April 05, @01:36PM (#31736454) Journal

    Funny how YOU backed up clone53421 above, here on your part, regarding firefox though (lol, when clone's information was STALE & OUT OF DATE alraady too no less):

    http://slashdot.org/comments.pl?sid=1591778&cid=31755996

    AND YET? LMAO:

    FireFox turned up YET ANOTHER SECURITY BUG & right when you shot your big libellous mouth off in that quote above on 04/05/2010 above, taken from here:

    ----

    Mozilla Firefox DOM Node Moving Use-After-Free Vulnerability:

    http://secunia.com/advisories/39175/

    Release Date 2010-04-02
    Last Update 2010-04-06

    ----

    http://slashdot.org/comments.pl?sid=1591778&cid=31755996

    That's where you quote above is from, and, Where Germany advised its peoples to stay away from FireFox 3.6, as they had for IE before that (but, never for Opera).

    (Thus, yet another security bug surfaced in FireFox 3.6.2 in that time frame, yet again, 2x that week it appears (LOL!)).

    sopssa - How stupid do you feel after your backing up that moron clone, sopssa, when he was quoted in error in that rant of his above that opens this posting of mine in reply, and the URL above that shows you backing his stale & out of date information?

    Why?? Because YET ANOTHER SECURITY VULNERABILITY SURFACED THAT DAY OR THE NEXT DAY in FIREFOX, YET AGAIN, lmao...

    "too, Too, TOO EASY!"

    Obviously sopssa, you lost yet again, and backed the wrong poster in clone53421, in such a stupid mistake on hiis part above.

    Obviously, You're too stupid to exist sopssa and it's no small wonder that all you do is post on slashdot all day, as you don't have enough skills or degrees necessary to your name in computing to actually have or hold a job in the sciences of computing.

  10. h.264 use in free web content ends 2015 by tk77 · · Score: 3, Informative

    Please check your facts on the licensing dates, they changed in February.

    http://www.mpegla.com/main/Pages/Media.aspx

    (direct PDF of the press release is here: http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf )

    1. Re:h.264 use in free web content ends 2015 by Jenming · · Score: 2, Interesting

      (DENVER, CO, US – 2 February 2010) – MPEG LA announced today that its AVC Patent Portfolio License will continue not to charge royalties for Internet Video that is free to end users (known as Internet Broadcast AVC Video) during the next License term from January 1, 2011 to December 31, 2015. Products and services other than Internet Broadcast AVC Video continue to be royalty-bearing, and royalties to apply during the next term will be announced before the end of 2010.

      So how about instead of touting a codec thats already outdated use h.264 for now and use the next 5 years to develop a codec that is actually better in some way.

      --
      Morpheus, God of Dreams.
    2. Re:h.264 use in free web content ends 2015 by gmuslera · · Score: 4, Insightful

      If all internet use h.264 now, will still be using, and in far more ways, in 5. You now can move away with not so big effort, in 5 years will be impossible, and most of the internet content will be tied to the will of a single company wanting that you and everyone else in the planet pays them for every device and app that potentially connects to internet. Support it "by now",and will never be pressure to change till will be too late.

      And open source somewhat follows the "shoulders of giants" idea, all have the source, so the experience could be used with another future open source codec if necessary.

    3. Re:h.264 use in free web content ends 2015 by stinerman · · Score: 1

      I don't see how that would matter. MP3s are still ubiquitous, and the format was finalized in 1991. Of course, they weren't used in earnest until the mid-90s, but that's still almost 20 years of them being around.

    4. Re:h.264 use in free web content ends 2015 by Anonymous Coward · · Score: 0

      I'd say it would be a big effort to move away now, if not already impossible. The big players support H.264, in hardware and software.

      If you really think it wouldn't be a big effort to move away from it, then I invite you to start the process and prove me wrong.

      Good luck.

    5. Re:h.264 use in free web content ends 2015 by earthforce_1 · · Score: 1

      Why not? It worked for .gif

      --
      My rights don't need management.
    6. Re:h.264 use in free web content ends 2015 by gmuslera · · Score: 1

      Internet is a bit bigger than it was by the time of gif vs png problem, and there werent so much commercial interest around as now big media companies could have over anything related with video in internet.

    7. Re:h.264 use in free web content ends 2015 by Goaway · · Score: 1

      Everybody is already using h.264. It's pretty much impossible already to get people to change to something else.

      The only way to get people to change to a new codec is to launch a better one. And Theora is not and will never be that.

  11. Re:sopssa, maybe because FIREFOX has constant bugs by HazMat+79 · · Score: 2, Funny

    This is /. so how dare you try to use an argument that may or may not use facts and or logic in it. Plus I ain't clicking on any fancy links just because you want to blow steam off on the internet. Remember winning an argument on the internet is like winning the special olympics, your still retarded after you get that medal.

  12. documenting Theora on http://en.swpat.org by ciaran_o_riordan · · Score: 3, Informative

    I've been documenting the software patents situation for Theora here:

    Adding information about On2's v8 codec would be very welcome.

  13. Is English your 2nd language? by aristotle-dude · · Score: 0, Flamebait

    They made their point quite clearly.

    They can't embed the codec and remain truly Free software.

    Second, while they could link to platform-provided codecs, it's a support nightmare.

    Third, it would legitimize patented crap.

    It is you who has no idea. Software can be free "gratis" but it is property and therefore cannot have "rights and freedoms". People have right and freedoms which can be extended by licenses by the original rights holders.

    They could add H264 support as a plug-in which would have its code stored in an external project which only mozilla staff would have access to. Mozilla could kick off official builds which had the plugin packaged with it while unofficial builds from the community would lack the plugin. Mozilla could also offer the plugin as a separate download either "free" or for a nominal fee to cover licensing costs.

    Linking in support for windows 7 and OS X would be trivial. Linux support is platform issue and not the problem of mozilla if they go this route.

    It is not crap and it is already legitimized. It has support of HD Cameras everywhere, Google, Apple, Microsoft, Blu-ray. Shall I go on? It is a licensed standard and now the defacto standard for video.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
    1. Re:Is English your 2nd language? by Svartalf · · Score: 2, Informative

      Excuse me... Video in HTML5 is supposed to get rid of that plugin thinking in the first place .

      It's not that you can do that- HELL, you can do that NOW.

      The real problem is that while it's implemented and "legitimized", each and every use requires a payment and a sign off against a license you may/may not agree with. Even to provide the content on the Internet will eventually require royalty payments with it. You won't be able to legally implement ANYTHING with video without their permission- and they can withhold it- just witness what's happening with Nokia and Apple right at the moment.

      If you've not caught all of that, perhaps you need to pay closer attention.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    2. Re:Is English your 2nd language? by hairyfeet · · Score: 0, Troll

      Except from what I have seen HTML V5 sucks ass? No offense but it does. I can play full screen SD H.264 flash on this 1.8GHz Sempron that I use as a netbox perfectly. It don't skip, or jerk, everything "just works". If I want to spend a whole $70 and add a AMD 4xxx AGP card I can do full screen 1080p on this same PC, no problem. The last time HTML V5 came up everyone was providing links to HTML V5 sites, so I tried them....yuck. Most had it in a little tiny window and even then it was a slideshow.

      As far as licenses go I just don't see how they could need a license to use whatever codec the user has already. I mean I kinda doubt that all those free MP3 players have licenses for the MP3 codec, do they? If the user doesn't have a codec a simple like to KLite Codec Pack (for Windows) or VLC (on OSX or Linux) would solve the problem without forcing FF to carry a license, wouldn't it? And then we could give the users the choice. Those that wanted to remain RMS style "free" simply didn't have to use it, the rest of us would have nice hardware accelerated FF without hassle.

      So I'm sorry, but until they can get HTML V5 or Theora to play as smooth and easy as H.264 on low power devices like my Sempron I'll pass. I'd say TFA was a step in the right direction, but in a way it ain't. They should have went for the "Big Three"...AMD, Intel, Nvidia, and gotten hardware acceleration on them FIRST. Since AMD and Intel have open specs it should be easier than Nvidia, and once two out of the three were on board Nvidia would have produced one just to have the "us too!" bullet point. Then millions of motherboards and discrete GPUs could come with Theora hardware acceleration out of the box, like they do with H.264 now. And it DOES make a BIG difference, believe me, as a PC builder and repairman I've seen firsthand. Video plays smoother, less chance of stuttering or dropped frames, better multitasking, it just makes the users experience much better, especially with the lower end machines which are VERY popular these days.

      While I wish Theora and HTML V5 the best of luck, unless they get hardware acceleration like yesterday I have a feeling the ship has done sailed. The only real chance IMHO of open video taking off would be now open VP8 codec which if it has made the gains shown in previous versions could be an H.264 killer. If whatever container they use plays as well as VP6 in a flash container we've got a winner here. But considering the frankly incredible mish mash of differing hardware when it comes to mobile it would probably have been better to get the desktops/laptops/nettops on board first, and hopefully get enough momentum going that the hardware manufacturers would jump in and help with Theora support on cells and other mobile devices.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    3. Re:Is English your 2nd language? by Anonymous Coward · · Score: 0

      So you fail at understanding this debate, but merrily pitch a wall of text in anyway. *sigh*

      Let me break this down for you: HTML 5 is a markup language. It has nothing to do with what size of videos, what bitrate, or how well they will play on your system. It allows, among other things, markup designating a video directly in the webpage, much as older versions of HTML support static images. What codecs are used is presently undefined (therefore an HTML5 video element could contain _any_ video, including h.264), and which codecs, libraries etc. get used are up to your browser.

      So contrasting HTML5 vs. h.264 vs. theora is so many kinds of wrong it's stupid. And blaming the standard instead of the browser is, too.

    4. Re:Is English your 2nd language? by hairyfeet · · Score: 0, Flamebait

      And you don't have the balls to post as anything but an Anon coward? Sigh...Can we PLEASE cut the bullshit? This is the SAME circle jerk argument that we get we anyone talks about codecs, to writ the "codec foo is just a container!" bullshit. Frankly I don't give a wet fart what the specs are, what I care about is what is actually being put on the web, mmmkay?

      Just as an avi is NOT a container but an Xvid or Divx video, since that is what 99.9995% of the world has decided it is, so is HTML V5 video Theora. Okay dumbass? Is that really that hard to understand? So keep your circle jerk that does exactly jack and squat, accept that HTML V5 is what the spec says, which I quote "User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format." Which as I pointed out in HTML V5 runs like dogshit on anything but multicores.

      So why don't YOU learn what it is that is actually going on, get your own UserID, and then come back when you have something other than more pedantic circle jerk bullshit to try to look knowledgeable, mmmkay?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    5. Re:Is English your 2nd language? by hairyfeet · · Score: 1

      Waste your points mods, waste them all away...it doesn't change the facts: FACT- HTML V5 IS NOT just a generic container, so sayeth Wikipedia and I quote "User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format."

      FACT- Theora has NO hardware acceleration on most platforms. FACT- Theora runs like hammered shit on anything less than a P4 3.2GHz, which means you just cut out most netbooks/nettops, older PCs, and pretty much every mobile device except the ONE CHIP that Moz has wrote a plugin for. FACT-everyone else that matters, Apple, MSFT, and Google, are running H.264. FACT- Nearly every device sold today, from cheap ass media boxes to cell phones, support H.264. FACT-Every single major motherboard AND discrete GPU comes with H.264 support out of the box.

      If you want to waste mod points going "la la la I can't hear you" knock yourself out, but it don't change reality. The reality is as of this moment HTML V5, which is standardized on Theora according to the spec, is a slow bloated POS that plays videos like the days of dialup unless you are running a serious hog CPU, and frankly it is a shit codec to start with and can BARELY keep up with H.263, and can't hold a candle to H.264. MSFT bet the farm on CPUs always getting bigger and better, and got bit right in the ass with Vista. Are you really gonna be dumb enough to follow MSFT down the road of failure?

      --
      ACs don't waste your time replying, your posts are never seen by me.
  14. Re:Firefox by Damnshock · · Score: 1

    They got hw-accelerated Theora for an OMAP3 SoC. The testing was on a *single* mobile phone, there's a difference ;)

    Anyway, the thing is that theora is as good as H264 or even better at low resolutions and bitrates, that's the reason why they are working on this for mobile phones/devices. Furthermore, having this for a SoC makes it much easier to port to other platforms and will probably work on future evolutions of the SoC as long as they keep the instructions set...

    So, it's reasonable what they are doing ;)

    Damnshock

  15. 4th option by Macka · · Score: 1

    Mozilla and wider Open Source world has three options: (not mutually exclusive)

    You missed a 4th option:

    • Drop Firefox and switch to Chrome

    With support for H.264, Theora, (and hopefully soon VP8) all the bases are covered. This is the option that gets my vote, and now I can relax and enjoy the web as it's meant to be enjoyed, without having to worry or whinge about anything.

    1. Re:4th option by RAMMS+EIN · · Score: 1

      ``Drop Firefox and switch to Chrome''

      You could probably do that, but Chrome is not open source.

      Can you legally do all the things that open source allows you to do _and_ support H.264? And before anyone says "yes, by using the H.264 support from some other component", I'm asking about whichever component contains the support for H.264, not the browser per se.

      --
      Please correct me if I got my facts wrong.
    2. Re:4th option by Endymion · · Score: 2, Informative

      You could probably do that, but Chrome is not open source.

      You say that as if people care about "open source".

      They don't. At all.

      All normal people see (and say) is "the Cool New Video Site is broken in firefox, which obviously must be firefox's fault. So I'll just use Chrome/IE/whatever".

      What all the anti-H264 people are missing is that not supporting H264 will drive people away from Firefox. I fail to see how driving people to the non-free browser is a "win for open source".

      --
      Ce n'est pas une signature automatique.
    3. Re:4th option by Macka · · Score: 1

      And what part of Chrome is not open source? AFAIK Chromium on Linux uses ffmpeg's (open-source) h.264 implementation.

  16. Won't help anyone. by Hurricane78 · · Score: 1

    Because I have yet to see a Theora video site. I say that the price of the additional data traffic costs to get the same quality as H.264 is still more than the license.
    I”m all for an open codec. But everybody knows that unless it”s also a *better* codec, we won”t see it being used. Companies have no interest in paying more and don—t care as much about open source as they should for their own good.
    File sharers don’t care about licenses anyway.
    So we”re left with the tiny subset of private people and very small companies who don”t use it for file sharing.

    And then there’s the point of one actually caring about licensing. Honestly I don’t thing the MPEG will ever sue. Because that would kill off H.264 pretty quickly on the web. They have other interests that are more important than a bit of license money.
    So I will use H.264 even without a license, just as I did with GIF, JPEG, etc, etc, etc.
    Because I think we are stronger, and the can”t ever hurt us. Instead of backing down like a submissive beta-human loser.

    Also, the whole discussion is retarded anyway, because it's utterly idiotic of the Firefox team, to not just link to ffmpeg/DirectShow/CoreVideo, and be done with it. No legal issues for them whatsoever. It’s been said a thousand times already. But they want to ram their thing down our throats no matter what.
    To me, that is no better than if the MPEG group would force us to pay for a license. Except that they don’t (yet).

    Protip: If fighting has made you into what you fought against in the first place, then maybe you should stop, and take a deep breath...

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:Won't help anyone. by Sir_Lewk · · Score: 1

      I have yet to see a Theora video site.

      Really? You haven't been to wikipedia?

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    2. Re:Won't help anyone. by Anonymous Coward · · Score: 0

      Oh yeah, the .0001% of wikipedia articles that have video, and even then it uses a shitty java player so the end user could care less what codec is used.

    3. Re:Won't help anyone. by Anonymous Coward · · Score: 0

      That's a grand total of one site. I've never viewed a video there, but I watch videos on Youtube and Hulu all the time. Guess what codec they use? I'll give you a hint -- it's not Theora.

      Whether you like it or not, this battle is over, and Theora lost (or, more correctly, never had a chance in the first place). Firefox needs to abandon Theora and fully jump on the H.264 bandwagon, or they'll find themselves as irrelevant as Netscape Navigator.

    4. Re:Won't help anyone. by Draek · · Score: 1

      Because I have yet to see a Theora video site.

      Here's one.

      And then theres the point of one actually caring about licensing. Honestly I dont thing the MPEG will ever sue.

      Pity that argument doesn't work with your average corporate lawyer, isn't it?

      So I will use H.264 even without a license, just as I did with GIF, JPEG, etc, etc, etc.
      Because I think we are stronger, and the cant ever hurt us. Instead of backing down like a submissive beta-human loser.

      Ohh, you're so *manly* when you infringe on a big company's patents! Take me, Hurricane, take me hard!

      Don't be so childish and ridiculous. You're content with committing patent infringement and forcing everybody else to either do the same or pay MPEG-LA's extortion fees, and all that why? because you're a lazy fuck. You're not an alpha male, you're not part of La Resistance, you're just a nerd hiding behind anonymity to commit a crime, all to avoid making a stand for your principles.

      If you really weren't a loser, you'd be like the guy in TFA working to make Theora (and other open codecs) better, but instead you bend down and hope you avoid being raped by being lost in the crowd of other losers like yourself. Grow the fuck up, will ya?

      --
      No problem is insoluble in all conceivable circumstances.
    5. Re:Won't help anyone. by hitmark · · Score: 1

      at SD the quality difference is not large. And HD, on a screen maybe 5"-10"? That should be added to the dictionary as nuts.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    6. Re:Won't help anyone. by Anonymous Coward · · Score: 0

      Oh yeah, the .0001% of wikipedia articles that have video, and even then it uses a shitty java player so the end user could care less what codec is used.

      It only uses a shitty Java player when the site is browsed with a shitty browser that doesn't support open video natively. Download a browser that does.

    7. Re:Won't help anyone. by sowth · · Score: 1

      Why would they need to drop Theora to support H.264? The situation isn't either or. They don't support H.264 because they are concerned about potential legalities or licensing costs (not just now, but in the future).

    8. Re:Won't help anyone. by Anonymous Coward · · Score: 0

      sorry, i wouldn't know, even though i use firefox, i haven't stumbled across a wikipedia video in many years.

  17. Re:Firefox by sjames · · Score: 1

    While streaming H.264 is currently royalty free, distributing a codec for it is NOT. So how about it moneybags, would you care to foot the bill for a worldwide unlimited license from MPEG-LA?

    NO? That's what everyone else says, and there's your answer. Mozilla made the choice they did because that's the one they are legally able to make. If you find it that objectionable, perhaps you can help Mozilla get a deal from MPEG-LA?

  18. video acceleration isn't a browser function by YesIAmAScript · · Score: 1

    It's an OS function.

    Firefox should have nothing to do with it. The browser should play whatever the OS can support.

    This is like Firefox saying they now support Dvorak keyboards.

    --
    http://lkml.org/lkml/2005/8/20/95
    1. Re:video acceleration isn't a browser function by hitmark · · Score: 1

      should firefox also only show the image formats supported by the os its running on?

      heck, png got started as gif replacement, as gif had one or more patents attached to it during the early days of the internet.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    2. Re:video acceleration isn't a browser function by allo · · Score: 1

      it does. my firefox is dynamically linked to system libpng i.e..

    3. Re:video acceleration isn't a browser function by hitmark · · Score: 1

      and their source code configure script has the option --with-system-png, so it can be compiled either way.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    4. Re:video acceleration isn't a browser function by Simetrical · · Score: 1

      it does. my firefox is dynamically linked to system libpng i.e..

      It's now also dynamically linked to system libtheora. Same deal. It's not linked to some generic image-rendering library that decides which formats to support. The reason is very simple: image and video in HTML must integrate with the surrounding content. You have to be able to style it with CSS, overlay other content on it, manipulate it in all sorts of complicated ways with script, etc. A generic image or video rendering library is not likely to support all these features, or at least not with the necessary performance. Try overlaying content on Flash and see how well that works (hint: last I checked, it doesn't).

      It's worth pointing out that no browser is using a video backend that they don't control. Firefox is using libtheora, Opera is using GStreamer, Chrome is using ffmpeg, Safari is using QuickTime or something related to that (including on Windows). All of them are either open-source, or controlled by the browser vendor, not the OS (except Safari on OS X and IE on Windows, but only incidentally). You just don't have the flexibility otherwise.

      Disclaimer: I'm not a browser developer, I only hang out with them on standards lists/IRC channels, and this reflects my own poor understanding of things that have been said in my presence.

      --
      MediaWiki developer, Total War Center sysadmin
  19. Re:Firefox by Svartalf · · Score: 5, Informative

    Heh... Damnshock, have you ever worked with a TI SoC?

    The codec was implemented against the C64x+ on a Linux based target on OMAP3.

    Each phone isn't magically different in that respect. In fact, TI provides a platform SDK to use the DSP and everybody using Linux as their base OS is using the same SDK and pathways to get the data in/out of the engine and merely specifying their own get/on get/off points, which are actually submitted to the DSP via the API TI provides to each and every customer of their hardware.

    What does this mean?

    It means that the DSP work done now is available, largely ready for use on:

    Motorola Droid
    Palm Pre
    Palm Pixi
    Nokia N900
    BeagleBoard and derivatives...
    Gumstix Overo Water & Fire
    Open Pandora Handheld
    iPhone GS... ...and anything else using an OMAP3 SoC and Linux.

    Seriously. Done once, able to be used elsewhere as long as you provide consistent interface rules. You might need to adjust the place you get and put the data for the operation, but the algorithm and the vast bulk of the DSP code doesn't change from device to device.

    More to the point, you're going to find that with a bit of tweakage, the work can probably be implemented on OMAP2 platforms such as the Nokia N800/N810 as there's more than enough headroom on the C64x+ to lead me to believe that there's a possibility of doing it on a C55x class DSP- not that someone would go to that trouble unless there was a business case for it.

    Now, this doesn't mean everybody gets "hardware" Theora yet- you still need to implement for at least Blackfin and Snapdragon as well for the bulk of the mobile device space. The main big deal here is that it has now been shown that it CAN be done and done fairly easily.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  20. Re:Firefox by Svartalf · · Score: 1

    and before you remark... iPhone uses a similar DSP edge so my offhand remark about iPhone alongside with "anything else Linux" shouldn't nullify the argument... I added iPhone at the last moment and didn't qualify it this way.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  21. Re:Firefox by RAMMS+EIN · · Score: 1

    ``Open source has some advantages, but if it's technically lesser and doesn't work with companies, it's not going to win.''

    I've emphasized the part that I think is the main point here. It's not about quality. It's not about cost. It's about how businesses work.

    I don't know this for sure, but I would be surprised if H.264 weren't pushed through the normal corporate channels. If you run a company that makes H.264 decoders, you are going to have some of your people meet with people from other companies to try and sell them your decoder. Your salespeople have lunch with representatives from other companies, they play golf with them, and they show them some shiny demos. This is how the game is played: the same way as it is played for many other products.

    Conversely, I would be highly surprised if there was nearly as much time, effort, and money being spent on selling Theora. It doesn't even matter very much how good Theora is relative to H.264, or which will be cheaper to run your website on. It's simply not being sold like H.264 is. Theora is this scary thing: made by a bunch of idealists who believe in freedom and openness.

    Now picture yourself in the position of any of the large stakeholders in this game. Could be one of the desktop OS giants: Microsoft and Apple. Or one of the entities that are in the multimedia business, say Macromedia, MPEG-LA, Sony, or Universal. Or perhaps you are one of the players in the very important field of mobile devices; say, HTC, RIM, or AT&T. Would you rather go with the technology pushed by the nice salesman who treated you to dinner and made you a nice, business to business, the way things have always been done offer? Or would you go with the rebels, who are screaming that you should implement their technology so that they will be in control instead of you?

    --
    Please correct me if I got my facts wrong.
  22. Re:Firefox by Pecisk · · Score: 1

    I have no idea why Firefox still fights against the giant, emm, I mean Microsoft and loses money and time on it. I mean, great, geeks have nice browser on Linux, but what about Windows 98, Windows 2000, Windows XP, Windows Vista, etc. and everything else...emmm there is no anything else that has Internet Explorer support? It's a lost battle.

    If I were them...ok, I can't continue this with straight face.

    I have question - why do you ask? Mozilla can't distribute H.264, period. Not in this, nor in parallel universe (assuming that they have softpatents too). What is left for them? Theora is here and while some of cool guys don't use, I and lot of geeks do. It is functional, it is usable. So why do you care? It's their decision.

    If you don't dig reasons why open source community sometimes do things they do - fine. If it won't succeed in overtaking H.264 - fine. But you have to think about that there never be one, holy video format. That there will be multiple competitive ones. Theora suits very good for distributing content where you need to avoid to touch softpatents (ok, some people insist that there should be some threats but it's not in the open like MPEG-4, which has special agency who collects royality). H.264 is and probably will be used for distributing lot of commercial videos where distributor already paid royalties. There comes Dirac.

    And in the end - open source has always been some kind of underdog, so fighting instead of accepting defeat is in our blood.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
  23. Re:Firefox by westlake · · Score: 1

    I have no idea why Firefox still fights against the giant and loses money and time on it. Great, they got hw-accelerated Theora to one single mobile phone. What about all the televisions, other mobile phones, computers, airplanes, PS3, 360, and everything else under the sun that has H.264 hw supported? It's a lost battle.

    The number of licensees for AVC/H.264 has passed the 800 mark.

    They include - for all practical purposes - every significant player in consumer tech, video production and video distribution in the world.

    You could begin, if you like, with

  24. Re:Firefox by BikeHelmet · · Score: 1

    One big thing getting in the way of Theora is the lack of easy encoders.

    Have you seen what they call easy? Two lines of cryptic text commands - commands that change from version to version, and aren't listed in the documentation.

    With H.264, you can pick up a GUI for free, drag a slider to "Maximum", and wait 2-3 hours. Then you have a wondrous quality video, ready to be streamed, and hardware accelerated on a lot of platforms. There's even websites that will generate all the code for you, so plunking it in your own website is easy, even for the average nitwit that barely knows HTML.

    If you haven't got technical superiority, and you haven't got ease of use, what have you got that's going to win people over?

  25. Good thing I still have it in my basement by paradigm82 · · Score: 3, Funny

    I knew it would some day be possible to have full-HD on my old C64 :-)

  26. Re:Firefox by Anonymous Coward · · Score: 0

    One big thing getting in the way of Theora is the lack of easy encoders.

    http://www.mirovideoconverter.com/

    Here's the user manual:

    1. Drag file to the drop area.
    2. Click the 'Convert!' button.
    3. Enjoy open video in Firefox, Opera, and Chrome.

    Doesn't seem too hard.

  27. Re:Firefox by Goaway · · Score: 1

    Anyway, the thing is that theora is as good as H264 or even better at low resolutions and bitrates,

    This is not actually true. h.264 is significantly better, including at low resolution and bitrates.

    (Theora loses a little bit less at low resolutions, but this is mainly because Theora is so bad at high-resolution video.)

  28. Re:Firefox by BikeHelmet · · Score: 1

    Well, you're right - it certainly is easy!

    But it doesn't offer any options for bitrate or quality. It's a bit like taking a screenshot and saving it as a .BMP with MS Paint.

    When you upload that to a website, people will shout at you for not compressing it or picking a better format.

  29. It's already good enough without acceleration by pslam · · Score: 1

    This keeps getting brought up, and people keep regurgitating the same bad information. Here's the facts:

    • Most smartphones sold in the last 2 years will manage QVGA (320x240x25fps) Theora in software-only, no problem.
    • High-end smartphones (3GS, Nexus, etc) will manage VGA (640x480) Theora, with a bit of help from dedicated YUV to RGB conversion.
    • 720p and high bitrate Theora streams need hardware acceleration on even the fastest smartphones. Do you really care if your mobile phone is only playing back in 480p?
    • Theora is about 10-20% less quality for same bandwidth. There's a lot of really bad comparisons out there, the most popular of which make mistakes such as comparing streams even an iPhone 3GS can't play (H.264 in stupidly high profiles). For normal usage, 10-20% less quality is perfectly fine. Again, do you really care about that 10-20% on your mobile phone?
    • The power consumption difference between pure software and hardware accelerated implementations is small. There's other big power users such as the radio and the backlight. Don't get me wrong: it's worth doing, but people shouldn't view the (guesstimate) 20% difference in battery time as a deal-breaker. Again, hyperbole turns this into 'totally unusable' in some people's minds.

    It's Slashdot hyperbole and trolling again. I know I fall into that trap myself, but being slightly behind the best does not translate to totally useless. On the contrary: being a format that can potentially be used universally by any platform is a HUGE advantage that more than outweighs the slight difference in quality.

    1. Re:It's already good enough without acceleration by shutdown+-p+now · · Score: 1

      Again, do you really care about that 10-20% on your mobile phone?

      Well, yes. I have 3G with a 3Gb monthly cap (and, around here, it's not the worst plan by far). When it comes to something that is measured in dozens of megabytes, 20% is definitely a big deal.

  30. Re:Firefox by TarMil · · Score: 1

    Great, they got hw-accelerated Theora to one single mobile phone.

    From TFA: "This SoC (System on Chip) is best known as being the base behind Nokia’s N series of mobiles (including the N900), the Motorola Droid, Palm Pre, and the Beagle Board." That's slightly more than a single mobile phone.

  31. soppsa, You only answer to others reading now by Anonymous Coward · · Score: 0

    I read what you wrote (as well as your other identity here in clone53421), so much for 'real accounts' (because yours and clone53421 are obviously the same person trying to play 'clever' here, and your days of fooling others using alternate accounts is done here now, sopssa). You and your alter ego clone53421 couldn't prove firefox was faster than opera, so you tried to use a technicality (where timonthy the article poster here put up that firefox 3.6.2 would not release until later this month, but, timothy never updated his news post here http://news.slashdot.org/story/10/03/23/0415208/Germany-Warns-Against-Using-Firefox with this quote from timothy's news post "Note: the warning (from the Federal Office for Information Security) is provisional, and should be rendered moot by the release later this month of 3.6.2.") to get the better of the person you're replying to because of timothy's error in posting false or stale news (or just incorrect news), in your implying that firefox is more secure than Opera is. Strangely, before that other person apk could reply, the post and news article was shut. Why? Because firefox showed yet another security error right when that article was put up about firefox 3.6, which forced an early patch to firefox 3.6.2, which again showed yet another security vulnerability (3 in 1 week or thereabouts? Please!) - http://secunia.com/advisories/39175/ , and right when clone53421 was libelling the ac apk and raving that firefox 3.6.2 was secure and that Germany never said not to avoid using firefox, when they did, clearly, as they did about ie. Germany never did so for Opera though. That new error being used by the ac apk would clearly have made you, sopssa, and your obvious alternate account in clone53421 in error (clone is obviously your alter ego here that you use to mod yourself up with is more like it and we all know that goes on here from scum like yourself and others) wrong on that account, yet again, and simply because the DOM error in firefox was a serious security vulnerability, and you knew it, which would have thrown your attempts to make it seem as if firefox is as secure and free of security vulnerabilities as opera is, and it's clearly not. Awfully strange how that article closed 2 weeks before it should have, eh? Not.

  32. sopssa is clone53421 here too obviously by Anonymous Coward · · Score: 0

    I read what you wrote (as well as your other identity here in clone53421), so much for 'real accounts' (because yours and clone53421 are obviously the same person trying to play 'clever' here, and your days of fooling others using alternate accounts is done here now, sopssa). You and your alter ego clone53421 couldn't prove firefox was faster than opera, so you tried to use a technicality (where timonthy the article poster here put up that firefox 3.6.2 would not release until later this month, but, timothy never updated his news post here http://news.slashdot.org/story/10/03/23/0415208/Germany-Warns-Against-Using-Firefox with this quote from timothy's news post "Note: the warning (from the Federal Office for Information Security) is provisional, and should be rendered moot by the release later this month of 3.6.2.") to get the better of the person you're replying to because of timothy's error in posting false or stale news (or just incorrect news), in your implying that firefox is more secure than Opera is. Strangely, before that other person apk could reply, the post and news article was shut. Why? Because firefox showed yet another security error right when that article was put up about firefox 3.6, which forced an early patch to firefox 3.6.2, which again showed yet another security vulnerability (3 in 1 week or thereabouts? Please!) - http://secunia.com/advisories/39175/ , and right when clone53421 was libelling the ac apk and raving that firefox 3.6.2 was secure and that Germany never said not to avoid using firefox, when they did, clearly, as they did about ie. Germany never did so for Opera though. That new error being used by the ac apk would clearly have made you, sopssa, and your obvious alternate account in clone53421 in error (clone is obviously your alter ego here that you use to mod yourself up with is more like it and we all know that goes on here from scum like yourself and others) wrong on that account, yet again, and simply because the DOM error in firefox was a serious security vulnerability, and you knew it, which would have thrown your attempts to make it seem as if firefox is as secure and free of security vulnerabilities as opera is, and it's clearly not. Awfully strange how that article closed 2 weeks before it should have, eh? Not.

  33. It's logical: FF 3.6, 3.6.2, & 3.6.3 had 3 bug by Anonymous Coward · · Score: 0

    3 bugs in less than 1 month's time no less, which made FF issue 3.6.2, to fix FF 3.6...

    Additionally, then, during the 'debate' where clone53421 was calling me all kinds of names & libelling me too, where sopssa here showed up doing the same? FF had to issue 3.6.3 as well, right during that debate (URL below) - so much for clone53421/sopssa's b.s., that Opera's not more secure vs. known security vulnerabilities, than FF has shown itself to be.

    Well... time to put those "2" in clone53421 & sopssa (same person, diff. logon accounts, I have seen this & CAUGHT others in that here, before here - imo, they're SCUM & online "neocheaters" use that little "trick" online in forums, ALL THE TIME (very easy to catch too)) away now.

    (AND, despite the moderators here closing that thread 2 weeks earlier than usual -> http://news.slashdot.org/story/10/03/23/0415208/Germany-Warns-Against-Using-Firefox )

    I suspect because the mods here are "FF fanboys" as much as they *NIX zealots - read on:

    ----

    "This is /. so how dare you try to use an argument that may or may not use facts and or logic in it." - by HazMat 79 (1481233) on Saturday April 17, @09:58AM (#31881310)

    Yes, how "dare" one show what is stated in my subject-line above - 3 bugs in Firefox in less than 1 month's time, which CLEARLY illustrates that that sopssa (alias clone 53421, his alternate account he uses to mod up his own posts) is "backing the wrong team" & via nefarious means no less as well, & that Firefox has less vulnerabilities than Opera does? I think/KNOW not.

    Firefox will turn up more of these because it is used more, as a reason for it, perhaps more than anything else (not that FF's coding team doesn't do its job, they do, but they are more 'scrutinized' because FF's more used - this same case applies to the "Windows vs. *NIX" debates that go on here + elsewhere online also).

    In fact, on that note ('security-by-obscurity'), and on WEB BROWSERS, specifically? Well, this ought to put the final touch on THAT much, from a "hacker/cracker" via the "pwntoown" contest & his statements on that much also:

    ----

    http://www.theregister.co.uk/2010/03/25/pwn2own_2010_day_one/

    "The problem Microsoft has is they have a big market share, said Vreugdenhil, the hacker who attacked IE. "I use Opera, but that's basically because it has a tiny market share and as far as I know, nobody is really interested in creating a drive-by download for opera. The web at the moment is pretty scary, actually."

    ----

    Nuff said, on the subject of which browser even the "hacker/cracker/security researcher types" use, & why (security-by-obscurity, @ THE VERY LEAST)...

    ----

    "Plus I ain't clicking on any fancy links just because you want to blow steam off on the internet." - by HazMat 79 (1481233) on Saturday April 17, @09:58AM (#31881310)

    Then don't: I'll just post the data involved right here for you to read is all:

    ----

    Mozilla Firefox DOM Node Moving Use-After-Free Vulnerability:

    http://secunia.com/advisories/39175/

    Mozilla Firefox DOM Node Moving Use-After-Free VulnerabilitySecunia Advisory
    Release Date 2010-04-02
    Last Update 2010-04-06

    (Which is clearly YET ANOTHER SECURITY VULNERABILITY FOUND IN FIREFOX, during the 03/23/2010 - 04/05/2010 run time of the article's posting here on /., before the mods "strangely closed it early" (not), & where Germany warned its peoples to STAY AWAY FROM FIREFOX (as they did with IE before it no less), but... Germany's NEVER done the same to Opera.)

    ----

    "Remember winning an argument on

  34. Re:Firefox by vshade · · Score: 1

    The iPhone 3Gs uses a samsung SoC not an OMAP3

  35. An "effete mod down" vs. FACTS? LMAO, good luck! by Anonymous Coward · · Score: 0

    LMAO, per my subject-line above? ALL YOU HAVE ARE YOUR EFFETE MOD DOWNSm vs. easily verified facts!

    (Which sopssa issues via alternate logon registered accounts here. Sopssa - do you think you're fooling anyone w/ that little trick?).

    It's obvious you are also clone53421, because of your showing up SO DEEP into a debate he & I were having (where clone53421 was libelling myself no less, & tossing a fit calling me all sorts of names too, the SURE SIGN OF DEFEAT IN DEBATE no less is that type of frustration) that you just "gave yourself away" clearly.

    So, top FF's being warned against by GERMANY, for bugs in FF 3.6, & then again in 3.62 + YET AGAIN issuing 3.6.3 right away in the SAME WEEK NO LESS?? Please...

    3 bugs in less than 1 month's time no less, which made FF issue 3.6.3, then 3.6.2 before it, to fix FF 3.6... those are far more factual than your mod downs as "troll", by all means!

    So much for clone53421/sopssa's b.s., that Opera's not more secure vs. known security vulnerabilities, than FF has shown itself to be.

    Well... time to put those "2" in clone53421 & sopssa (same person, diff. logon accounts, I have seen this & CAUGHT others in that here, before here - imo, they're SCUM & online "neocheaters" use that little "trick" online in forums, ALL THE TIME (very easy to catch too)) away now.

    (AND, despite the moderators here closing that thread 2 weeks earlier than usual -> http://news.slashdot.org/story/10/03/23/0415208/Germany-Warns-Against-Using-Firefox [slashdot.org] )

    3 bugs in Firefox in less than 1 month's time, which CLEARLY illustrates that that sopssa (alias clone 53421, his alternate account he uses to mod up his own posts) is "backing the wrong team" & via nefarious means no less as well, & that Firefox has less vulnerabilities than Opera does? I think/KNOW not.

    Firefox will turn up more of these because it is used more, as a reason for it, perhaps more than anything else (not that FF's coding team doesn't do its job, they do, but they are more 'scrutinized' because FF's more used - this same case applies to the "Windows vs. *NIX" debates that go on here + elsewhere online also).

    In fact, on that note ('security-by-obscurity'), and on WEB BROWSERS, specifically? Well, this ought to put the final touch on THAT much, from a "hacker/cracker" via the "pwntoown" contest & his statements on that much also:

    ----

    http://www.theregister.co.uk/2010/03/25/pwn2own_2010_day_one/ [theregister.co.uk]

    "The problem Microsoft has is they have a big market share, said Vreugdenhil, the hacker who attacked IE. "I use Opera, but that's basically because it has a tiny market share and as far as I know, nobody is really interested in creating a drive-by download for opera. The web at the moment is pretty scary, actually."

    ----

    Nuff said, on the subject of which browser even the "hacker/cracker/security researcher types" use, & why (security-by-obscurity, @ THE VERY LEAST)...

    In fact, as to the ISSUANCE OF ANOTHER SECURITY PATCH FOR FireFox?

    Well, I'll just post the data involved right here for you to read is all:

    ----

    Mozilla Firefox DOM Node Moving Use-After-Free Vulnerability:

    http://secunia.com/advisories/39175/ [secunia.com]

    Mozilla Firefox DOM Node Moving Use-After-Free VulnerabilitySecunia Advisory
    Release Date 2010-04-02
    Last Update 2010-04-06

    (Which is clearly YET ANOTHER SECURITY VULNERABILITY FOUND IN FIREFOX, during the 03/23/2010 - 04/05/2010 run time of the article's posting here on /., in regards to GERMANY warning vs. FF usage... which is before the mods "strangely closed it early" (not), & again - it was where Germany warned its peoples to STAY AWAY FROM

  36. You're the one modded down as troll sopssa by Anonymous Coward · · Score: 0

    Sopssa (or, should I say clone53421)? Not only were you modded down as a troll, but you had your butt handed to you (both of "you", in sopssa and your alternate logon account here you use to mod yourself up with, in clone52321).

    All you have is your b.s., and that was disproven easily here:

    Hilariously, while that debate was raging 03/23/2010 thru 04/05/2010?

    Heh, FireFox had to issue 3.6.2, & a day later on 04/06/2010, they had to issue 3.6.3 right after... why? SECURITY BUGS!

    (Then, rather "oddly"? LOL, the post was closed WAY EARLY here on that topic no less -> http://news.slashdot.org/story/10/03/23/0415208/Germany-Warns-Against-Using-Firefox and VERY EARLY (03/23/2010 to 04/05/2010)... "gee, I wonder why?" (not -> http://secunia.com/advisories/39175/ where the FIREFOX DOM ISSUE WAS FINALLY RELEASED PUBLICLY, & caused FF 3.6.3 to issue, in the SAME MONTH, 3 security bugs... ))

    No, I'd rethink your "transparent strategems" of effete mod downs and posts closing early and your use of multiple logon id's here only backfired on you, sopssa.

    Please: Don't give advice to others! Just because you're fool enough to be a "registered wannabe" here, doesn't mean I have to be, so you can troll me all the more easily? No thanks!

    After all - you're the one who started trolling me, and you messed up badly because not only was FireFox 3.6 recommended against by the German Gov't., as was IE (Opera never has had the "dubious honor" mind you), but you libelled the AC APK also (the sure sign of defeat in debate).

    APK

    P.S.=> The next time "you & yours" even TRY to troll me, sopssa? This will all be put out as to your "motivations why" (your 'geek angst' @ screwing up royally, lol)... now, "eat your words", the bitter taste of defeat for your trolling (how do they taste I wonder, lol?)... apk

    1. Re:You're the one modded down as troll sopssa by sopssa · · Score: 0, Troll

      APK,

      I remember once discussing with you on actual things. You know I'm a Opera user and think FF sucks. No, I am not clone53421. I've also seen your mindless threads and how you have trolled a single article for the past 6 years.

      You need to get help.

  37. Re:Firefox by Anonymous Coward · · Score: 0

    I'm sure Mozilla could afford the licensing to distribute h.264, the issue is that the licensing doesn't cover re-distribution which is something that Mozilla cares about. Since h.264 isn't established as the codec for HTML5 video and considering Firefox has a significant browser market share, it is certainly worth them holding out on this one. I'm not sure there is much chance of Theora displacing h.264 (though this news might change things), but it could hold back h.264 enough to give the VP8 codec that Google is rumoured to be releasing under an open licence a chance at doing so.

  38. Funny you responded so deep in a post (not) by Anonymous Coward · · Score: 0

    http://slashdot.org/comments.pl?sid=1591778&cid=31755996 which was so far down, there is almost no way you could have come upon it. Yet "oddly enough" (not), you did "suddenly show up" to try to cut down your betters. Who are you trying to fool here? I read that exchange, and the ac apk has done more than yourself that was noted well in respectable publications and trade show contests like Microsoft Tech Ed, in this art and science, and certainly more than clone53421 has or ever will. I think this is the part that made clone53421 "pop" and start libelling apk along with name calling. Truth hurts is why.

    Now also, from the data you yourself posted on Windows IT Pro, the ac APK proved his point in that Windows IT Pro article: That memory manager programs do indeed help on Exchange Servers (and other applications also) by recovering them when they stall due to memory fragmentation, and he also showed Dr. Mark Russinovich, just before that article was made no less, how to correct errors in his pagedefrag.exe program, due to M.R.'s hardcodes of paths to files (eventlogs and registry hives), and that's a "native mode" NT based OS app too. APK's closing comments on it, however, sealed it, because he stated VISTA would flop, and it did, due largely to problems in attempting to make Windows like UNIX's are, in memory mgt. and other areas (file copies & more that dealt in memory use). He proved correct over time, and, to the point that Microsoft had to end up redoing portions of how they used memory in fact.

    You tried to cut him down, and this is your "just reward" is all sopssa: Humiliation. I'd reconsider whom you try to "backup" or "put down" next time, sopssa. You lost by backing the wrong team in clone53421 the libeller.

    Clone53421, your obvious alter-ego alternate logon registered account here? He (you) apparently couldn't stand the fact that Firefox showed yet another error, beyond 3.6, also beyond 3.6.2 (which issued during that debate no less to cover up why Germans said to avoid Firefox, as they did IE before too), and lastly issuing 3.6.3 during that timeframe of that article which was (03/23/2010 through 04/05/2010, when it "suddenly was closed" and VERY early too for a slashdot news post, odd that eh? Not!), which is when the DOM error in Firefox showed up, the last day that article stayed open for comment (very early close too).

    That only served in proving Firefox is more prone to security vulnerabilities by far versus Opera (which has a smaller history of security vulnerabilities typically, and Opera's also been proven faster on all levels on webbrowsers, from parsing HTML to javascript processing & usually in the lead, over time on both areas).

  39. You need the help, & here is why by Anonymous Coward · · Score: 0

    " I've also seen your mindless threads and how you have trolled a single article for the past 6 years." - by sopssa (1498795) * on Sunday April 18, @02:46PM (#31888872)

    I only responded to others, and CLEANLY defeated them, using verifiable facts from the likes of Microsoft no less. From the data you yourself posted on Windows IT Pro? LMAO, ok:

    There, I proved that memory manager programs do indeed help on Exchange Servers (and other applications also) by recovering them when they stall due to memory fragmentation, & via DOCUMENTED FACTS FROM MICROSOFT ITSELF - once I put that out?

    LMAO - All the morons from arstechnica (Jay Little & Jeremy Reimer + Jarrett DeAngelis, a doctoral student those 2 brought in to "try to get the best of me", lol, so much for that -> ) had to either leave, or just eat their words (Jarrett DeAngelis, posts around here as starkruzr too as he did there at Windows IT Pro).

    In fact, Reimer's libel ended his "articles" being shown at arstechnica, because I exposed him as a done nothing & no CSC or CIS degrees (not even a cert) or years-to-decades of professional "hands on experience in the trenches" in this art & science of computing.

    Jay Little (a 3rd rate VB coder Reimer first brought there to try to "get the best of me" - because he cannot himself, not enough technical know-how is why in Reimer, so he uses Lackeys) failed hugely!

    LOL, Jay Little literally stated, verbatim:

    "I am an expert on Exchange server"...

    Sure he is/was - NOT! Not when I proved that MEMORY OPTIMIZERS can restart STALLED exchange servers!

    Then? Jay Little ran...

    Albeit, after he chased me to NTCompatible.com, to try to harass me there and track posts I did to try to "cut them down", & LMAO, yet again Jay Little only got himself kicked from there (as he has @ Channel 9 on Microsoft too) messing up on ramdisks (and windows crash code definitions).

    Jay Little then got websites of his removed in their ENTIRETY at CrystalTech.com, and petitiononline.com (where in the latter he made death threats directed MY way no less). Talk about "geek angst". Reimer, like Little, had portions of his website removed for libelling me as well.

    It seems that LIBEL is the "last resort" of the defeated online... and they only end up paying for it.

    APK

    P.S.=> IF you're going to try to "cut me down"? At least tell the truth of what happened, sopssa... otherwise? You'll look like a fool, AGAIN... pretty simple! apk

  40. Calling me "mindless"? Ok, done better than this?? by Anonymous Coward · · Score: 0

    "I've also seen your mindless threads" - by sopssa (1498795) * on Sunday April 18, @02:46PM (#31888872)

    Calling me mindless now (more name tossing), ok: Show me, show us all reading, that you've done more in this art & science than I have (which *might* start to earn you the right of stating I am "mindless"):

    "My Name is Ozymandias: King of Kings - Look upon my works, ye mighty, & DESPAIR..."

    ----

    Windows NT Magazine (now Windows IT Pro) April 1997 "BACK OFFICE PERFORMANCE" issue, page 61

    (&, for work done for EEC Systems/SuperSpeed.com on PAID CONTRACT (writing portions of their SuperCache program increasing its performance by up to 40% via my work) albeit, for their SuperDisk & HOW TO APPLY IT, took them to a finalist position @ MS Tech Ed, two years in a row 2000-2002, in its HARDEST CATEGORY: SQLServer Performance Enhancement).

    WINDOWS MAGAZINE, 1997, "Top Freeware & Shareware of the Year" issue page 210, #1/first entry in fact (my work is there)

    PC-WELT FEB 1998 - page 84, again, my work is featured there

    WINDOWS MAGAZINE, WINTER 1998 - page 92, insert section, MUST HAVE WARES, my work is again, there

    PC-WELT FEB 1999 - page 83, again, my work is featured there

    CHIP Magazine 7/99 - page 100, my work is there

    GERMAN PC BOOK, Data Becker publisher "PC Aufrusten und Repairen" 2000, where my work is contained in it

    HOT SHAREWARE Numero 46 issue, pg. 54 (PC ware mag from Spain), 2001 my work is there, first one featured, yet again!

    Also, a British PC Mag in 2002 for many utilities I wrote, saw it @ BORDERS BOOKS but didn't buy it... by that point, I had moved onto other areas in this field besides coding only...

    Lastly, being paid for an article that made me money over @ PCPitstop in 2008 for writing up a guide that has people showing NO VIRUSES/SPYWARES & other screwups, via following its point, such as THRONKA sees here -> http://www.xtremepccentral.com/forums/showthread.php?s=ee926d913b81bf6d63c3c7372fd2a24c&t=28430&page=3

    ----

    What do I have to say about that much above? I can't say it any better, than this was stated already (from the greatest book of all time, the "tech manual for life" imo):

    "But by the grace of God I am what I am: and his grace which was bestowed upon me was not in vain; but I labored more abundantly than they all: yet not I, but the grace of God which was with me." - Corinthians Chapter 10, Verse 10

    (And, because I got LUCKY to have been exposed to some really GREAT classmates, professors, & colleagues on the job over time as well)

    APK

    P.S.=> Additionally, vs. what you said here, in your starting of trolling of myself -> http://slashdot.org/comments.pl?sid=1591778&cid=31755996

    (Where you noted the MEMORY OPTIMIZATION HOAX by Dr. Mark Russinovich (now of Microsoft, & a former "colleague" of mine as we both worked for Sunbelt in the mid to late 1990s no less, who actually THANKED ME via email, for showing him that he HARDCODED (rookie error no less, from a PHD) paths to registry hives and event logs in his pagedefrag.exe app)) ?

    You had better take a peek @ what REALLY occurred there @ Windows IT Pro:

    http://slashdot.org/comments.pl?sid=1621832&cid=31889042

    (So, sopssa: How does it taste, eating YOUR OWN WORDS, troll? "The bitter taste of defeat"?? You deserve it, for trying to make me look poorly here, and being way, Way, WAY OFF on your part, as per usual!)... apk

  41. Re:Firefox by centuren · · Score: 1

    I have no idea why Firefox still fights against the giant and loses money and time on it.

    I think it's great, completely aside from the merits of any video codec or open vs proprietary. I'm just happy to read about software makers standing behind their solution and pushing to make it work. A lot of Slashdotters rightly pointed out hardware support as a major issue for Mozilla's Theora support, and Mozilla seems to be working on it. Obviously, this is a small step against a massive obstacle, that should go without saying (but I'm not actually new here). I think it's great precisely because it would be so much easier for Mozilla to take the H.264 path of least resistance.

    Everything to do with the web is becoming more and more... convergent. The Internet doesn't crumble to a halt if browsers don't all work the same; we still got by when some sites built their layouts with divs, and others with layers. I'd much rather see smart people still working to develop different implementations of things then reach the point where everyone gets behind whatever manages to be the entrenched giant.

    It's a lost battle.... Open source has some advantages, but if it's technically lesser and doesn't work with companies, it's not going to win.

    That could be said now and in the past about so many things that didn't give up and go away, and yet have users. You can still buy Ogg portable media players, because even though they've gone from ugly to pricey, they've always found a customer base. I've read comments that lament that pushing this issue could be the death of Firefox, but they will find a user base (not everyone picks a browser on the ability to stream videos). Opera is still around, thanks to its loyal users, and it's not even open source.

    As good as it was to see so many friends and family members shift from IE5 & 6 to Firefox, I don't think there's any danger of those people reverting to IE6. I don't mind if they switch to Chrome or Opera or Safari, so long as it does the job well enough. Mozilla (or any other company/project) fighting the uphill battle and supporting what it thinks is best isn't something I ever want to see stop, particularly with the Internet. The strength of the "web development platform" is in full bloom, and with it seems to come an assumption that it's vital for all browsers to always go in a direction that supports and strengthens the "web platform" concept.

    Well, I work in web development, and I admit it's definitely nicer when browsers are more consistent at handling the same code the same way. Nicer, meaning, we can officially support more browsers. IMHO, that luxury isn't worth moving into an age where browsers all emphasise conformity rather than developing what makes them unique in their vision.

  42. Re:Calling me "mindless"? Ok, done better than thi by sopssa · · Score: 0, Troll

    Why do you paste this list of where your software have been included at? Sure, good for you and I'm happy for you. But it doesn't back your claims one bit. I'm quite certain many of us here on slashdot have an awesome (in a nerdy way) history. If you want to expand that outside nerdy stuff, I'm quite sure it's even more awesome. Random fact: When I was 14 I slided down a snowy hill, saw a girl I liked and my friend told me to go for it and hug her. We dated for the next 3 years. But what does that have to do with the conversation?

    I'm all up for a good debate (do you see how I love it here on slashdot?), but you make no good arguments by assaulting people or telling them they are someone else like you did with me and clone53421. You also do not win anything by claiming you "won" or "beat" someone, or by having multiple personalities and posting under them backing up each other - while by the style of text it's clear it's you.

    Make an account, start providing some real information, debating or talk and discuss about real things.

    You initially assaulted me about Firefox. Just so you know, like you, I am an Opera user.

  43. You called him mindless, he showed otherwise by Anonymous Coward · · Score: 0

    Why do you paste this list of where your software have been included at?

    You called him mindless is why, and since you did, he only asked if you have done more or better things, yourself, than he could show in this science of computing. His statement elicited enough of a reaction (after you said you would not speak to he also earlier) to you after you called him mindless that you needed to defend yourself.

    Albeit, you only did so, with an evasion of his questions (and that's all you had in response when asked if you could show you did more than he has that was noted well by others in this science in written publications, commercially sold software, and in large technical competitions also).

    you make no good arguments by assaulting people or telling them they are someone else like you did with me and clone53421

    You called him mindless. He showed otherwise. Clone53421 called him a lot worse and kept it up and not only made large mistakes in doing so but was driven to the point of name calling and libel (and clone53421's also ultimately been shown as being incorrect too, because firefox did show a new security vulnerability, 3rd that month no less).

    I also found it rather odd that thread closed in less than 2 weeks too, when Germany warned their people to stay away from firefox and before that internet explorer. That never did happen for Opera, and Opera is proven faster by far in many legitimate analysis he used in the other post where that debate occurred (and you also came in very late there, starting up with the ac apk here).

    You get what you got for that type of behavior in calling the ac apk mindless as you did. What you got was an exposure of the fact you have not done anything that others noted as good in publication or said tech shows like MS tech ed, as he has (after you called him mindless and what have you, no less).

  44. Flash HTML replacement. by DrYak · · Score: 1

    HTML5 will do nothing to replace embeddable TrueType fonts

    No, HTML won't do it because that's something that has been doable with src, url & format keywords in CSS. The only problem is that not all browsers supports those.
    HTML is about content, CSS is about visual style.

    vector animation

    Again, animation isn't HTML's job. It's Javascript's. And SVG could be animated with DOM. Once again the main obstacle is getting the specification adopted everywhere.

    built-in MP3 and MP4 support

    Supporting audio is a problem tackled by the Audio tag.

    Specific codecs: Well that's where the whole debate is. Both Mp3 and Mp4 are covered by patents. Some like Mozilla feel that, as an open standard, HTML5 should also use codecs which are freely implementable by anyone.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]