Slashdot Mirror


Vimeo Also Introduces HTML5 Video Player

bonch writes "Following in YouTube's footsteps, Vimeo has now introduced its own beta HTML5 video player, and like YouTube, it uses H.264 and requires Safari, Chrome, or ChromeFrame. The new player doesn't suffer the rebuffering problems of the Flash version when clicking around in the video's timeline, and it also loads faster. HTML5 could finally be gaining some real momentum."

369 comments

  1. Excellent. by Khyber · · Score: 3, Insightful

    Now if only FireFox will get support.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    1. Re:Excellent. by PenguSven · · Score: 2

      Now if only FireFox will get support.

      I think you mean

      Now if only FireFox will add support.

      --
      What is...?
    2. Re:Excellent. by Winckle · · Score: 3, Insightful

      This is a big thing for me. I don't give a damn about their ideology or their patent concerns, if youtube choose h264 then h264 has won this mini format war, and firefox better swallow their pride and licence it.

      If they don't, i'll end up on chrome for windows, and I already use Safari on mac because their mac UI team are atrocious.

    3. Re:Excellent. by Korin43 · · Score: 4, Insightful

      Honestly, as much as I'd like to stop using Flash immediately, I'd rather have Mozilla try to stick this out. Somewhere around a third of all people on the internet use Firefox (and I assume a higher number of Youtube users). If Mozilla can push Google to support Theora it will be worth the wait.

    4. Re:Excellent. by smash · · Score: 4, Insightful
      Everybody transcoding their videos = not going to happen.

      If firefox do not support H.264, they're going to become irrelevant as far as video goes.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    5. Re:Excellent. by Anonymous Coward · · Score: 0, Insightful

      Too bad theora sucks compared to h.264

    6. Re:Excellent. by Jessta · · Score: 1

      Putting your hand up to pay for the licensing of H.264?
      At least with flash adobe was nice enough to make a linux version at no cost.

      --
      ...and that is all I have to say about that.
      http://jessta.id.au
    7. Re:Excellent. by Korin43 · · Score: 0

      It's hard to find a good comparison, but most seem to be pretty favorable to Theora.

    8. Re:Excellent. by Korin43 · · Score: 2, Insightful

      Using Theora for new videos doesn't seem like such a big deal though. The article says that Vimeo's new HTML5 stuff doesn't work on 35% of their videos. I assume that has something to do with the encoding. The problem is that if we just accept the formats that require thousands of dollars for licensing, we'll never get to use free ones. Unless they're forced to (by a company like Google), Microsoft and Apple will never support a free format, because they can easily afford the licensing fees and they know that Mozilla can't.

    9. Re:Excellent. by smash · · Score: 5, Insightful
      Google has no incentive to go theora either, as it means transcoding all their stuff - and they clearly already have a h.264 license anyway.

      The authoring tools for .ogg are not there either.

      So really, open source people can whine all they want, it will make no difference - Firefox can buy a license, or they can become irrelevant. Or maybe start their own video hosting to compete, but my bet is that will be more expensive than a h.264 license.

      Or hell, they can just use whatever codecs are available on the host platform.... and get back to what they should be worried about - writing a web browser, rather than getting involved in a codec war they have no chance winning

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    10. Re:Excellent. by Philip_the_physicist · · Score: 5, Informative

      https://bugzilla.mozilla.org/show_bug.cgi?id=422540
      They are working on a Gstreamer backend for the video tag, and that will provide support for h264. From skimming the comments, it seems that there is a working but slow patch for 3.5, which is yet to be updated for 3.6.

    11. Re:Excellent. by javilon · · Score: 4, Insightful

      This will of course benefit ChromeOS and will force Microsoft into implementing html5 and H264 negating its strategy of killing adobe and becoming king of the online video.

      But there is a bad smell about this. Google could achieve this as well by adding Theora to the supported codecs. Google is putting Firefox in a position where it is either encumbered with patents therefore losing the status of "pure" open source project, or looking bad in the feature front. I don't like this.

      --


      When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    12. Re:Excellent. by Endymion · · Score: 3, Interesting

      Google (or any similar company) has no business reason to use Theora.

      If they do nothing, they still support Firefox, though flash. So why spend even a small amount of time/money to re-encode video?

      --
      Ce n'est pas une signature automatique.
    13. Re:Excellent. by Anonymous Coward · · Score: 0

      You know who gives a damn about their ideology? The people who actually write Firefox. You know who gives a damn about patent concerns? The rights holders, and the people who actually write Firefox.
      If you don't like how the Fireox devs ideology has affected Firefox in this manner (i.e. no h264 licensing) then don't use it, but don't whine about the ideology that made Firefox possible in the first place.

    14. Re:Excellent. by Anonymous Coward · · Score: 0, Insightful

      are you fucking kidding?

    15. Re:Excellent. by Anonymous Coward · · Score: 1, Informative

      Must be a typo. I think you'll find most seem to be pretty favourable to H.264. Unless that is you could provide a single link that shows a Theora video with higher quality than H.264 at the same bitrate?

      I could give you about 10 that show otherwise. here's one

    16. Re:Excellent. by bill_mcgonigle · · Score: 4, Insightful

      and firefox better swallow their pride and licence it.

      Why should they license it when an embeddable player is available on every OS with noticeable marketshare?

      They just need to enable the HTML5 video tag to use that. Oddly enough I couldn't find this bug at BMO with a quick search.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    17. Re:Excellent. by Winckle · · Score: 1

      That's cool. They can not care what their users think, and not support big popular websites, and they can have all the ideology they want and no users.

    18. Re:Excellent. by smash · · Score: 3, Insightful

      Or firefox could have.... a plugin architecture for whatever codec the user likes, preventing us from being stuck with some shitty 2010 codec technology 5 years from now.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    19. Re:Excellent. by BZ · · Score: 2, Interesting

      > Why should they license it when an embeddable player is available on every OS with
      > noticeable marketshare?

      Because those players tend to be security hellholes. Passing unsanitized data to them is a good way to get exploited...

    20. Re:Excellent. by Dr.+Spork · · Score: 4, Insightful

      Also, Ogg Theora is just less good than h264 on several levels. For one thing, there are hardware decoders for h264, but more importantly for me, h264 just indisputably looks better. Seriously, in this grudge match of Firefox v. Google (and now others), Firefox is on the losing side. I hope the developers realize this soon. Maybe Google is not intervening because they're happy to let people say "fuck it, I guess I'll try it with Chrome" - as I'm about to.

    21. Re:Excellent. by clem · · Score: 5, Funny

      You know, I was originally leaning towards Theora as the better codec. But your brazen anonymous cursing has turned me right around on this issue. Well done, sir.

      --
      Your courageous and selfless spelling corrections have made me a better person.
    22. Re:Excellent. by sxpert · · Score: 5, Informative

      Now if only FireFox will get support.

      I think you mean

      Now if only FireFox will add support.

      Now, if only the stupid h264 codec would be freed !

    23. Re:Excellent. by amorsen · · Score: 1

      Firefox can't realistically license H.264. We're talking a license for unlimited copies with the right to do pretty much anything you want with the copies, including turning them into video editing software. It would be the last license sold, because everyone else can just piggy back on it.

      --
      Finally! A year of moderation! Ready for 2019?
    24. Re:Excellent. by Anonymous Coward · · Score: 0, Insightful

      How could anyone possibly lean to Theora being a better codec?
      Fixing your patent system is the solution, not using Theora.

    25. Re:Excellent. by Antiocheian · · Score: 1

      Same here. His argument is flawless and convincing. I thought Theora was fine but I am fortunate enough to have read this great study (the second part -- the "kidding" -- is really eye opening). I won't be using Theora any longer either.

    26. Re:Excellent. by sulliwan · · Score: 1

      There is a 3rd option, don't buy the license, but include a decoder such as ffmpeg anyway, just don't allow the feature on copies of Firefox used in countries which enforce software patents. Not being able to watch YouTube might just nudge the average American to at least get informed about the issue. Codec licenses make no sense, it's a license to use a mathematical equation. Licensing specific implementations is fine, there are free alternatives which don't use any of the copyrighted code available.

    27. Re:Excellent. by FrostedWheat · · Score: 1

      And while politicians are fixing* the issue, what do we use in the meantime?

      * HAHAHAHAHA!

    28. Re:Excellent. by master5o1 · · Score: 3, Insightful

      How does using HTML5 + H.264 negate their attempt to draw people away from Flash for video? It just doesn't aide their Silverlight efforts.

      --
      signature is pants
    29. Re:Excellent. by LordVader717 · · Score: 1

      FireFox can't license it because the GPL explicitly forbids it. The legality of GPL'd software using propreitary codecs is ambiguous, a situation which Mozilla wishes to avoid.

      I wish Youtube would support Theora, but OTOH I realize that most people just want to give the codec a boost. If Youtube want to use a patent-encumbered viideo format, that's their right to do so. The move away from flash certainly makes the platform more open and less dependent on proprietary technology. But they must also realize that this means an inferior solution for the worlds most popular browser to support HTML5.

      The real scandal is Apple's attempt to sabotage Theora.

    30. Re:Excellent. by CowboyBob500 · · Score: 1

      And neither to the majority of Internet users around the world as there is no license required outside of America (and possibly Japan). OSS supporters need to focus on the fact that it is the US patent system that is broken here, not the codec.

    31. Re:Excellent. by CowboyBob500 · · Score: 5, Insightful

      And a majority of that third live outside the jurisdiction of the US patent system so the license issue becomes moot. Personally I'd rather the rest of the world stick 2 fingers up at the US system and continue to use browsers that support H.264 and don't pay any patent licenses to anyone.

      For example, why not make a US and non-US version of Firefox with the non-US version having H.264 support. US people will still manage to get the working version and Firefox will still have the required support.

    32. Re:Excellent. by mattsday · · Score: 1

      What's wrong with using, say, DirectShow/Quicktime/FFMPEG/etc on various platforms provided those libraries exist and using a built-in theora for basic compatibility?

      I understand the patent dispute and it does make sense, but why not pass the buck on the most popular platforms and get a different library to render the video?

      --
      Now there's one hoopy frood who really knows where his towel is!
    33. Re:Excellent. by gedw99 · · Score: 1

      I noticed that the vimeo videos look much better anti-aliased that the You tube videos.

      both are doing h264, but vimeo is much better looking !!!

      come on Google get your Sh% together ...

    34. Re:Excellent. by Tapewolf · · Score: 1

      That's cool. They can not care what their users think, and not support big popular websites, and they can have all the ideology they want and no users.

      Hundreds of millions of people use Firefox, according to Mozilla's estimates. Even a modest amount per infringement would result in legal damages of at least one billion dollars.

    35. Re:Excellent. by Anonymous Coward · · Score: 0

      It's a small quibble, but the *nix equivalent of DirectShow/QuickTime is Gstreamer and Xine (perhaps others). FFMPEG is merely a nice video converting program (perhaps you're thinking of it's association to libvacodec, which can be used to power xine media player).

    36. Re:Excellent. by Andreas+Mayer · · Score: 1

      It's hard to find a good comparison, but most seem to be pretty favorable to Theora.

      That's the first time I hear this. Care to give just one example?

      Anyway, I don't believe Theora has a chance. It's just like it was with MP3/Vorbis. Everything supports H264 and most people have absolutely no incentive to use anything else, let alone some obscure OSS codec.

    37. Re:Excellent. by polyp2000 · · Score: 1

      You used the "J" word ... surely it must be that simple ... LOL

      --
      Electronic Music Made Using Linux http://soundcloud.com/polyp
    38. Re:Excellent. by Anonymous Coward · · Score: 0

      Firefox can buy a license, or they can become irrelevant.

      Are you a shill, or just a simpleton Troll? The only thing that will become irrelevant are the people and products who support the lowest common denominator. I almost never use Youtube because it requires flash, javascripts, cookies and a bunch of other security and privacy nuisances. Given the quality of things that are uploaded to Youtube (and the quality of the discussions and comments), I'd say most people are better offer sticking to text-only sites where quality and substance almost always out-ranks Flash (the technology and the adjective).

      The intelligent people are the ones who will use independent third party tools to download YouTube videos that they really feel they need to watch. And nope, Firefox does not need a license to use h.264 because that codec and the corporate idiots behind it never had the intelligence to properly and legally patent it.

      - Signed,

      a former Slashdotter who still lurks occasionally

    39. Re:Excellent. by BlackHawk-666 · · Score: 1

      You're indulging in the "Not written here" attitude, where code that is written in any other codeshop is considered inferior. If the programmers would put their egos on hold for a while and learn to re-use code and acquire libraries then they might actually start to get some product out the door.

      For the record, I have almost 30 years experience writing code, and a good decade of running teams of programmers. I know what they're like.

      --
      All those moments will be lost in time, like tears in rain.
    40. Re:Excellent. by delinear · · Score: 1

      That's a very good point, and while there are still so many non-HTML 5 enabled browsers (various versions of IE, I'm looking at you) lurking around out there, the big players will have to continue to offer at least this level of dual support.

    41. Re:Excellent. by r00t · · Score: 1

      You're indulging in the "Not written here" attitude, where code that is written in any other codeshop is considered inferior.

      If you're good enough, this is normally true!

      The people hacking Firefox are people who enjoy writing code. It's not just a paycheck. It's a pretty good bet that most of them are good.

      More importantly, you have to remember: documentation, interface changes, emergency repairs. Random not-written-here code often fails all 3 of those issues, especially if you don't have full source code rights.

    42. Re:Excellent. by Anonymous Coward · · Score: 0

      Internet browsers are a major target for security attacks.

      What is your suggested response to a security problem in a third party codec? Should Mozilla/Firefox just say "Not my problem!"?

    43. Re:Excellent. by Anonymous Coward · · Score: 0

      Why do you assume the answer is to infringe the patent rather than do what everyone else must be doing and pay the license cost?

      Note, I'm not necessaily saying they should implement this, it's up to the people behind FF whether they'd rather not support it and risk losing users (and this depends on whether their ultimate aim is to have the number 1 browser or to have the most possible users while being 100% true to the open source ideal), but just clarifying that leave it out or infringe the patent are not the only options here.

    44. Re:Excellent. by Alioth · · Score: 1

      Why does Firefox need to carry the codec at all? Why not just use the installed system libraries to play h.264 video? Then it ceases to be Mozilla's problem.

    45. Re:Excellent. by abhi_beckert · · Score: 1

      Good quality vorbis videos take up too much disk space for YouTube to use it (they said so during html5 spec arguments).

      So either firefox supports h.264 (via QuickTime plugin?) or users have to put up with flash.

    46. Re:Excellent. by Anonymous Coward · · Score: 0

      Google could achieve this as well by adding Theora to the supported codecs.

      By that i believe you are meaning convert every file on Youtube to have the codec for Firefox?
      Are you shitting me? That ain't easier at all. That is A LOT of data.

      It would be easier for Mozilla to give up and go with the team.

      But this is a format war, it will either continue for several years, or it could end next week.
      I'd rather the format companies just got together to work on the best format they can for the web, that would be much nicer.
      Can't see that happening, they'll only end up arguing over the name.

    47. Re:Excellent. by tepples · · Score: 1

      There is a 3rd option, don't buy the license, but include a decoder such as ffmpeg anyway, just don't allow the feature on copies of Firefox used in countries which enforce software patents.

      The trouble is that Mozilla Corporation is headquartered in a country that enforces software patents.

    48. Re:Excellent. by delinear · · Score: 1

      Aren't Google and Apple in the same situation? Without knowing the intricacies of Mozilla's funding (and it's possible they might attract less donations if they start licensing commercial products) or the costs involved in licensing, I don't know how realistic this is but it must apply to them all (and if everyone can piggy back on this, why don't FF piggy back on Chrome?).

    49. Re:Excellent. by tepples · · Score: 1

      Given the quality of things that are uploaded to Youtube (and the quality of the discussions and comments), I'd say most people are better offer sticking to text-only sites

      Then why did the popularity of television grow at the expense of things like Reader's Digest?

      Firefox does not need a license to use h.264 because that codec and the corporate idiots behind it never had the intelligence to properly and legally patent it.

      Where did you learn that?

    50. Re:Excellent. by Anonymous Coward · · Score: 0

      good i managed to convince at least one of you dumbasses!

    51. Re:Excellent. by ChienAndalu · · Score: 1

      They are already transcoding everything to .flv

    52. Re:Excellent. by hitmark · · Score: 1

      unless i am totally off target, firefox is under a special license called the mozilla public license (MPL).

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    53. Re:Excellent. by TheRaven64 · · Score: 1
      True in more ways than one. Outside the USA, the software patents on the CODEC are not valid. The only open source implementation of H.264 that I am aware of, however, is x.264 which is GPL'd. As Mozilla is distributed under three licenses (GPL, LGPL, and MPL) it can only use code which is compatible with all three of these licenses, which excludes x.264.

      Interestingly, Opera claims to be using GStreamer to implement the video tag. The H.264 implementation in GStreamer is based on x.264, so if Opera is distributing this then they are in violation of the GPL.

      --
      I am TheRaven on Soylent News
    54. Re:Excellent. by aliquis · · Score: 1

      Why should there be freaking codecs in the browser in the first place?

      Just let people build firefox with gstreamer or whatever if they want to get video support or without it if they don't care.

      (Multiview on the Amiga showed whatever (exceptions?) file you had a datatype for.)

      Personally I would had been fine with the tag supporting ANY video format and then put the responsibility for actually having a codec for it in the hands of the user. But I can understand why they don't do this (though now the user may have to be able to understand how to convert their files instead, which may be equally or even more complicated.)

      Anyway, sure a free format would be nice but do one really want one if it looks much worse at the same bitrate? To use Theora just because it's free even if it sucked would, well, suck. (And to demand that the videos will be H.264 now and forever suck to, but I guess they will follow up with H.265 and so on to.)

      And in the end neither of GIF, JPEG or MP3 was free? Right? Would free ones had been better? Probably, but if they aren't popular who cares?

    55. Re:Excellent. by TheRaven64 · · Score: 1

      Self reply: Opera is only distributing the LGPL'd CODECs for GStreamer, which means that they won't be supporting H.264 on Windows, only on *NIX for people who installed GStreamer themselves.

      --
      I am TheRaven on Soylent News
    56. Re:Excellent. by tepples · · Score: 1

      Personally I'd rather the rest of the world stick 2 fingers up at the US system

      By opening up to immigrants from the US, or no?

      For example, why not make a US and non-US version of Firefox

      Because Mozilla Corporation is headquartered in the United States, and several European countries appear to recognize patents on H.264 and AAC as well.

    57. Re:Excellent. by TheRaven64 · · Score: 1

      FLV is a container format, not a CODEC. You are not transcoding to FLV, you are just packaging the bitstream, which is much faster. The YouTube FLV files contain... H.264. All H.264 video tag support costs them is the time to package the existing bitstream in a different container, which they can probably do on the fly and (optionally) cache. They already have the infrastructure in place for doing this because the iPhone gets the H.264 without Flash. If you use Safari with the ClickToFlash plugin, you've already lost Flash from YouTube, because it has an option to fetch the video and play it with the QuickTime plugin instead of Flash, which uses about 10% of the CPU that the Flash player uses.

      --
      I am TheRaven on Soylent News
    58. Re:Excellent. by DrXym · · Score: 1

      Firefox shouldn't care if its free or not. If the OS exposes the H264 codec through its multimedia APIs, Firefox should make use of it.

    59. Re:Excellent. by Anonymous Coward · · Score: 0

      Then why did the popularity of television grow at the expense of things like Reader's Digest?

      You seem to be getting off topic here. The discussion is the Internet (or at least that was the scope of my arguments). Readers Digest (oh man you're making me laugh), is the epitome of lowest common denominator. You know what happens when food gets digested? The same things happen with information. A more logical and relevant comparison would be a discussion section in a Youtube comment area compared to a discussion section in a Slashdot area. Yepp it can get bad here, but not THAT bad -:)

      Jeezus, I remember when my dad read a Readers Digest article about how long haired kids who listen to heavy metal music are "Drug abusers". TV was slightly more intelligent than that (TV had PBS and the McNeil/Lehrer Report, Frontline, Nova, etc and so on...). And Gilligan's Island and Looney Tunes, and All in the Family... Back then not just anybody could create content and post it up for everybody to see.

      To digress a bit, Readers Digest was actually most popular at the time before TV became de-regulated. And apparently the most upstanding in the community still read the magazine ("According to MRI, Reader's Digest reaches more readers with household incomes of $100,000+ than Fortune, The Wall Street Journal, Business Week and Inc. combined." Readers Digest). It's a sad state of affairs.

      Where did you learn that?

      Wikipedia, under h.264 (I didn't think I'd need to reference it).

      At any rate, I will emphasize that I do not necessarily think Youtube is a bad thing (it can be quite useful. However, people should not be rewarding bad practices; (and the people who do are generally not the most intelligent). That is the main crux of my motivation to post here.

    60. Re:Excellent. by DrXym · · Score: 1

      Firefox doesn't have to ship with any H264 support, apart perhaps from a basic understanding of MP4 containers. All it has to do is check the container to see what audio / video codec is used, check with the system to see if it provides those codecs, and then either play the content or direct the user to some help where they can sort themselves out.

    61. Re:Excellent. by TheRaven64 · · Score: 2, Interesting

      It's not quite so clear cut. H.264 is better than Theora, but VC-2 (which is patent-free, based on the BBC's Dirac) is competitive with, and in a lot of cases better than, H.264. Importantly, the BBC is working with hardware manufacturers to get it accelerated (there was also a Google SoC project last year to implement it in GLSL so you can run it on a GPU). VC-2 looks like, in a couple of years, it will be the ideal format for web video. Using Theora now sets a precedent that royalty free implementation is important for web standards.

      --
      I am TheRaven on Soylent News
    62. Re:Excellent. by Anonymous Coward · · Score: 0

      As someone who doesn't live in the US, I'm glad the technically superior format won in spite of stupid laws. I think that the patents won't make much of a difference in the US either - people will just install a third-party codec or something even if Mozilla can't distribute them.

    63. Re:Excellent. by tepples · · Score: 1

      You seem to be getting off topic here. The discussion is the Internet

      You made a point that text is better than video. I was showing you a counterpoint. Can you recommend a video sharing site with more intelligent comments on the whole than YouTube?

      the corporate idiots behind it never had the intelligence to properly and legally patent it. [source:] Wikipedia, under h.264

      I assume that you refer to this part of the article: "In December 2008, the US Court of Appeals for the Federal Circuit affirmed the District Court's order that the patents be unenforceable but remanded to the District Court with instructions to limit the scope of unenforceability to H.264 compliant products." If true, this would resemble Microsoft's open specification promise in effect. But it still poses problems for free software similar to those of Microsoft's open specification promise: work-in-progress decoder implementations can't be published because they are not yet compliant, and the copyleft licenses typically require that patented inventions used in covered works be made available for all purposes. Besides, the United States isn't the only country with H.264 patents.

    64. Re:Excellent. by TheRaven64 · · Score: 2, Informative

      No. The licenses for Chrome and Safari do not allow unlimited distribution. The H.264 licenses are capped per year, so Mozilla Corp. could easily afford to pay for an H.264 license for this year and then everyone who distributed FireFox would have a legal license as part of that. However, if they stopped paying, people who had received FireFox would then be unable to legally redistribute it. As Mozilla is distributed under three licenses which all permit redistribution, that would mean that anyone, like a Linux distribution, that distributed copies from upstream would be infringing.

      I'm not sure if FireFox and Gecko require copyright assignment for patches, but if they don't then the Mozilla Foundation would also be violating the copyright of their contributors if they distributed it along with code that required a patent license.

      --
      I am TheRaven on Soylent News
    65. Re:Excellent. by Goaway · · Score: 4, Insightful

      Mostly it seems Mozilla just do not want to support anything but Theora, and they're making up weak excuses for why they shouldn't use platform libraries to play video.

      I sure hope they grow out of it soon.

    66. Re:Excellent. by CowboyBob500 · · Score: 2, Insightful

      Because Mozilla Corporation is headquartered in the United States

      Tough luck for them. I't won't be long for a fork to appear that includes the H.264 codec - possibly released by Canonical or other interested party . The US seems to be rapidly heading towards some kind of lawsuit singularity which it needs to pull back from or simply disappear.

      several European countries appear to recognize patents on H.264 and AAC as well.

      Citation? I can't find anything concrete to support this statement.

    67. Re:Excellent. by Anonymous Coward · · Score: 0

      You made a point that text is better than video. I was showing you a counterpoint. Can you recommend a video sharing site with more intelligent comments on the whole than YouTube?

      I don't think I did make "a point that text is better than video". It all depends. I certainly didn't (intend) to give any type of intellectual status to Readers Digest. I don't generally go to download sites. I don't generally tend to go to discussion sites either (as I've stated earlier, I've given up on Slashdot, although old habits die hard... I guess my standards are too high -:)).

      To be more specific as to my motivations for posting, I was really disappointed by this statement; "Firefox can buy a license, or they can become irrelevant." Which was moderated way up, and yet it is so simple (stupid). Firefox will only become irrelevant to people for whom it has no relevance. Making a blanket statement like that is illogical. If companies like Google (Youtube) don't want to play nice with free and open source software then people have a choice to bend over and take it like a man, use alternatives (I mentioned Youtube downloaders), or change behaviors (don't even bother going to these sites... i.e. why not go to a reference library and read a science journal instead of Readers Digest?). Clearly, most people are just going to support Youtube. So be it, if that's what they want. It will just make things more difficult for people like me who continually find it harder and harder to travel (the Internet or the World) without being anally probed and having to financially support (by hook or by crook) corporations who proclaim to "do no evil".

      I assume that you refer to this part of the article [wikipedia.org]

      Yeah. I was thinking about getting a bit deeper into things, but everybody here already knows how IP laws are complicated, and lawyers like to complicate things further. I was just making my point (my two-cents).

    68. Re:Excellent. by packman · · Score: 1

      Hmm - in what time-frame are you stuck? You already know how to make fire?

      I mean - wake up. Your view of the world is so damn limited it irritates me, and I see this a lot on /. Your life is simply not the center of the universe. Yes - you don't use Youtube, have something against javascript, cookies and flash (can't disagree on the last-one actually)... without knowing what the hell you're actually talking about. HTML5 and Javascript are married, the videotag without javascript is pretty useless. Cookies are usefull things that can be used to track you, but a decent browser makes sure this is limited. Privacy issues? Simply don't browse the web then. You're not in 1995 anymore.

      For the vast majority of the users, only one thing matters: it works. It doesn't even have to work well or be the best. Just look at IE6's marketshare to prove that point. 99,9% of all firefox users don't give a damn about those things and go with the defaults. If firefox doesn't work, and the Internet Explorer also installed on their system does, they'll drop FF in an eye-blink...

    69. Re:Excellent. by Anonymous Coward · · Score: 0

      Then those players need to be fixed. The solution is not to implement a new palyer with more posible bugs.

    70. Re:Excellent. by ChienAndalu · · Score: 1

      Thanks, I didn't know that.

      However the last time I checked, you could upload videos in a dozen or so formats, which then get converted to h264 and resized into different resolutions. So there is a lot of encoding already going on.

    71. Re:Excellent. by jez9999 · · Score: 1

      And a majority of that third live outside the jurisdiction of the US patent system so the license issue becomes moot. Personally I'd rather the rest of the world stick 2 fingers up at the US system ... at which point the US uses powerful trade sanctions to ram their IP laws down other countries' throats, and other countries' leaders kowtow because the people see the sanctions as more of an immediate problem than long-term onerous licencing laws.

    72. Re:Excellent. by tendays · · Score: 1

      Someone posted this in the previous H.264 versus Ogg story, which gives a data point including screenshots pointing to ogg being better: http://people.xiph.org/~greg/video/ytcompare/comparison.html

    73. Re:Excellent. by icebraining · · Score: 2, Informative

      In countries where patents on software algorithms are upheld, the vendors of products which make use of H.264/AVC are expected to pay patent licensing royalties for the patented technology that their products use. This applies to the Baseline Profile as well. A private organization known as MPEG LA, which is not affiliated in any way with the MPEG standardization organization, administers the licenses for patents applying to this standard, as well as the patent pools for MPEG-2 Part 1 Systems, MPEG-2 Part 2 Video, MPEG-4 Part 2 Video, and other technologies.

    74. Re:Excellent. by Just+Some+Guy · · Score: 1

      Firefox can buy a license, or they can become irrelevant.

      Or than can say, "hey, we can get our users switched over to your codec a lot faster than Microsoft can talk theirs into upgrading from IE6. Give us a free license so we can make your product the de facto standard?"

      --
      Dewey, what part of this looks like authorities should be involved?
    75. Re:Excellent. by maxume · · Score: 1

      ffmpeg appears to support decoding h.264 independent of x.264 (but uses x.264 for encoding).

      (I realize that Gstreamer doesn't depend on ffmpeg as much as other video apps, but if the code is in ffmpeg, it is out there, so the only obstacle would be patents)

      --
      Nerd rage is the funniest rage.
    76. Re:Excellent. by icebraining · · Score: 1

      It will nudge them to switch to the browser someone said on twitter/facebook that works with Youtube.

    77. Re:Excellent. by sgtrock · · Score: 1

      So, do you have $5,000,000/year to give to Mozilla for the H.264 licensing fee?

    78. Re:Excellent. by Goaway · · Score: 1

      ...Which does, as far as I know, not apply when you use the OS-supplied functionality for playing h.264.

    79. Re:Excellent. by icebraining · · Score: 1

      Not only FLV is only a container, as it has been said, but many videos in "HQ" are already in MP4.

    80. Re:Excellent. by maxume · · Score: 1

      Here's a link to the LGPL source file (well, presumably the main file implementing the support, I haven't studied the structure closely, and there are about a dozen files in the directory with h264 in the name):

      http://git.ffmpeg.org/?p=ffmpeg;a=blob;f=libavcodec/h264.c

      --
      Nerd rage is the funniest rage.
    81. Re:Excellent. by LordVader717 · · Score: 1

      Click within Firefox.
      The MPL contains similar restrictions BTW.

    82. Re:Excellent. by RailRide · · Score: 1

      Minor trivia:

      If you encode your uploads as Flash video with the previous codec used by YouTube, H.263 compression with less than 350kb/s audio+video bitrate, then they'll pass onto YouTube's servers unmolested. I do this, and my uploads are viewable within a minute or so of uploading, rather than spending several minutes "Processing, please wait".

      When I re-downloaded one of my recent videos to examine it (using Super©*), it was still in H.263 format.

      Why do this? Less CPU-intensive for older systems (videos of long model trains--which comprise most of my submissions--tend to highlight framerate issues), and it's compatible with my Archos 5-series media device (as well as their TV+ DVR), so I need not produce two versions of the same video.

      ---PCJ

      *(yes they do make it tedious to find the d/l link. It's at the bottom of ths page if you're looking for it)

    83. Re:Excellent. by stdarg · · Score: 1

      What is the licensing fee per person? Why would it be difficult to turn h264 support into a plugin that costs the same as the license fee plus 35 cents for transaction costs? From other comments on the thread, the fee wouldn't even be required for many Firefox users who are based outside the US, and users inside the US could buy it if they really hate the idea of watching videos via Flash.

    84. Re:Excellent. by bill_mcgonigle · · Score: 1

      Guilty as charged. Still, it's already been working for other object types for, what a decade?

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    85. Re:Excellent. by bill_mcgonigle · · Score: 1

      Because those players tend to be security hellholes. Passing unsanitized data to them is a good way to get exploited...

      That bridge has already been crossed - Firefox will already happily embed, say, a QuickTime Player object for you with other tags. The only difference would be enabling that functionality for the VIDEO tag. Nothing's going to stop the bad guys from using an object or embed tag if they want to get you!

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    86. Re:Excellent. by EvilRyry · · Score: 1

      I think you meant Theora, as Vorbis is an audio codec. Or maybe you'd like to go watch some MP3 videos.

      How many times does this link need to be posted for people to stop the Theora/Vorbis FUD? http://people.xiph.org/~greg/video/ytcompare/comparison.html

    87. Re:Excellent. by wvmarle · · Score: 1

      Wouldn't it be possible to use an extension for that? I'm not a moz dev but it seems to me having used some extensions that they can basically do anything. Hooking in to the video tag, checking whether there is h264 content, and if so take care of that content should be possible. Either with supplied codec, or by using whatever the underlying system exposes.

      Then indeed anyone outside the US would be able to legally see h264 in Firefox. And anyone inside the US would be able to illegally do the same.

      And then there is mplayer-plugin. Since quite some time I am watching YouTube videos in Firefox/Ubuntu without even having Flash installed. Greasemonkey and some scripting pull the h264 from YouTube and feed it to mplayer.

    88. Re:Excellent. by Ihmhi · · Score: 1

      I wonder if it would be unethical from a FOSS standpoint for Firefox to put out an announcement about how to use these codecs through. Firefox needs to have enough people adopting them for Vimeo, YouTube, etc. to accept those browsers.

    89. Re:Excellent. by bflong · · Score: 1

      "I don't give a damn about their ideology or their patent concerns"

      I'll just stop reading there. Thats really stupid of you.

      --
      Why is it so hot? Where am I going? What am I doing in this handbasket?
    90. Re:Excellent. by BZ · · Score: 2, Interesting

      > where code that is written in any other codeshop is considered inferior

      Not at all. I've written my share of code with security bugs in it and have no illusions about code I write.

      But the key thing here is attack surface. Taking a shot at securing the decoder for the one codec that Firefox ships (by fixing the bugs fuzzers found in it, for example) took several man-months of work. This is work that has in fact not been done on most of the platform-default decoders, especially because new ones can be dropped in at any time. Firefox could whitelist codecs, but that's not what the proponents of using the system codec set are pushing for.

      And since those system codecs would not be something Firefox can control the updating of, if there _is_ a security vulnerability in one... then what? Ship a Firefox update that disables that codec (blacklisting, effectively)? There don't seem to be any other options.

      This isn't a theoretical issue, by the way; please count up the number of codec vulnerabilities patched in just Quicktime on Mac over the last year.

    91. Re:Excellent. by Korin43 · · Score: 1

      No I'm not going to find an example. Every time this comes up I hear "OMG BUT THEORA SUCKS", while in every comparison I've seen, Theora just does fine (except comparisons of old versions of Theora). If someone wants to convince me that there's a problem with the codec, why don't they post their proof? Instead all of the responses to me are "OMG BUT THEORA SUCKS" or "LOLZ EVERYONE KNOWS THAT THEORA SUCKS. QED.".

    92. Re:Excellent. by sgtrock · · Score: 1

      I'm not opposed to seeing the plug-in architecture extended to support generic video codecs. However, does that automatically meant that Mozilla has to write the plug-in as well? My guess is that as soon as they did, they'd have lawyers knocking at their door, discovery request in hand, asking to see all of their records concerning downloads inside the U.S. Failure to answer the discovery request adequately would immediately be followed up for a bill for the entire download list. NOT a pleasant place for Mozilla to be.

    93. Re:Excellent. by ObsessiveMathsFreak · · Score: 1

      Mostly it seems Mozilla just do not want to support anything but Theora, and they're making up weak excuses for why they shouldn't use platform libraries to play video.

      Using platform libraries is how web video (including flas) already works. Or should I say, already doesn't work.

      --
      May the Maths Be with you!
    94. Re:Excellent. by Anonymous Coward · · Score: 0

      Must be a typo. I think you'll find most seem to be pretty favourable to H.264. Unless that is you could provide a single link that shows a Theora video with higher quality than H.264 at the same bitrate?

      I could give you about 10 that show otherwise. here's one

      Once you compare Theora to a high quality H.264 encoder it looks pretty bad, unfortunately most people here only seem to know that one comparison done by Xiph themselves against the (relatively crappy) Youtube H.264 encoder with animated content where differences are generally harder to spot. The differences at the same bitrate are obvious in other comparisons.

      Here are some more:
      Videos Encoded with Theora 1.1 and x264 r1259. The "Island" trailer shows the differences well because there are lots of high motion scenes.
      Metrics Animated content. Relatively new.
      Metrics By one of the Xiph guys. A little older. Huge lead for H.264.

    95. Re:Excellent. by FrankieBaby1986 · · Score: 1

      I like that idea! I have another one too, which I've mention on /. before. The patents on h264 are holding back the Web, progress, and so America and the world. Their time is up. The creators have made their money back and then some, I'm sure. The US government should either

      A) Invalidate the H264 patents.

      B) Apply some kind of "Eminent Domain" or simply out right BUY OUT and release the codec as free.

      --
      ERROR: SIG NOT FOUND (A)bort, (R)etry, (F)ail?:
    96. Re:Excellent. by moosesocks · · Score: 2, Interesting

      Google just purchased on2, who own the IP rights to a number of rather good codecs, including a few that they claim to be as good as, if not better than H.264.

      Theora, on the other hand, isn't a particularly good codec.

      IMO, the best thing for google to do would be to release on2's codecs under a permissive license, and make them the exclusive means by which HD content is delivered via YouTube. This should ensure a rather speedy adoption among all of the major browsers.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    97. Re:Excellent. by Anonymous Coward · · Score: 0

      That's because everyone knows that Theora sucks.

    98. Re:Excellent. by ObsessiveMathsFreak · · Score: 1

      Google (or any similar company) has no business reason to use Theora.

      This is true. Google is an internet services provider. Unfortunately, they also make a browser now, which means they can pretend to be a browser maker when giving their opinions to W3C on the video tag.

      Likewise, it is true for Apple, who are a hardware/online retail company. Again, they also happen to make a browser, so can again pretend to be a browser company when talking to W3C.

      Meanwhile, actual browser companies like Opera and Mozilla have every business reason to not touch H264 with a ten foot pole. They tried telling this to W3C--seeing as they have more users than the aforementioned other two companies--but to no avail. They didn't listen.

      Sometimes, I think Google just made a browser so they could push the web the way they want it to go.

      --
      May the Maths Be with you!
    99. Re:Excellent. by ardor · · Score: 1

      You can post this as often as you want, the comparison is still full of errors as a result of an ffmpeg bug (it was previously believed to be intentional). It uses x264, which is an opensource h264 encoder. The x264 developers responded to this comparison on reddit, highlighting the many errors in it: http://www.reddit.com/r/programming/comments/8iphn/theora_encoder_improvments_comparable_to_h264/

      --
      This sig does not contain any SCO code.
    100. Re:Excellent. by Sir+Homer · · Score: 1

      Well to use H.264 you must get a license. If Mozilla gets a license it only protects Mozilla from lawsuits, NOT the rest of the Internet. It could lead to a situation like when GIF was patented, where if you had a GIF on your website you could be sued if you didn't pay for some $5000 license. I don't know if some of you are old enough to remember that, but it sucked.

    101. Re:Excellent. by Sir+Homer · · Score: 0, Offtopic

      H.264 could lead to a situation like when GIF was patented, where if you had a GIF on your website you could be sued if you didn't pay for some $5000 license. I don't know if some of you are old enough to remember that, but it sucked.

    102. Re:Excellent. by Sir+Homer · · Score: 1

      Or YouTube will continue to use Flash. Not everyone hates Flash. To use H.264 you must get a license. If Mozilla gets a license it only protects Mozilla from lawsuits, NOT the rest of the Internet. It could lead to a situation like when GIF was patented, where if you had a GIF on your website you could be sued if you didn't pay for some $5000 license. I don't know if some of you are old enough to remember that, but it sucked.

    103. Re:Excellent. by bonch · · Score: 1

      YouTube chose H.264...the format war is over.

    104. Re:Excellent. by bonch · · Score: 1

      Why would you do that when the OS already has H.264 playback that Firefox could rely on?

    105. Re:Excellent. by TheRaven64 · · Score: 1

      VideoCD chose MPEG1... the format war is over.

      DVD chose MPEG2... the format war is over.

      Oh, wait. We can change CODECs every few years.

      --
      I am TheRaven on Soylent News
    106. Re:Excellent. by Baloo+Uriza · · Score: 1

      Except it's W3C that sets the standards.

      --
      Furries make the internet go.
    107. Re:Excellent. by amorsen · · Score: 1

      Chrome and Safari aren't Open Source or Free Software. You can't legally turn them into video editors and then redistribute them.

      --
      Finally! A year of moderation! Ready for 2019?
    108. Re:Excellent. by snadrus · · Score: 1

      Options:

      Buy h264: Won't happen. Would you sell it? Not in our patent system where it's "property" without a property value or eminent domain laws.

      Firefox gains h264: And becomes "impure" open source or moves out of the USA. Possible but unlikely.

      Move sites to $FREE_CODEC: h264 videos are already everywhere since Flash used them. Not gonna happen.

      Firefox uses OS Libraries: It stays clean and users/maintainers add what they want.

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
    109. Re:Excellent. by Hurricane78 · · Score: 1

      Now if only anybody in the real world would care if it is “free”.

      Every movie and show i downloaded in the last 2 years, was encoded with it.
      ffmpeg, vlc, mplayer, xine, windows, they all support it.

      So actually, the Firefox team would not have to get into any hassle AT ALL.
      Just bind to ffmpeg, and be done with it.
      And/or bind to DirectShow on Windows.
      As an alternative.

      This means: ZERO non-free code in Firefox (as it would be a dynamic OS library).
      Still support for the crappy Theora.
      And full H.264 support.

      If anyone still bitches about THAT, he need a hard slap with a reality towel. ;)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    110. Re:Excellent. by Hurricane78 · · Score: 1

      That’s the best thing: They don’t have to license shit.
      Just bind to DirectShow on Windows, ffmpeg on Linux, and CoreVideo on Mac, and you’re done.
      They can still offer a fallback to a builtin Theora codec.

      It’s just evangelism/extremism.
      Additionally, it’s impossible to sue everybody who uses H.264 without a license. Because everybody uses it. If they would care to rake in money trough lawsuits, they would long have started.

      Protip: GIF, MP3, H.264, etc, are de-facto free.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    111. Re:Excellent. by ifwm · · Score: 1

      "VideoCD chose MPEG1... the format war is over.

      DVD chose MPEG2... the format war is over.

      Oh, wait. We can change CODECs every few years"

      So you expectthe internet to be replaced by something new in the next few years?

      Otherwise, your examples are useless and invalid.

    112. Re:Excellent. by sznupi · · Score: 1

      Vimeo always had higher bitrate in their videos than most video sites; somewhat important considering they are "artsy" kind of video site to a large degree.

      I imagine that's still the case with HTML5/H264 video.

      --
      One that hath name thou can not otter
    113. Re:Excellent. by TheRaven64 · · Score: 1

      The Internet as a whole? No. Internet clients? Absolutely. Individual sites? Sure, easily. Upgrading Internet clients is pure software. Upgrading hardware players is much harder, but they go through upgrades every couple of years. The dominant format for video on the Internet has been MPEG-1, RealVideo, and now H.264. The format war isn't over, because when a better codec comes along it's trivial ton deploy it on the Internet. One round in the format war may be, but all formats are temporary.

      --
      I am TheRaven on Soylent News
    114. Re:Excellent. by BlackHawk-666 · · Score: 1

      I'm just wondering what makes the Firefox team certain they can write these codec implementations and players better than the teams who specialise in that field. Security can be quite tricky and there's no reason to believe that a volunteer for a browser project will also be bringing a raft of security programming practices to bear on his code.

      If anything, I think Firefox shouldn't ship with any media playing code or codecs, and instead should rely on the other projects to provide that via plug-ins, libraries, whatever it takes to hook the two together.

      Learn to delegate.

      I know Quicktime / ffmpeg / etc are all open to system flaws and attack, but what code isn't. How about you count up how many the Firefox project has had over the last 12 months and if it's any more than 1 it means you guys aren't producing perfectly secure code either.

      --
      All those moments will be lost in time, like tears in rain.
    115. Re:Excellent. by Korin43 · · Score: 1

      I just wanted to point out that the problem isn't as big as I'd thought. Apparently Webkit uses gstreamer now, so Chrome already supports Theora and Vorbis (at least on Linux), and Firefox is capable of using gstreamer (there has been a patch available since 3.0), so they could theoretically support anything. Safari will probably remain married to Quicktime, but with some work we could probably convince Apple to make Theora/Vorbis codecs ship by default. Similarly, I expect IE to use directshow when it gets HTML5 support, and while Microsoft will never add Theora/Vorbis by default, it's extremely easy to install.

      Just thought I'd add this since I learned some since writing my other reply.

    116. Re:Excellent. by BZ · · Score: 2, Informative

      > I'm just wondering what makes the Firefox team certain they can write these codec
      > implementations and players better than the teams who specialise in that field.

      Nothing. That's why they're not writing the codec impl they're using; they're using an off-the-shelf theora decoder (though they've contributed a bunch back to it in the process of integrating it).

      But the result is that the codec they're shipping they have the source for and have at least some people who can competently patch that source in the event of a security hole being discovered, while also sending the patch upstream.

      As for the player... The player being used is pretty much off-the-shelf too, as above, but the method of feeding data into it had to be custom-written to deal sanely with HTTP, security restrictions in the browser, etc.

      > no reason to believe that a volunteer for a browser project

      I believe everyone working on the Theora support in Firefox was in fact a full-time employee whose job it was to make it work.

      > I know Quicktime / ffmpeg / etc are all open to system flaws and attack, but what code
      > isn't.

      Sure. The question is what happens once such a flaw is discovered. If you're not Apple and you depend on Quicktime and a hole is discovered in Quicktime, what are your options? Have a security hole or stop playing videos until Apple patches it? The situation is, of course, better with ffmpeg.

    117. Re:Excellent. by node+3 · · Score: 1

      Google is putting Firefox in a position where it is either encumbered with patents therefore losing the status of "pure" open source project

      '"Pure" open source project'?

      1. See Iceweasel
      2. They have financial deals with Google for search placement and default home page[*]
      3. See the multitudes of other '"pure" open source projects' which support h.264
      4. Pass h.264 on to the OS or some other plugin. It's not like Firefox doesn't already make use of close-source OS functions.

      So I really don't know what this is all about except for Firefox attempting to *push* the technologically inferior theora codec for political reasons. While I appreciate the anti-patent stance, I'm perfectly fine with using h.264 and AAC. I want my media to be high quality, not ideologically pure.

      [*] I'm not opposed to this deal, just that it doesn't exactly shout "pure open source ideology". It shows a certain comfort level with pragmatic compromises, such as accepting money in exchange for a default search engine and home page.

    118. Re:Excellent. by node+3 · · Score: 1

      Firefox doesn't ship with Flash support, either, yet it works just fine.

      If there's some reason (which is *entirely* of Mozilla's own choosing) that they can't include native h.264 support, or use system APIs, they can simply let the user download a plugin (easily created using the existing x.264 project), problem solved.

    119. Re:Excellent. by node+3 · · Score: 1

      This is true. Google is an internet services provider. Unfortunately, they also make a browser now, which means they can pretend to be a browser maker when giving their opinions to W3C on the video tag.

      Likewise, it is true for Apple, who are a hardware/online retail company. Again, they also happen to make a browser, so can again pretend to be a browser company when talking to W3C.

      How are Apple and Google "pretending" to be "browser companies"? They actually make real browsers. Chrome and Safari aren't artifices intended to meet some sort of technicality for influence over the W3C.

    120. Re:Excellent. by Goaway · · Score: 1

      And not playing at all is a better state of affairs?

      (Also, Flash does not use platform libraries.)

    121. Re:Excellent. by Khyber · · Score: 1

      No.

      Of course, you probably know jack shit about fourcc-based codecs, so I'll just be quiet and let you make a fool out of yourself.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    122. Re:Excellent. by Khyber · · Score: 1

      "It's just like it was with MP3/Vorbis"

      HAHAHAHA NO!

      Try running a pitchshifter plugin across an MP3 versus an OGG.

      You will notice the sound quality in an OGG is much better, because EVERYTHING gets encoded, not cut-then-encoded like MP3.

      And for those of us that would rely upon pitch-shifting of compressed files (rare but happens) OGG is superior.

      And pretty much that is what gives OGG the advantage over MP3. My pitch-shifted splash cymbals don't sound underwater in OGG compared to MP3.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    123. Re:Excellent. by midnaz · · Score: 1

      Apparently Webkit uses gstreamer now, so Chrome already supports Theora and Vorbis (at least on Linux)

      Webkit doesn't support anything. They have the HTML5 video tag parsing, and everyone who uses Webkit gets to "bring their own codec." Apple uses Quicktime, webkit-gtk uses gstreamer, Chromium uses ffmpeg (shipped with H.264 and Ogg on Chrome, only with Ogg on Chromium).

      and Firefox is capable of using gstreamer (there has been a patch available since 3.0), so they could theoretically support anything.

      But will they? I don't think they are going to ship with gstreamer support anytime soon. And that leaves Windows and Mac; DirectShow on Windows XP doesn't have support for H.264.

      but with some work we could probably convince Apple to make Theora/Vorbis codecs ship by default.

      Hah, that's hilarious. When hell freezes over.

  2. Adobe... by Dan+East · · Score: 3, Interesting

    I shed not a tear for you.

    --
    Better known as 318230.
    1. Re:Adobe... by MrNaz · · Score: 3, Insightful

      Don't. IE will not support HTML5 for many years, if history is anything to go by, making Flash at least a fallback requirement for any remotely popular video site for the forseable future.

      --
      I hate printers.
    2. Re:Adobe... by Toonol · · Score: 4, Insightful

      And you can't write videogames in HTML5. Flash will be around for a while.

      The real problem with Flash, stupid menu widgets, irritating ads, and non-html website frontpages, won't disappear until sites can recreate equally annoying equivalents via some other method.

    3. Re:Adobe... by Anonymous Coward · · Score: 0

      You can write videogames in html5. And SVG.

    4. Re:Adobe... by Anonymous Coward · · Score: 0

      How? Any examples?

    5. Re:Adobe... by .tekrox · · Score: 4, Insightful

      Javascript.

      Don't whine that it's slow - Chrome, Opera, Safari and Recently firefox now have very fast javascript engines.
      Don't whine its not powerful enough - ActionScript (Flash Scripting) is Javascript. And Flash isn't very quick at interpreting it either...

    6. Re:Adobe... by JackAxe · · Score: 1

      You wouldn't call Java JavaScript. The same can be said about ActionScript 3, which is actually more like Java. What you say holds true for older version of AS though.

    7. Re:Adobe... by iapetus · · Score: 2, Informative
      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    8. Re:Adobe... by abhi_beckert · · Score: 1

      Modern browsers have JiT compilation for fast execution and hardware accelerated 3D graphics... I would argue html5 is *better* for games than flash

    9. Re:Adobe... by Anonymous Coward · · Score: 0
    10. Re:Adobe... by BikeHelmet · · Score: 1

      Plus, most javascript doesn't have huge memory leaks. You can do things that leak, like deleting and recreating functions over and over - but mostly it should be okay.

      Flash games tend to spiral upward in memory and CPU usage. I remember on my old Athlon XP, games at ArmorGames would start smooth, but get choppy within 20 minutes. I had to restart the browser to fix it.

    11. Re:Adobe... by TheRaven64 · · Score: 1

      Microsoft has said that IE will support HTML5 in the next version. Given that Microsoft already has a working H.264 implementation that ships as part of Windows 7's implementation of DirectShow, and that Flash is a competitor's product, I don't imagine that supporting the video tag will take them very long.

      By the way, one of the design goals for HTML5 was that it should be possible to implement all of it via plugins and stylesheets for legacy browsers. When the spec is a bit more finalised, expect to see an HMTL5 plugin for IE if MS doesn't get its act together.

      --
      I am TheRaven on Soylent News
    12. Re:Adobe... by raynet · · Score: 2, Informative

      ActionScript 3 is one dialect of ECMAScript as is Javascript and JScript. Nothing really to do with Java.

      --
      - Raynet --> .
    13. Re:Adobe... by jez9999 · · Score: 1

      Don't. IE will not support HTML5 for many years, if history is anything to go by, making Flash at least a fallback requirement for any remotely popular video site for the forseable future.

      The other thing is: does HTML5 support live streaming video? Flash does.

    14. Re:Adobe... by Anonymous Coward · · Score: 0

      er that sucks actually.

      i thought it was the height of delusion to think that flash is going to lose out when it comes to video - to anyone who understands the issues here it obviously isn't.

      this is truly exceptional though, we don't need flash for games...? we can use svg and javascript? get a grip.
      you'll be telling me that flash isn't that widely distributed next. wtf are you people on?

      where is the appeal of attaching yourself to no-hope causes that are not only pointless but betray your complete ignorance on the matter?

      where is the pay-off for this kind of group think?

      unless adobe and the rest of the world come here and say "oh slashdot is right, flash is a bad thing" you will just be left here bleating at each other. irrelevant and out of touch as ever.

    15. Re:Adobe... by iapetus · · Score: 2, Informative

      He asked for an example of a game in HTML5. I provided an example of a game in HTML5. A simple transaction.

      Ironically it's you who's left over bleating to yourself, working yourself up into a frothing rage over things that nobody ever said. You might want to check your caffeine dosages.

      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    16. Re:Adobe... by vitaflo · · Score: 1

      "And you can't write videogames in HTML5. Flash will be around for a while."

      HTML5 is not just the video tag (as much as people seem to think it is). It also includes things like the canvas element, that, when combined with JS, can certainly make games possible. There really is little reason to use Flash at all anymore.

    17. Re:Adobe... by Hurricane78 · · Score: 1

      Wrong. There is no reason you can’t write games in HTML5.

      There are 3 parts needed to create a video game:
      - A canvas. Check. <canvas> And SVG adds a whole vector library too.
      - A programming language. Check. JavaScript. In fact Flash’s ActionScript is just JavaScript with data types.
      - Enough performance. Pure JS should already be faster than ActionScript. Only the rendering is a bit slow right now. Which will change soon.

      In fact, with WebGL coming soon, HTML5/JS will seriously beat Flash out of the water in terms of what it can do. Because as soon as the textures, models and shaders are loaded into the graphics card, rendering last-generation graphics quality will perform just as well as with pure C/C++. (Only world updates, events, etc, will be slower.)

      Look at this, to see what can be done nowadays:
      http://people.mozilla.com/~prouget/demos/tracker/tracker.xhtml
      I wouldn’t call this a lightweight algorithm at all.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
  3. Here that wooshing sound, Firefox? by Endymion · · Score: 4, Insightful

    That's the sound of you getting passed by.

    I'm a total GNU fanboy most days, and generally agree with the moral move they are trying to make with OOG formats, but in this case it is a losing strategy. H264 video has gotten a momentum that is hard to break, similar to how MP3 got a momentum in the past. It has nothing to do with technical features, morals, licensing, or other commonly-argued things. Instead, it's about a critical-mass of popularity. H264 video the new pop thing, even in cases where people don't even know terms like "H264".

    By not finding a way to make video work properly, Firefox is saying they want to be left behind. No, I highly doubt people like google or others will re-encode video into Theora. They will make the business decision that not only is it a lot of work, it's not necessary as firefox is supported with Flash.

    If the Firefox people want to make a good moral stand with this issue, they should pull something similar to the crypto situation and make an "international" version. That version could serve as an embarrassment to the restrictive patent system, and a useful political talking point. At a minimum, though, they should simply remove all codec processing form the project, leaving that particular can of worms to an external project (gstreamer? embed mplayer/vlc/other? some new project created specifically for this purpose?).

    I love firefox. I really do. So please don't choose to be non-player in the video arena!

    --
    Ce n'est pas une signature automatique.
    1. Re:Here that wooshing sound, Firefox? by Anonymous Coward · · Score: 0

      If someone wants to pay for the stupid H.264 licensing issues to go away, then I'm sure Mozilla/Firefox would quickly gain support. That's unlikely to happen though. :/

    2. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      Easy to speak when it's not your ass on the line for patent infringement.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    3. Re:Here that wooshing sound, Firefox? by Endymion · · Score: 1

      While I'd love it if the patent/licencing issues could be easily fixed like that, I seriously doubt it will ever be the case. In the world of video, more than most other fields, patents have become a total minefield. Even in things like "patent free" Theora, companies are still reluctant to implement them for fear of submarine patents.

      So I suspect we will have this problem in one form or another no matter what.

      So Firefox should sidestep the issue by externalizing it. This is not idea, but it's practical and strategic. Firefox is riding a powerful wave of popularity right now, and they need to keep that momentum going to win the larger war. Pop culture these days means things like youtube, and if you don't work perfectly with youtube (and hulu, and vimeo, and related sites), you will be ignored by the masses.

      --
      Ce n'est pas une signature automatique.
    4. Re:Here that wooshing sound, Firefox? by javilon · · Score: 2, Insightful

      Mozilla should just link to the distribution's provided ffmpeg and just let you decide what codecs you compile in. That would mean that at least in FOSS operating systems the problem is sorted.

      That would also mean less code to manintain, and to give an advantage to FOSS operating systems.

      --


      When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    5. Re:Here that wooshing sound, Firefox? by onefriedrice · · Score: 1

      Mozilla's ass wouldn't be on the line if they would just pay for the necessary licenses from MPEG LA like everybody else.

      Otherwise, Firefox will become the browser for those who just really like Flash.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    6. Re:Here that wooshing sound, Firefox? by jvillain · · Score: 2, Interesting

      It has every thing to do with licensing. It is unreasonable to expect a nonprofit group to fork out millions of dollars to give you a free product. If you want to start paying for FireFox maybe they can do some thing for you.

      Audio and video are the only arrows left in the quiver of the proprietary companies. I think once companies start to realize that it is safe to do HTML5 you will see companies that say screw it we don't feel like paying these fat fees any more when we can use some thing free instead. Up until now they really didn't have much of a choice they were stuck with Flash. Now they have options It is simple business that if some one does some thing that lowers their costs you have to do some thing to lower yours. So as companies start moving towards lower cost and free codecs the others are going to have to follow them.

      I do have to say that things are going to get interesting for Google going forward. They have been at war with Microsoft, they have already started a war with Apple and they are ramping up the war with the open standards and open source communities. Soon they aren't going to have any friends left.

    7. Re:Here that wooshing sound, Firefox? by Endymion · · Score: 3, Interesting

      This is why I suggest they either:
        1) Make it a non-USA release, similar to PGP/PGPi in the past. This would be if they wanted to take a stand, and make lots of activist-style press releases on the subject. It would also probably be more effective than trying to talk everybody into using Theora.
        2) Externalize the issue, by using an external program instead. That way they aren't decoding any video, and are totally safe from patent issues.

      Option #2 is recommended, as a pragmatic decision.

      --
      Ce n'est pas une signature automatique.
    8. Re:Here that wooshing sound, Firefox? by Endymion · · Score: 1

      It is likely not legal for them to pay for a license directly. Such a license would likely require them to not release the patented code openly, like they are required to do for the GPL.

      Such a license would also not pass to others, so Ubuntu/etc would not be able to distribute the licensed firefox.

      --
      Ce n'est pas une signature automatique.
    9. Re:Here that wooshing sound, Firefox? by arose · · Score: 1
      This is not idea, but it's practical and strategic.

      Practical? What are you going to do, put a yellow bar on top when people visit a site with h.264 video that says: "Sorry, due to patent restrictions we can't play this video, we would tell you how to work around this issue, but it might expose us to lawsuits, happy hunting"? You can't have a polished user experience without transparent handling here, and you can't have transparent handling without exposing yourself (and Firefox isn't small enough to fly under the radar).

      Any sort of back room deals with MPEG LA would basically remove one option from the triple license, thus alienating a huge chunk of the tech savvy base that made the browser into what it is. If it was me I'd take the chances by being marginalized due to lack of codec support instead of being marginalized due to brain drain to webkit and possible replacement as the default browser in major Linux distributions. Brainshare matters, especially with Chrome up and coming.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    10. Re:Here that wooshing sound, Firefox? by Endymion · · Score: 2, Insightful

      It's unreasonable to expect pop culture to shift because it's choice is inconvenient.

      Trying to change perceptions like that didn't work with Vorbis-vs-MP3, and it won't work here either.

      --
      Ce n'est pas une signature automatique.
    11. Re:Here that wooshing sound, Firefox? by Endymion · · Score: 3, Insightful

      that WOULD be an improvement over what they are doing now, which is to simply not play anything!

      The proper response, though, is not to put up some sort of error message, but to use an external solution such as mplayer, ffplay, vlc, gstreamer, or whatever, and make it "someone else's problem".

      Chrome up and coming is an even bigger issue because of this. If it works well with youtube, and firefox doesn't, then firefox will lose dramatic market share to Chrome.

      --
      Ce n'est pas une signature automatique.
    12. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      Make it a non-USA release, similar to PGP/PGPi in the past.

      Not with being incorporated in the US. They'd have to at least double overhead to set up a separate company/organization to distribute this version, since explicitly doing it under the US entity would be considered exporting a product, and letting the community do it would cut of the revenue from Google and confuse less tech savvy users.

      Option #2 is recommended, as a pragmatic decision.

      I elaborated on this above.

      Basically I consider that the pragmatic and the idealistic approach leads down the same road in this case, even if it doesn't seem to at first glance (as is often the case in FLOSS). Since Chrome also supports Theora and support in Opera is on the way (that covers all major, cross platform browsers as well as all Windows browsers with video tag support), the strategy is basically the same as in the "take back the web" days, convince the people who haven't/are not likely to invest in h.264 to take advantage of the feature (with fall backs where appropriate) and see if Microsoft's and Apple's hands can be forced.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    13. Re:Here that wooshing sound, Firefox? by Anonymous Coward · · Score: 0
      OOG formats

      Uh oh, looks like someone's going to get their head broken with an open source CD...

    14. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      The proper response, though, is not to put up some sort of error message, but to use an external solution such as mplayer, ffplay, vlc, gstreamer, or whatever, and make it "someone else's problem".

      The "someone else" will be the user, if they don't have the framework of choice set up, that's the problem. Youtube (or any other major site with a significant portion of IE hits) is not about to drop flash support any time soon. On Windows this is handled transparently for Firefox, so no breakage occurs. On Linux the Gnash, swfdec and Adobe (with the help distro maintainers) will make it work one way or another with minimal headache for Firefox developers. Yes, technically part of that runs into the same old patent problems, but they are the same as the ones in your suggestion.

      The upside on the other hand is that Firefox is playing it by the book and can work on support for truly free solutions.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    15. Re:Here that wooshing sound, Firefox? by timmarhy · · Score: 3, Informative

      here's the thing - something that's genuinely new and required real effort like H264 to develop, patenting it is a valid use for the patent system. and if you look at the licensing terms for h264 is insanely fair and cheap - your looking at only $100,000 for a service with 1,000,000 subscribers, and thats only if your a commercial entity. i dare say if your running a website that has a subscription of over a million people you can afford $100,000 for the core technology that under pins your operation. if you can't, Your Doing It Wrong.

      --
      If you mod me down, I will become more powerful than you can imagine....
    16. Re:Here that wooshing sound, Firefox? by BZ · · Score: 1

      > Such a license would likely require them to not release the patented code openly

      That's actually not a problem as long as you avoid GPLv3 (and I'm fairly certain that it's not a problem with MPL in particular). But IANAL, etc.

      > Such a license would also not pass to others, so Ubuntu/etc would not be able to
      > distribute the licensed firefox.

      This, on the other hand, is a much bigger concern.

    17. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      It worked with PNG, even if it took a while. And it worked with Vorbis to a limited extent (there is another option when you need it, there is reasonable hardware support and the lives of game and other developers have been made easier), but that battle wasn't about the web before HTML5 and Firefox 3.5.

      Yes, it's a slow process, but with h.264 there is are 15 years or so where it can make a difference, this was not the case with PNG as the patent covering GIF creation expired or MP3, which had a bigger head start in a different marketplace.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    18. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      GPLv2 is a problem as well if it ever comes down to it, see section 7.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    19. Re:Here that wooshing sound, Firefox? by smash · · Score: 2, Interesting

      How about a plug-in architecture? That way we aren't stuck with shitty 2010 video formats in the www of 2015, either.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    20. Re:Here that wooshing sound, Firefox? by Endymion · · Score: 1

      Sure, in 15 year or whatever, it'll be trivial. Most software will be able to implement all of this with minimal hastle.

      But in the mean time, the war against other things like Flash, Silverlight, IE, and open-web-standards in general will be lost.

      --
      Ce n'est pas une signature automatique.
    21. Re:Here that wooshing sound, Firefox? by onefriedrice · · Score: 1

      Naw, there's obviously a way to get it done, and it's not that difficult either. It's not really an issue that's very different from distributions allowing users to install "non-free" packages.

      Google licenses h.264 for use in Chrome. Obviously that doesn't extend to Chromium, but it doesn't really need to. It's clear that if you want h.264 support, you'll need to run the Google binary since they've paid the royalties. There's no reason Mozilla couldn't license h.264 for their officials builds. Ubuntu/etc can continue to include their own completely free, pseudo-branded Firefox build and simply put up a "non-free Firefox" package in a repository. It's been done many times for other useful, non-free packages... it's not like this is some new process we're figuring out for the first time.

      Furthermore, the GPL isn't an issue here because Mozilla is the copyright holder of the codebase. That means they can build and distribute a binary mixed with patented/proprietary code, though distributing that source code would clearly be at odds with both the GPL and the h.264 license conditions. However, as the copyright holder, they are not bound by the restrictions of the GPL, including the restriction of binary distribution. The GPL is a license and licenses are for licensees. They are not required to release all the source code they link with their GPL-licensed code. Indeed, Mozilla doesn't even release their binaries under GPL conditions, but rather under their own MPL (see bottom).

      None of this may be convenient, but it is abundantly clear to most of us (for better or worse) that h.264 has won for now. Mozilla may think they have some clout because of their market share, but at the end of the day, it's the likes of YouTube and other online content providers that really have the last word, and they have chosen h.264.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    22. Re:Here that wooshing sound, Firefox? by Rocketship+Underpant · · Score: 3, Insightful

      I agree 100%. Mathematical algorithm patents are not recognized in most countries outside the US, so make an international Firefox version that only visitors who claim to be outside the US can download.

      --
      He who lights his taper at mine, receives light without darkening me.
    23. Re:Here that wooshing sound, Firefox? by Dr.+Spork · · Score: 1

      Yeah, that's interesting and awful. And to make the licensed portion into some sort of a binary-only library that plugs into Firefox would defeat the big advantage of HTML5, which is that it doesn't need extra plugins.

      So isn't there a way in which Firefox could call the relevant codec installed on the computer through the HTML5 "video" tag and use that codec to play back the video? I mean, every Windows machine already has its own h246 decoder. Since we already own that decoder license thanks to Microsoft, why can't Firefox just take advantage of it? Obviously, the FF on other OSes would need different solutions, but just about every modern computer already can decode h264 and I have to think that FF could find a way to take advantage of this. But I don't know much about how the "video" tag is implemented to know whether this is possible. I assumed it was, because people talk about hardware-accelerated decoding, etc. Another question I have is about whether Chromium also can't play h264. Does anyone know?

    24. Re:Here that wooshing sound, Firefox? by onefriedrice · · Score: 1

      You guys are forgetting that Mozilla owns the copyright to the code, and none of the 3rd-party code they use is GPL. As owner, they are the licensor, and the licensor is not bound to the same conditions as the licensees. Ultimately, they will have to include h.264 support in their official binaries just like Google has done with Chrome. The rights won't extend to those who build custom binaries like Ubuntu, but that's what the distinction between free and non-free is for.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    25. Re:Here that wooshing sound, Firefox? by onefriedrice · · Score: 1

      Another question I have is about whether Chromium also can't play h264.

      Google only licensed h.264 for Chrome. I believe you can get Chromium to play h.264 by making it use a version of ffmpeg with that codec built-in, but that's certainly not something Google distributes.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    26. Re:Here that wooshing sound, Firefox? by eihab · · Score: 2, Insightful

      it's the likes of YouTube and other online content providers that really have the last word, and they have chosen h.264

      YouTube is not the only video site in town. DailyMotion went with Theora and others may follow that example.

      The web is supposed to be open, if we kowtow to patent encumbered formats just because Google says so, then I'm afraid the last 10 years we have spent trying to get up from under Microsoft and the browser wars would have been a complete waste.

      We're basically going to head back to "This site is best viewed by X or Y", only with different values for X and Y.

      The reason a "plug-in" solution is redundant stems from the fact that you can already serve H.264 content using plug-ins _today_. The whole point of the <video> tag was to standardize and open up the mess video has become (Flash, Quicktime, WMP, Silver light, etc.).

      If you shun browser makers (and content producers) with patent encumbered formats, then you might as well call Flash a standard and be done with it.

      It amazes me that the general sentiment against MS's closed-"open" office formats was highly negative (which was well deserved), but when Google basically says F-U to What-wg and does whatever it wants anyway with a patent encumbered format then Firefox is at fault for not paying for royalties.

      The day YouTube moves to HTML5 and only serves H.264 content (which will not happen any time soon, thanks IE) is the last day I'll visit that site. Thanks, but no thanks, I'm not going back to the dark ages of the web to watch a dog skate-board.

      --
      If you can't mod them join them.
    27. Re:Here that wooshing sound, Firefox? by LordVader717 · · Score: 1

      That doesn't stop the licensing authorities collecting fees and suing left right and center. Almost the entire industrialized world upholds codec patents and indeed many of the patent holders are European companies.

    28. Re:Here that wooshing sound, Firefox? by micheas · · Score: 1

      Mozilla does not own all the code in Firefox, otherwise their would not have been such a todo about getting all the developers to allow the triple licensing.

    29. Re:Here that wooshing sound, Firefox? by CowboyBob500 · · Score: 1

      Citation? Whilst many of the patent holders are European companies, I'm pretty sure that licenses are only payable in the US. Wasn't it the case that Fraunhofer only required license fees in the US for MP3? They sold their own implementation of the MP3 codec elsewhere yes, but independent implementations were license free as I recall.

    30. Re:Here that wooshing sound, Firefox? by drtsystems · · Score: 1

      There is nothing stopping exactly what you say which is why all this hullabaloo is stupid. Directshow (or whatever it is called now in windows 7), quicktime in mac, and mplayer in linux. And I'm sure third parties would begin distributing builds with VLC built in so 10 year old operating systems (cough Windows XP cough) could be supported without worrying about making sure the correct codecs are installed.

      Added bonus would be that hardware acceleration is supported out of the box, in windows 7 and mac at least, because quicktime and win7's codecs support it.

    31. Re:Here that wooshing sound, Firefox? by Anonymous Coward · · Score: 0

      Mathematics should not be patentable.

    32. Re:Here that wooshing sound, Firefox? by FrostedWheat · · Score: 1

      It has nothing to do with technical features, morals, licensing, or other commonly-argued things. Instead, it's about a critical-mass of popularity.

      Unfortunately the real world disagrees.

    33. Re:Here that wooshing sound, Firefox? by tepples · · Score: 1

      How about a plug-in architecture?

      How about getting the user's account pwned through a security hole in a poorly written plug-in codec that was never meant to deal with intentionally malformed video files?

      That way we aren't stuck with shitty 2010 video formats in the www of 2015, either.

      We're already stuck with shitty 1994 image formats because none of the major web browsers can display MNG videos* or JPEG 2000 images. There are nearly decade-old bugs in bugzilla.mozilla.org that are RESOLVED WONTFIX.

      * MNG is a replacement for animated GIF. Unlike more popular video codecs such as MPEG-4 ASP, H.264, or Theora, it's designed specifically for lossless reproduction of line art animations.

    34. Re:Here that wooshing sound, Firefox? by TheRaven64 · · Score: 2, Insightful

      PNG was easy. Want alpha channels? Use PNG. Want better compression? Use PNG. Want more than 256 colours? Use PNG. Oh, and by the way, it's royalty free so you won't get hit by those fees that everyone's starting to have to pay for producing or reading GIFs.

      Theora is hard. Want good quality? Use H.264. Want multiple implementations optimised for different profiles? Use H.264. Want hardware accelerated playback on mobile devices? Use H.264. Oh, and there's a small license fee that you'll have to pay if you live somewhere with software patents.

      VC-2 is a bit easier to sell. Similar quality to H.264, lossless profile, hardware acceleration close to market, royalty free. Even then it's not quite clear that it's superior because you can play back reasonable quality H.264 on a much lower-spec'd machine and the current generation of handhelds all come with H.264 decoding (and, in some cases, encoding) hardware, not VC-2 hardware.

      --
      I am TheRaven on Soylent News
    35. Re:Here that wooshing sound, Firefox? by TheRaven64 · · Score: 1

      The BBC pays for an H.264 license, even though software patents are not valid in the UK. Most of the time, it's done indirectly. The license fee is charged to the company dstributing the CODEC. A recent ruling means that US companies have to pay for licenses for distributing things that infringe US patents even in foreign countries where the patents are not valid, so, for example, Apple has to pay for every copy of QuickTime (up to the cap), irrespective of which country the end user lives in.

      --
      I am TheRaven on Soylent News
    36. Re:Here that wooshing sound, Firefox? by Truekaiser · · Score: 1

      I have the latest build able version of chromium installed. 4.0.295.0 and it won't work.

    37. Re:Here that wooshing sound, Firefox? by DJRumpy · · Score: 1

      That nails it exactly. It's kind of amusing reading all of these posts about the technical merits of OGG, how licensing fees suck, exporting international versions, ad-nauseum, but in the end, Firefox needs users, and basic users don't care about any of these things. They just want a browser that works.

      As far as I know, there are no major sites yet that force you to use HTML5 and h.264. Unless someone specifically looks for the /html5 on youtube, they won't even notice a difference. I DO think the FF folks should be in panic mode though. Granted they hold a very large market share and that can't be insignificant to the folks at YouTube, but when a popular site like youtube is flirting heavily with changing standards in such a public way, you have to stop and take notice. It's the epitome of 'viral advertising'.

      That said, why didn't the FF folks see this coming and already have a workaround in place? The writing was on the wall over a year ago (as far back as 2008?) that youtube was experimenting with piping out h.264 instead of flash. Why are they seemingly so unprepared for this?

      If the http://www.youtube.com/html5 address becomes well known, and 'regular' Firefox users get irritated, a switch to Chrome is linked right on the youtube pages they can't view under the beta.

    38. Re:Here that wooshing sound, Firefox? by Anonymous Coward · · Score: 1, Funny

      if you can't, Your Doing It Wrong.

      You're Spelling It Wrong.

    39. Re:Here that wooshing sound, Firefox? by LordVader717 · · Score: 1
    40. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      They just want a browser that works.

      That is exactly the problem, an external package that you can't transparently install due to patent concerns is exactly the opposite of "just works".

      Why are they seemingly so unprepared for this?

      Just because they don't do exactly what you want them to do, doesn't mean they are unprepared. Trying to standardize HTML5 on Theora was step one, and if nothing else brought attention to the issue. Implementing it ASAP was step too, it gives web developers, power users and alike the ability to play with it.

      Now it's time for the trenches of the mindshare battle, they don't need to win youtube, just enough people that Theora can't be conveniently ignored. Do you think it's because of Opera's spoofing that there are hardly any significant IE only sites left on the public internet?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    41. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      PNG was easy. Want alpha channels? Use PNG.

      I can only assume you were not around before IE7 or something like that, because that's how long it took to get proper PNG support (in the form of the alpha channel you tout as a killer feature) all major browsers. It was anything but easy.

      Oh, and by the way, it's royalty free so you won't get hit by those fees that everyone's starting to have to pay for producing or reading GIFs.

      Oh, the MPEG LA is revising their licensing terms as we speak, I don't expect them to drop the price do you? Also, there was never a problem reading GIFs to my knowledge.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    42. Re:Here that wooshing sound, Firefox? by DJRumpy · · Score: 1

      Not to belabor the point, but it does 'just work' on Safari and Chrome. There are no external 'packages' to install or anything of the sort.

      I consider over a year of warning with no implementation in production 'unprepared'.

    43. Re:Here that wooshing sound, Firefox? by cynyr · · Score: 1

      I'm currently giving chromium a shot, but it doesn't support the parents site either. As far as i can tell, despite having 2-3 media players that can play h264 with video decode help from my gpu there is no way to make it work on Linux.

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
    44. Re:Here that wooshing sound, Firefox? by TheRaven64 · · Score: 1

      IE5 for Mac supported alpha channels. IE 5 and 6 on Windows supported 1-bit alpha. This was exactly the same that they supported for GIFs, so using PNG was always at least as good, quality wise, as GIF. The only thing GIFs did that PNGs didn't was animation. For everything else, PNG was either better or no worse. This is not the case with Theora with respect to H.264.

      --
      I am TheRaven on Soylent News
    45. Re:Here that wooshing sound, Firefox? by BZ · · Score: 1

      That's the subscription side of the licensing, you're correct. The big wildcard is the "broadcast" side, also known as "put that one video on my blog". It's free through the end of this year; after that we'll see what the licensing terms look like.

    46. Re:Here that wooshing sound, Firefox? by BZ · · Score: 2, Informative

      > I consider over a year of warning with no implementation in production 'unprepared'.

      You're assuming that the goal was to support H.264. That's not in fact a goal at the moment, because it's seen as detrimental to the future of video of the web (though of course beneficial to several big companies today).

    47. Re:Here that wooshing sound, Firefox? by Anonymous Coward · · Score: 0

      who the f*** are you to tell us what the "real world" want or doesn't want?

      how many people are using flash anyhow? is anyone really going to notice if youtube stop using it...?

    48. Re:Here that wooshing sound, Firefox? by BZ · · Score: 1

      > and make it "someone else's problem"

      That can almost work ok until this someone else's code you have no control over ends up with a security hole that's being exploited. Then what courses of action do you have?

    49. Re:Here that wooshing sound, Firefox? by DJRumpy · · Score: 1

      I'll end up burning some Karma here, but so be it. To your mind, their plan is to bury their heads in the sand in regards to h.264 and pretend it doesn't exist? That obviously won't happen, and the bug reports indicate they don't believe it will either. They are aware of the issue but they don't have a production ready solution.

      OGG has already lost the war (was there ever really one to begin with)? If Mozilla was to choose to go down that path, they certainly could (one of the benefits of FOSS), but they would become irrelevant by doing so considering the other big players already support it in some fasion.

      It's noble to aspire to such lofty goals, but realistic to understand that they will eventually have to support all of the codecs in the HTML5 standard, not just those that they deem worthy.

      To my mind, this is no different than MPEG, MPEG-2, AC3, MP3, AAC, H.264, DivX, etc. Although FOSS might dislike their licensing and patents and strive to create reverse engineered solutions, you'll find it supported in one way or another in every flavor of Linux. It's just not realistic to think otherwise.

    50. Re:Here that wooshing sound, Firefox? by ObsessiveMathsFreak · · Score: 1

      Chrome up and coming is an even bigger issue because of this. If it works well with youtube, and firefox doesn't, then firefox will lose dramatic market share to Chrome.

      WTF? It's just the video tag, a new way to play videos on a site where videos already play.

      I don't know where all the crowing against Firefox is coming from in this thread, but people need to put things in perspective. Most users will not even notice that videos play differently across browsers, let alone want to switch over this fact. While IE is still using flash to play video, YouTube and the rest cannot drop the platform and firefox will always fall back on that. Users won't notice. Their videos will keep playing.

      Chrome, chrome, chrome. They made a big splash, but not very many people got wet. They certainly didn't thrill me enough to relish the prospect of MPEG-LA and their patents turning into the next Unisys and sinking every browser on the planet. Yes, H264 is technically better than OGG. But JPEG2000 was in the same position against JPEG, and it was--correctly--dropped like a stone due to patent issues.

      The video tag is dead. Patent encumbered formats are practical impossibility, not only for FOSS browsers, but even for smaller commercial ones like Opera. If even a company like Opera wasn't going to come to the table over this, you know that something stank about MPEG-LA and their future position on licensing. Apple and Google have other concerns which they judge to override their patent concerns. But we'll see the proof of this in the coming years when MPEG-LA decides to "leverage" its "intellectual property rights". There's a story about a frog and scorpion which might offer insight into this issue.

      --
      May the Maths Be with you!
    51. Re:Here that wooshing sound, Firefox? by ObsessiveMathsFreak · · Score: 1

      Mathematical algorithm patents are not recognized in most countries outside the US,...

      ...yet.

      --
      May the Maths Be with you!
    52. Re:Here that wooshing sound, Firefox? by BZ · · Score: 3, Informative

      > They are aware of the issue but they don't have a production ready solution.

      "They" (we) are in fact aware of the issue, and feel that H.264 as the "standard" web video format is in fact detrimental to the long-term health of the web and to Mozilla's mission (which is not to make a web browser; the web browser is a means to an end).

      > they will eventually have to support all of the codecs in the HTML5 standard

      The standard doesn't specify any codecs.

    53. Re:Here that wooshing sound, Firefox? by yabos · · Score: 1

      To play Flash video, the USER has to install the Flash plugin. I don't see how it is any different if they have to install a different plugin to play H.264 video.

    54. Re:Here that wooshing sound, Firefox? by DJRumpy · · Score: 2, Informative

      True. Bad choice of words. I should have said 'supported by' instead:

      "On October 17, 2007, the World Wide Web Consortium encouraged interested people to take part in a "Video on the Web Workshop", held on December 12, 2007 for two days.[10] A number of global companies were involved, submitting position papers.[11] Among them, Nokia's paper[12] states that "a W3C-led standardization of a 'free' codec, or the active endorsement of proprietary technology such as Ogg by W3C, is, in our opinion, not helpful." Ogg's codecs are licensed under the BSD open source license, and are therefore not proprietary in any accepted sense of the word. Apple Computer have also opposed the inclusion of Ogg formats in the HTML standard on the grounds that H.264 performs better and is already more widely supported, citing patents and the lack of precedents of "Placing requirements on format support", even at the "SHOULD" level, in HTML specifications.[13]

      In response to such criticism, WHATWG has cited concerns over the Ogg formats still being within patent lifetime and thus vulnerable to unknown patents.[14] Such submarine patents may also exist for non-free formats like MP3 and H.264. Also, the AVC patent licensing policy is subject to change in a not-yet-clear manner.[15]
      [edit] HTML5 turns neutral"

      On December 10, 2007, the HTML 5 specification was updated[16], replacing the reference to concrete formats:

              User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format.

      with a placeholder:[17]

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

    55. Re:Here that wooshing sound, Firefox? by yabos · · Score: 1

      "How about getting the user's account pwned through a security hole in a poorly written plug-in codec that was never meant to deal with intentionally malformed video files?"

      Kind of like what happens with Flash today? I'm not so certain that whatever Mozilla would include with Firefox would necessarily be any better. They are constantly patching security holes in Firefox just like every other piece of software.

    56. Re:Here that wooshing sound, Firefox? by BZ · · Score: 1

      Right. So the key part is that at the moment all codecs are "supported" by html5...

    57. Re:Here that wooshing sound, Firefox? by DJRumpy · · Score: 1

      Just not supported by the browser ;) Agreed.

    58. Re:Here that wooshing sound, Firefox? by BZ · · Score: 1

      Right. And more to the point, it's not realistic to have a browser support all codecs "supported" by the spec. Have to pick and choose somehow (if only by picking which system libraries one uses).

      It's too bad the whole thing is such a mess.... :(

    59. Re:Here that wooshing sound, Firefox? by stdarg · · Score: 1

      The reason a "plug-in" solution is redundant stems from the fact that you can already serve H.264 content using plug-ins _today_. The whole point of the tag was to standardize and open up the mess video has become (Flash, Quicktime, WMP, Silver light, etc.).

      But the plugins used today require tag markup specific to each plugin to get them to work. For instance if you want to embed quicktime in your page to play a movie, you do something like

      [object classid="clsid:02BF25D5..." ...]
      [param name="src" value="sample.mov"]
      [/object]

      If another user doesn't have quicktime, the browser isn't going to know that the object tag with clsid 02BF25D5... can theoretically be mapped to a different set of markup to show the movie with flash, or ffmpeg, or whatever.

      The point of the video tag is (or should be) simply to get rid of that external program specific markup and let the browser figure out how to handle the video at runtime based on its configuration, not to dictate how the browsers should be coded. Whether the browser implements a minimal set of video formats as a statically linked library, or whether it uses plugins, or whether it just replaces the video tag with an embedded flash video, it doesn't matter. The standard should specify the interface, not the implementation.

    60. Re:Here that wooshing sound, Firefox? by stdarg · · Score: 1

      The default ffmpeg implementation shipped with chromium doesn't contain encumbered codecs. I don't know if you're using a package system, but in Ubuntu there's a package called chromium-codecs-ffmpeg-nonfree that you can install to play h264 video. I guess there's a way to do it in the build system too -- I doubt it's as easy as setting a configure option though.

    61. Re:Here that wooshing sound, Firefox? by Anonymous Coward · · Score: 0

      Get the hell outta here. Region codes for software?

      I despise IP region locking. It's censorship and discrimination, and furthermore, unenforceable.

      The fact that such brainless measures are unenforceable will then subsequently be unacceptable to brainless policymakers, who will then put an increasingly elaborate censorship infrastructure into place.

      Hello vicious circle?

      I have a better solution: how about we ignore the exponentially growing number of laws created by corporations for their own benefit and do a little "I am Spartacus"? Or would you rather continue this cat and mouse game until the lethal end?

    62. Re:Here that wooshing sound, Firefox? by snadrus · · Score: 1

      Ideals other than GNU:
      Unix: Do 1 thing & do it well
      When I found the codec would be *in* Firefox rather than OS libraries, that was trouble. Firefox broke sensible rules right there.

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
    63. Re:Here that wooshing sound, Firefox? by PybusJ · · Score: 1

      Others have commented on the problems mozilla have with licensing H.264 decoder distribution. Maybe that could be worked round by relying on a system codec (which licensed or not is the distro/user's responsibility), but there's more to it than that.

      The Mozilla foundation's mission is to help the Internet remain an open and accessible global public resource, not to create the browser with the greatest market share at all cost. The MPEG-LA's mission is to extract as much revenue for their member IP "right's holders" as possible, not to further open video on the web.

      The MPEG-LA charge software suppliers an IP license to distribute a decoder, but they also have a price sheet for the people providing the content.

        - distribute an encoding application they want payment
        - use that application to encode and they want a payment (yep two different licenses for both the supplier and user)
        - charge for your streamed content they want a per stream payment

      Now, as is sensible strategy, they aren't enforcing their charges for internet streaming at the moment. But the current licensing period ends 31st Dec 2010, and the rights holders will want more next time round.

      If H.264 works everywhere and becomes the only standard for video on the web, then the web becomes less open and accessible for everyone publishing content.

      Now I've no idea what Google pay in licensing for streaming youtube, and what their view is of what they'd have to pay in the future, but they have recently acquired the company responsible for the VP7 and VP8 codecs, so it looks like they do value access to a codec not controlled by the MPEG-LA.

      Google (youtube) probably support only H.264 right now on technical merits, they (Chrome) are quite happy to support ogg/theora playback. I'd not be surprised to something new come out from them using the codecs (and people) they got from On2 this year.

      Apple are MPEG-LA rights owners; they have no interest in any open AV formats on the web and will probably not implement anything else unless market forces mean they have to.

      Mozilla avoid H.264 on licensing cost and support for openness.

      Opera avoid H.264 on licensing cost grounds.

      Microsoft just wish HTML5 would go away and you'd start using Silverlight (and upgrade to Windows 7 too, please).

      There are good arguments for not supporting H.264, at least not until a viable open alternative is widely supported too.

    64. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      Firefox can keep completely out if it's just another plugin. Not even a shadow of legal doubt and no extra manpower to maintain a codec back end that they can't even tell users to install.

      It's also sending a strong signal to web developers that the push for a free-for-all web infrastructure is over. That is not how Firefox gained it's market share...

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    65. Re:Here that wooshing sound, Firefox? by sznupi · · Score: 1

      ...
      Mozilla avoid H.264 on licensing cost and support for openness.

      Opera avoid H.264 on licensing cost grounds. ...

      Presenting this like Opera doesn't care about open web is insincere. Opera actively pushes for a web accessible to everybody (even includes many classes of devices usually omitted), proposed tag, were behind CSS, had probably one of the most strict "standards-only" rendering approach.

      http://www.opera.com/company/vision/
      http://my.opera.com/core/blog/2009/12/31/re-introducing-video

      --
      One that hath name thou can not otter
    66. Re:Here that wooshing sound, Firefox? by arose · · Score: 1

      Please review the thread of why h.264 without external packages is not viable. There is no way to "prepare" for Apple paying to their patent interest (they have a patent in the MPEG LA pool for h.264, which at the very least means they have a good legal backing in cases of submarines and probably royalties) any better.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    67. Re:Here that wooshing sound, Firefox? by sznupi · · Score: 1

      ...and then we'll be able to tell they're copying Opera ;)

      (no, seriously: http://my.opera.com/core/blog/2009/12/31/re-introducing-video )

      --
      One that hath name thou can not otter
    68. Re:Here that wooshing sound, Firefox? by tepples · · Score: 1

      What are you going to do, put a yellow bar on top when people visit a site with h.264 video that says: "Sorry, due to patent restrictions we can't play this video, we would tell you how to work around this issue, but it might expose us to lawsuits, happy hunting"?

      That's what it already does for SWF files if you don't have Adobe Flash Player installed.

    69. Re:Here that wooshing sound, Firefox? by Tack · · Score: 1

      I can only assume you were not around before IE7 or something like that, because that's how long it took to get proper PNG support (in the form of the alpha channel you tout as a killer feature) all major browsers. It was anything but easy.

      It's much nicer now, true, but it wasn't a huge problem pre-IE7. You needed to jump through the filter=DXImageTransform.Microsoft.AlphaImageLoader(...) hoop, but things like that were easily handled inside the web framework, or could be automatically "fixed" with a bit of Javascript.

    70. Re:Here that wooshing sound, Firefox? by Dr.+Spork · · Score: 1

      Thanks for your answer. So it seems that this is the sane direction for Firefox developers to go. Why would they even want to bundle their own codecs with the release, if this is possible? Not only does this stir up a useless debate, but it also bloats up Firefox itself. Actually, I can forgive including Theora, since it's not commonly installed on consumer machines. But yeah, 4.0 should definitely be designed to use Directshow codecs on Windows and the relevant VLC or ffmpeg libraries elsewhere.

    71. Re:Here that wooshing sound, Firefox? by smash · · Score: 1

      Plug ins are not necessarily any less secure than having the codec(s) built into the browser. In fact if designed and implemented properly, it could well be more secure - there is NO reason for a rendering plugin to have write access to disk, for example. Plug in vs no plug in, makes no difference. Except maybe its easier to disable an exploitable plugin without killing your whole browser.... which is a good thing.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  4. Flash should be abandoned by Anonymous Coward · · Score: 0

    At least M$ will then finally go under.

  5. Sigh... by snikulin · · Score: 1

    I have tried HTML5 Youtube with Chrome (v.3.0.195.38) about 30 minutes ago.
    Badly pixelated image and no full screen video.
    To me Flash video looks *much* better so far.

    1. Re:Sigh... by clarkn0va · · Score: 1

      That was my experience too. Disappointing. Add to that the fact that most of the videos I found (through somewhat random clicking) were flash-only. I didn't find any HD content in html5 at all, and I'm not really sure why. To me, h.264 is hi def. Hours and hours of 720p and 1080p on my NAS, and 99% of it is h.264 encoded, so what is youtube's hold up?

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    2. Re:Sigh... by micheas · · Score: 1
      The flash videos seem to skip a little more than the html5 videos for me with:

      Chromium 4.0.304.0 (Developer Build 36483)
      WebKit 532.9
      V8 2.0.6.1
      User Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9 (KHTML, like Gecko) Chrome/4.0.304.0 Safari/532.9

      But I don't notice a huge difference between them, other than the videos still play when flash(64bit) crashes, as it tends to do at the end of the day.

  6. Branding over functionality... by RalphBNumbers · · Score: 4, Informative

    It seems that both Youtube and Vimeo have both chosen to use their own custom controls, and disable the default controls native to the user's browser.

    That wouldn't be such a big deal, except for the fact that full screen mode can currently only be entered using those default controls (making full screen mode available via a scripting api is considered a security risk, and thus discouraged by the HTML5 spec). So they're sacrificing that functionality at the alter of branding.

    --
    "The worst tyrannies were the ones where a governance required its own logic on every embedded node." - Vernor Vinge
    1. Re:Branding over functionality... by phizi0n · · Score: 2, Informative

      I'm going to have to put the blame on the browsers for not implementing a "double click the video to go fullscreen" behavior or some sort of key binding. Sites shouldn't have to refrain from branding just to allow the user to go fullscreen, the browser should always provide a method for the user to do it.

    2. Re:Branding over functionality... by Endymion · · Score: 1

      One nice thing about HTML5 over flash: it's much easier to fix such things in greasmonkey or similar tools.

      --
      Ce n'est pas une signature automatique.
    3. Re:Branding over functionality... by LoverOfJoy · · Score: 1

      Don't know about Vimeo but YouTube, at least, lists full screen mode as one of the "restrictions" they are currently working on fixing. Hopefully it comes out of beta faster than the typical Google project.

    4. Re:Branding over functionality... by pbhj · · Score: 1

      [...] full screen mode can currently only be entered using those default controls (making full screen mode available via a scripting api is considered a security risk, and thus discouraged by the HTML5 spec). So they're sacrificing that functionality at the alter of branding.

      If the browsers don't let the user override the branding then they're broken. I should be able to choose to use the native controls for all videos if I wish - just as I can choose to display all websites as green-on-black in a console font if I want to.

    5. Re:Branding over functionality... by Tim+C · · Score: 1

      I don't know about any other browsers, but F11 puts the browser in full screen mode for both Firefox and IE.

    6. Re:Branding over functionality... by Firehed · · Score: 1

      Did you not read the part where he said that turning on fullscreen mode is not part of the native video APIs? I completely fail to see how greasemonkey is going to fix that. Scripts running from localhost don't get special permissions.

      --
      How are sites slashdotted when nobody reads TFAs?
    7. Re:Branding over functionality... by Firehed · · Score: 1

      You can, but it's a pain in the ass - and you have to do it on a per-site basis. Unlike font-faces and styles, the video controls are just generic HTML elements with onclick bindings to manipulate video playback - it's not a simple thing where you just replace a sprite for the controls overlay. You have to manipulate the DOM to remove/hide the custom controls and enable the native controls on the video element; the latter is trivial, but the former is not since every site does that differently. YouTube at least also puts an empty div overlaying the video element specifically to block you from doing that - also easy to deal with, but one of many things that you'll have to fix on a per-site basis.

      --
      How are sites slashdotted when nobody reads TFAs?
    8. Re:Branding over functionality... by phizi0n · · Score: 1

      There's a difference between putting the browser in fullscreen and making the embedded video go fullscreen. What good is having the browser fullscreen if the video is still stuck at the same arbitrary resolution it was before?

    9. Re:Branding over functionality... by phizi0n · · Score: 1

      I think they mean that greasemonkey, firebug, and similar extensions will be able to strip out the branding code, not that they would have any control over scripting the video to go fullscreen. By removing the branding code you get the browser native controls back which hopefully provide a fullscreen mode. With html5 it is also much easier to just find the URL of the video file and download it or open it in another browser tab/window.

  7. its a start by frvfilmslashdot · · Score: 1

    this is alot of comment!!!! for a hot topic,,

  8. I care by Prikolist · · Score: 1

    No, really, I do care. Safari and Chrome, that covers both Mac and Windows users fully, right? That's like 99.99% of the market, right?

    You can't be serious that those browsers put together include only about 10% of users?

    --
    I think Linux isn't better than Windows hence in the slashdot realm I'm a troll
    1. Re:I care by Anonymous Coward · · Score: 0

      cry more....

      you can download chromeframe for your windows IE fetish...

  9. This may not be an apt analogy, but by Skratchez · · Score: 1, Interesting

    if web video formats follow the precedents of home video, porn will be the deciding factor. See Betamax v. VHS, and Bluray v. HD DVD. As goes porn so goes mainstream content providers, right? I should probably do some research into the delivery method of choice in online stag films, but it's just so tedious.

    1. Re:This may not be an apt analogy, but by Anonymous Coward · · Score: 2, Funny

      if web video formats follow the precedents of home video, porn will be the deciding factor. See Betamax v. VHS, and Bluray v. HD DVD. As goes porn so goes mainstream content providers, right? I should probably do some research into the delivery method of choice in online stag films, but it's just so tedious.

      I believe they are currently standardizing on Microsoft Fleshlight...

    2. Re:This may not be an apt analogy, but by Btarlinian · · Score: 5, Informative

      Actually, I'm pretty sure porn went for HD-DVD. So it's not always the right indicator.

    3. Re:This may not be an apt analogy, but by wvmarle · · Score: 1

      I have always heard that the consortium pushing Betamax at the time was actively preventing porn to be released on Betamax.

      In case of Beta/VHS and HDDVD/Bluray I have no idea what would stop a publisher (porn or mainstream) from shipping both formats, especially if they have a reasonably large sales volume. This particularly looking at the Beta/VHS case where there is nothing special like menus or so to be added. It's plain video.

    4. Re:This may not be an apt analogy, but by westlake · · Score: 1

      if web video formats follow the precedents of home video, porn will be the deciding factor

      Replace "porn" with "Disney" and you would be much closer to the truth.

      The Disney customer doesn't just view or rent - he buys. For his kids and for himself as a collector.

    5. Re:This may not be an apt analogy, but by Anonymous Coward · · Score: 0

      not much into buying porn, but my understanding is only the big makers made a choice. the war was over before the cheap houses started doing hi def porn. so never really hit critical mass in porn.

    6. Re:This may not be an apt analogy, but by Firehed · · Score: 1

      From what I hear *cough*, a lot of porn is still using WMV. Which is not nearly as limiting as the native support of Theora (yes it's Free, but my browser doesn't know that out of the box), but still excludes all Linux and Mac users that don't want to fight with irritating and semi-functional plugins.

      --
      How are sites slashdotted when nobody reads TFAs?
  10. All hail HTML5 what a crock of shit by FlyingGuy · · Score: 1, Flamebait

    I have the tried the latest versions of chrome ( for windows since the linux version is barely functional) and Firefox and they don't support HTML 5 correctly yet.

    Come talk to me when the big committee in the sky pulls their collective heads out of their asses and finalizes HTML 5 and fixes the problems that have been there since HTML 0.01

    This whole Video this and video that is a the tail wagging the dog. If you want to watch movies buy a DVD player subscribe to a cable service that gives you video on demand instead of pushing a bad specficiation out the door before it's finished and waisting a whole but load of programmer time making the incomplete spec of HTML 5 work in a half-assed way.

    --
    Hey KID! Yeah you, get the fuck off my lawn!
    1. Re:All hail HTML5 what a crock of shit by slimjim8094 · · Score: 2

      Come talk to me when you feel like saying what's wrong, rather than just using the word "half-assed" a lot.

      kthxbye

      --
      I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
    2. Re:All hail HTML5 what a crock of shit by Anonymous Coward · · Score: 1

      Yeah and fix those problems with TC/IP stack v 0.001 and dont forget the ones wrong with Linux kernel 0.0001, or the ones wrong with Mac 0.0001.

      Seriously, this is all is needed for a +1 insightful mod?

      PS: my primary browser on linux has been chrome for quite a while, i cannot believe it was unusable or you.

    3. Re:All hail HTML5 what a crock of shit by FlyingGuy · · Score: 3, Informative

      Box model, input model, floating model, version model etc. etc.

      Think it through, then think through all of the kludges you have to come up with to make these work correctly then you will understand.

      We had to wait for 5 versions of of HTML before we got an input type defined to handle things like numbers (floating, integer, fixed point), time, date?!

      Or how about a property to mark an input element as required instead of either having to come up with some javascript to then ripple through the controls to see if they are filled in, this should be handled by DOM and refuse to fire the submit method of a form unless all the fields marked in such a way are populated.

      How about a check box that actually is sent back in the post method to indicated that fact that it is NOT checked instead of having to write code that has to check if 1 of n check boxes are not there to figure out if the user decided not to check it.

      Or how about that Text Area is not considered an INPUT tag. Seems to me it should be since it accepts, wait for it.... INPUT for fucks sake.

      How about being able to float a DIV center and have text flow around it and conform to the DIV's margins, nope that don't work either.

      The box model where changing the internal padding, essentially an internal margin, changes the size of the box and shoves everything around it all over the place or adding a border stripe changes the external size of the box, don't even get me started...

      The list goes on and on and on. Get this shit fixed first the video will take care of itself.

      --
      Hey KID! Yeah you, get the fuck off my lawn!
    4. Re:All hail HTML5 what a crock of shit by FlyingGuy · · Score: 1

      Please elaborate on problems that are currently in either the kernel or in the TCP/IP stack that have persisted through 5 major releases? Ohh wait, the kernel is only at major release version 2.

      --
      Hey KID! Yeah you, get the fuck off my lawn!
  11. Daily Motion by tangent3 · · Score: 1

    Maybe it's time Youtube is boycotted and everyone switches over to Daily Motion, which has been supporting Theora for several months already:
    http://blog.dailymotion.com/2009/05/27/watch-videowithout-flash/

    Boycott probably not going to happen though :(

    1. Re:Daily Motion by LoverOfJoy · · Score: 4, Funny
      I love the FAQ on that page you linked to:

      But wait - the video quality is lower and sound is sometimes crackly...

      That's normal...for now.

    2. Re:Daily Motion by timmarhy · · Score: 2, Informative

      lol. i'd never heard of daily motion before, so it's chances of rolling youtube are slim to none, especially based on the back of h264 vs theora.

      --
      If you mod me down, I will become more powerful than you can imagine....
    3. Re:Daily Motion by Dr.+Spork · · Score: 1

      Yeah, WTF? This is a big fumble by Google. Here I was, tempted to give Chrome another shot just to see this work - as it's one of the very rare things that my beloved Firefox can't do. And when I go through the bother I find what? An experience worse than Flash?

      If Google knew this, shouldn't they have waited with the feature? Will there be another announcement that says: "HTML5 Youtube - now far less crappy than before? Download Chrome to see it!" And seriously, who will?

    4. Re:Daily Motion by Anonymous Coward · · Score: 0

      It's full of porn. Trust me.

    5. Re:Daily Motion by Anonymous Coward · · Score: 0

      Let me see. You use Windows Vista and IE, learnt to programme with Visual Studio. You don't use Linux but think that Mono should be installed by default anyway. Your mates sent you a link to Youtube and ever since you have logged on every day to watch the featured video.

      Just guessing.

    6. Re:Daily Motion by Anonymous Coward · · Score: 0

      Google has nothing to do with it. Their quality is fine, since they're using H.264. The quality screw-up is Daily Motion's. They use Theora, you see...

  12. +1 Informative by Anonymous Coward · · Score: 0

    This was pretty much response as well, it's pretty obvious if you sit with ffmpeg and run ten minutes of lazy encoding tests.

  13. Google already transcodes... by Anonymous Coward · · Score: 0

    Into a half dozen different formats and bitrates, what would be one more? It could replace that old and busted h263 crap they offer, for example. Youtube uses ffmpeg for their transcoding, ffmpeg can output Theora. So really, by simply offering HTML5 youtube has done most of the work needed for Theora.

    Host codes aren't intended to be exposed to the hostile web. You'd get 0wned up quicker than you could even say "video". The most common host platforms don't ship with a h264 codec in their media framework.

    The cost to Mozilla to license h264 would be a significant fraction of their annual budget, each and every year spending what is probably significantly more to license h264 decoders than has ever been spent developing Theora... and webmasters are still still stuck paying usage fees, and Mozilla has put itself in violation of the GPL. That whole path can only end in tears. The open web demands open formats. Full stop. A decade ago people here lamented the impossibility of fighting MSFT's lock on the web. Firefox made the impossible happen, and they can do it again. They aren't alone: Wikimedia and Dailymotion are other prominent organizations supporting this initiative.

    1. Re:Google already transcodes... by smash · · Score: 3, Insightful
      It would be "1 more" transcode that makes no business sense.

      Look, ditching h.264 is simply not going to happen. there are way too many hardware devices out there that do h.264 and no ogg. All I'm hearing is bitching from the firefox camp about how they're not going to support it for reason X rather than looking for a solution to the problem.

      Simply not supporting h.264 is an option, sure. I just don't think its going to end well for firefox.

      AS to host code not being exposed to the web... run it with least privilege in a sandbox. My bet is that any copy of theora embedded into the browser is exactly the same reference code as used else where in any case (and if its, not, then its not as well tested...), so that point is pretty moot.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:Google already transcodes... by Andreas+Mayer · · Score: 1

      Host codes aren't intended to be exposed to the hostile web.

      In case of the Quicktime framework, they certainly are.

      You'd get 0wned up quicker than you could even say "video".

      That's a problem of the provider of the codec then. Let them worry about it.

      The most common host platforms don't ship with a h264 codec in their media framework.

      But it can be added. Which actually is all the point about a system provided media framework.

    3. Re:Google already transcodes... by tepples · · Score: 1

      All I'm hearing is bitching from the firefox camp about how they're not going to support it for reason X rather than looking for a solution to the problem.

      The only solution that keeps Firefox free software in Mozilla Corporation's home country is to either 1. buy the patents and release them freely, or 2. include the H.264 decoder, but have the browser put up a timer on each video that counts down the years until the system clock indicates that the patent has expired in major markets. Mozilla lacks the money to do #1 by a couple orders of magnitude, and #2 isn't a solution. A lot of people think Google is trying to go toward #1 by buying On2.

    4. Re:Google already transcodes... by Khyber · · Score: 1

      "and #2 isn't a solution."

      Actually, if everyone were forced to see how stupid patent-encumbered software was via that direct mens, open-source standards would become the mainstream.

      Remember, Joe Stupid doesn't like not being able to watch his porn videos.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    5. Re:Google already transcodes... by midnaz · · Score: 1

      The most common host platforms don't ship with a h264 codec in their media framework.

      But it can be added. Which actually is all the point about a system provided media framework.

      The "most common host platforms" being referred to are Windows XP and Windows Vista. That's 80% of Firefox's userbase. Do you really think Microsoft will be adding new features to a 8 year old Windows version they are trying desperately to get people to move away from?

  14. H.264 by FrostedWheat · · Score: 5, Informative

    Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.

    Repeat after me: H.264 is NOT FREE, not by a long way. If Firefox included H.264 support then Firefox would also NOT BE FREE. It would be illegal for most of us to distribute a copy.

    1. Re:H.264 by tangent3 · · Score: 1

      How do you respond to those who say that the Mozilla Foundation should pay for the h.264 license?
      After all, Google and Apple are obviously paying for the license to distribute Safari and Chrome with h.264 for free, should be easy enough for Mozilla Foundation to do that too, right? Who really cares that Google and Apple are subsidizing the license fee from their main business models while Mozilla is a non-profit organization formed to provide support and leadership to open source projects that is financed only through donations?

      "So all they need is MORE DONATIONS. Someone else should make those donations so that *I* can have a free Firefox browser that can play h264 content."

    2. Re:H.264 by StripedCow · · Score: 1

      Repeat after me: H.264 is NOT FREE, not by a long way.

      So, they could implement the format and disable it by default. If users want to use it, or if they are allowed in their country, they have to enable it. Just show some
      popup when some site wants to use HTML5, and users will click "OK", you can bet on that.

      Something similar is done by the freetype project: http://freetype.sourceforge.net/patents.html, although in that case the patent can be circumvented by setting a compile-time switch.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
    3. Re:H.264 by Andreas+Mayer · · Score: 2, Insightful

      Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.

      It is.

      Repeat after me: H.264 is NOT FREE, not by a long way. If Firefox included H.264 support then Firefox would also NOT BE FREE. It would be illegal for most of us to distribute a copy.

      They should just use the video framework provided by the OS.

      But they don't want to. Because then they wouldn't get to push their 'free' (albeit inferior) OSS codec.

    4. Re:H.264 by FrostedWheat · · Score: 1

      How do you respond to those who say that the Mozilla Foundation should pay for the h.264 license?

      If the Mozilla Foundation got a license then it would be legal for me to download an H.264-enabled Firefox from mozilla.com, but illegal for me to give a copy of that Firefox to anyone else without buying a similar license or removing the H.264 decoder. So you're either being sued or back at square one.

    5. Re:H.264 by FrostedWheat · · Score: 1

      Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.

      It is.

      But why?

      They should just use the video framework provided by the OS.

      So instead of having one or two well supported codecs, you'd have a hundred and one that might work. You'd be back to the plugin-hell that online video was before Flash came along.

    6. Re:H.264 by FrostedWheat · · Score: 1

      Mozilla would have to do it via a compile time switch too, so you'd have to get your H.264-enabled Firefox binaries from somewhere else. Most people will not, and those that do risk all sorts of other nasties being bundled along with it.

    7. Re:H.264 by StripedCow · · Score: 1

      Mozilla would have to do it via a compile time switch too

      I see no fundamental problems with that. Just let firefox do a little compiling when the user presses the "OK" button.

      This solution may be a little bizarre, but that is exactly what the whole patent situation is... especially in this case of open communication standards.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
    8. Re:H.264 by StripedCow · · Score: 1

      those that do risk all sorts of other nasties being bundled along with it

      Nope. You only risk being sued if you try to sell something containing patented technology.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
    9. Re:H.264 by Andreas+Mayer · · Score: 2, Informative

      Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.

      It is.

      But why?

      Isn't that obvious? Because they choose not to use the system frameworks.

      They should just use the video framework provided by the OS.

      So instead of having one or two well supported codecs, you'd have a hundred and one that might work. You'd be back to the plugin-hell that online video was before Flash came along.

      I don't see a plug-in hell if everyone is standardizing on h264. You might have the option to use one of several decoders, yes. And that's a good thing!

      Anyway, it would not be Mozilla's problem. But it is if they simply refuse to play back h264 altogether.

    10. Re:H.264 by FrostedWheat · · Score: 1

      Who knows, maybe if the Javascript interpreter continues to improve... ;-)

    11. Re:H.264 by FrostedWheat · · Score: 1

      I'm not sure that's true, otherwise Fedora and Debian would have had MP3 supported out of the box years ago.

    12. Re:H.264 by Rockoon · · Score: 1

      Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.

      Mozilla supported GIF before its patent expired.

      Was Mozilla not free back then? Really?

      --
      "His name was James Damore."
    13. Re:H.264 by StripedCow · · Score: 1

      Well, for freetype, many linux distributions actually did include the patented material (i.e., they threw on the compile-time switch without actually asking the user). Here's a passage from the freetype page regarding this issue:

      Finally, many Linux distributions seem to distribute a patched version of FreeType 2 with the bytecode interpreter activated, unlike the sources we distribute. Of course, we can only deny any kind of responsibility in this case. It further means that in the event where you need to update the version of FreeType installed on your system from our sources, you should better manually activate the bytecode interpreter at compile time in order to prevent any loss of quality.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
    14. Re:H.264 by westlake · · Score: 1

      It would be illegal for most of us to distribute a copy.

      It would be perfectly legal if Firefox paid for the license.

      Firefox isn't living on Poverty Ridge. It receives massive infusions of cash each year from Google alone.

    15. Re:H.264 by FrostedWheat · · Score: 1

      That's a fair point. There's also the GIF patent.

    16. Re:H.264 by FrostedWheat · · Score: 1

      According to Wikipedia (not the best source I know...):

      Unisys [...] would not require licensing, or fees to be paid, for non-commercial, non-profit GIF-based applications

    17. Re:H.264 by crimperman · · Score: 1

      > > It would be illegal for most of us to distribute a copy.

      > It would be perfectly legal if Firefox paid for the license.

      But it wouldn't be legal for us to redistribute unless we also paid for the licence. There answer is that an h264 plugin could be made which could then be downloaded (and licenced) by individuals but that defeats the object of HTML5 which is to enable video to be viewed by your site visitors without the need for external plugins. HTML5+h264 is not a lot better than HTML4+flash really, in terms of freedom.

    18. Re:H.264 by pbhj · · Score: 1

      I've not checked the situation but people are saying that Apple (IIRC) only have this tied up in the US (which seems unlikely as codecs are patent encumbered in EPC states too). Thus Firefox could mirror there previous workaround for PGP. Under export laws FF weren't allowed to distribute 128 bit (again IIRC) encryption algos - thus they offered 2 versions one for the US (with the algos) and one for the rest (without). It was a case of the user choosing which version they wanted. I recall downloading the proper (non-crippled) version to the UK without any problems even thought this meant that FF strictly contravened export/national security laws.

      Mozilla may be a US corp but FF is not a US product. H.264 could be in a plugin distributed in a country without any patent restriction on it. No doubt a lawsuit on the basis of contributory infringement would arise but FF list all plugins available without making comment as to whether they are lawful in any jurisdiction - like a common carrier - and the outcome of a successful complaint would probably be bad for the plaintiff too.

      On a side note: I really wish that the interoperability clause had been passed into law in the EPC (European Patent Convention).

    19. Re:H.264 by F.Ultra · · Score: 1

      No with patents you can get sued for using the technology. So let's say that you obtained your version of Firefox from a source which have no license for the codec, then you can get sued for using that version!

    20. Re:H.264 by F.Ultra · · Score: 1

      GIF was never patented, it was the LZW compression used by GIF that was patented. And that patent expired in 2003-2004 so there is no longer any concern for GIF.

    21. Re:H.264 by aix+tom · · Score: 1

      Or users could just switch go Gentoo and make the binaries themselves.

      I think a lot of headaches for OSS developers could be avoided if the didn't ship binaries themselves, but left the binary compilation to the distribution or the user.

      Of course then their "You are not allowed to ship a self-compiled Firefox binary under the Firefox name/trademark" might bite them back, when everybody compiling it with additional codecs has to rename it to something else.

    22. Re:H.264 by BZ · · Score: 2, Interesting

      It would be legal for Mozilla to distribute Firefox if it did that. It would not be legal for anyone else to do so.

      For example, if you put a copy of Firefox on your USB keychain and went over to your friend's house and installed it there (from that keychain) without paying the H.264 licensing fees required, you could be sued for damages. Not much in the way of damages, clearly, but you would in fact be liable for them.

      Of course if you happened to be, say, Ubuntu, you would have to pay a pretty hefty fee (or be liable for significant damages) if you shipped Firefox as part of your distribution.

    23. Re:H.264 by DdJ · · Score: 1

      Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.

      That's because it is.

      Mozilla doesn't have to support H.264 themselves, they just have to "get out of the way". They just have to enable the ability for plugins to add support for new codecs. Pretty much every platform comes with some kind of H.264 implementation these days. The plugins would appear very rapidly, if Firefox permitted it.

      Do you prefer a world where YouTube asks some users to install an H.264 codec, or where it asks many users to install the Flash player? Why is H.264 worse than Flash?

      At one point Mozilla believed they had the leverage to force a codec other than H.264. Maybe they still think so. Hopefully, they'll get over it before too much damage is done to them.

    24. Re:H.264 by Anonymous Coward · · Score: 0

      Linux failed.
      Ogg failed.
      GIMP failed.
      Why are you free-tards so hell bent on having Firefox fail too?

    25. Re:H.264 by ObsessiveMathsFreak · · Score: 1

      Mozilla doesn't have to support H.264 themselves, they just have to "get out of the way". They just have to enable the ability for plugins to add support for new codecs. Pretty much every platform comes with some kind of H.264 implementation these days. The plugins would appear very rapidly, if Firefox permitted it.

      And you think that will save them when H264 has saturated the web, and MPEG-LA come seeking their pound of flesh? Anyway you look at it, Mozilla is either going to have to end up paying the liecence fee or else and equivalent amount defending itself from legal action.

      --
      May the Maths Be with you!
    26. Re:H.264 by ObsessiveMathsFreak · · Score: 1

      How do you respond to those who say that the Mozilla Foundation should pay for the h.264 license?

      What about other browsers? SeaMonkey, Flock, Konqueror, Dillo, Epiphany? Are all these supposed to become second class citizens of the web with no support for core tags? Konqueror is installed by default in every KDE installation and beyond. You think MPEG-LA is going to overlook that?

      If H264 becomes the standard for the HTML video tag, we will be faced with a web divided into browsers which have paid to support core features, and browsers which have not. Imagine this cancer spreading to new or even existing features in the future; where every new web development is the "property" of a private company looking for its protection money. After only three or four such developments, pretty soon, Mozilla literally won't have the money to pay them all off.

      It's not worth it. I don't want video in web pages so bad that I'll accept this; and I can already play them in flash when it comes right down to it. As bad as flash is, it's not the potential carcinogen that the video tag has now become.

      --
      May the Maths Be with you!
    27. Re:H.264 by Anonymous Coward · · Score: 0

      I don't know about the others, but Epiphany uses WebKit which uses GStreamer for audio/video, so H264 works in Epiphany. (Strangely, YouTube's HTML5 pages don't work in Epiphany for me, but it's not because of codec issues.)

    28. Re:H.264 by sznupi · · Score: 1

      With the way Mozilla approaches branding of modified version, Firefox is already "NOT FREE". Ask Debian folks.

      --
      One that hath name thou can not otter
    29. Re:H.264 by arose · · Score: 1

      Only creation of GIF's was covered by the patent.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    30. Re:H.264 by Rockoon · · Score: 1

      Unisys was not making demands in regards to reading GIF's, but it most definitely was covered by patents.

      If the argument that Mozilla shouldn't include any patented algorithms even if it has the rights to do so, then GIF support clearly violated this view.

      If thats not the argument, then whats wrong with Mozilla obtaining the rights to implement h.264?

      --
      "His name was James Damore."
    31. Re:H.264 by midnaz · · Score: 1

      Mozilla would have to do it via a compile time switch too

      I see no fundamental problems with that. Just let firefox do a little compiling when the user presses the "OK" button

      Err, if it is not compiled then it's not shipped as part of the package that you download. The point is that Mozilla can't distribute the source code so there is nothing for you to compile when you press that OK.

    32. Re:H.264 by StripedCow · · Score: 1

      why can't they distribute the source code? it's an open-source project after all...

      further, you have to think a little out of the box here... compilation is just translation from one language into the other. they might as well just ship the assembly code, and assemble it (i.e., call "as") when the user presses "ok". perhaps even the binary code could do, as long as there is an "ok" button.

      you see, it is not illegal to distribute the text of a patent, verbatim, so it should not be illegal to distribute a machine-readable version of that patent.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
  15. Google acquired On2, makers of video codecs by dracvl · · Score: 5, Interesting

    Google recently acquired On2, makers of the Ogg Theora (aka VP-3) codec which was released into the public domain and then taken over by xiph.org.

    On2 have codecs VP-7 and VP-8 which have equivalent (if not better) quality than h.264.

    It would not be surprising if Google made those codecs available, since they aren't patent-encumbered, and Google is heavily invested in HTML5 --and likes open standards.

    This would be the ideal outcome. h.264 is a really bad option.

    1. Re:Google acquired On2, makers of video codecs by SolitaryMan · · Score: 1

      ... Google is heavily invested in HTML5 --and likes open standards.

      Google likes standards open to them. There is a difference.

      --
      May Peace Prevail On Earth
    2. Re:Google acquired On2, makers of video codecs by DrXym · · Score: 1
      This would be the ideal outcome. h.264 is a really bad option.

      Actually its an excellent option. It's an industry standard, there are a multitude of free and non-free tools, it has well defined profiles & levels, it has countless software & hardware implementations, it is the default encoding format for an increasing number of hardware devices and it offers excellent quality.

      The simple reality is that open source codecs are never going to supplant H264 in this generation. Even google couldn't make it happen if they defaulted to an open source codec.

      I can understand why Firefox and Linux might not like H264 but it's here and its a reality. So how does one go about enabling open source apps to use a licenced codec? The answer for Firefox at least seems pretty simple, IT DOESN'T NEED TO LICENCE THE CODEC. Just provide a simple video plugin architecture and implementations for operating systems which include H264 (i.e. OS X & Windows) and a stub for those that don't. It wouldn't take more than a few days before a working Linux plugin appeared.

    3. Re:Google acquired On2, makers of video codecs by Anonymous Coward · · Score: 0

      > On2 have codecs VP-7 and VP-8 which have equivalent (if not better) quality than h.264.
      This is nothing but marketing lies. A good H.264 encoder, like x264, will beat VP-* easily, unless the test is specifically engineered to bring a different result.

    4. Re:Google acquired On2, makers of video codecs by Sir+Homer · · Score: 1

      No, it's a really bad option. Do remember when people got threatened with lawsuits for having GIFs on their website? That might happen with H.264 as well.

    5. Re:Google acquired On2, makers of video codecs by bonch · · Score: 1

      Do remember when people got threatened with lawsuits for having GIFs on their website?

      Please cite an example where someone was successfully taken to court for having a GIF on their website, because this comes off as FUD.

    6. Re:Google acquired On2, makers of video codecs by Sir+Homer · · Score: 1

      I said "threatened with lawsuits". H.264 is a patented format with participation fees that websites who use H.264 are expected to pay.

    7. Re:Google acquired On2, makers of video codecs by harmonise · · Score: 1

      Google recently acquired On2

      They have not. They made an offer, but it has not been approved by On2's shareholders. Some shareholders are opposed to it saying that Google's offer is not enough.

      --
      Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
    8. Re:Google acquired On2, makers of video codecs by node+3 · · Score: 1

      I said "threatened with lawsuits". H.264 is a patented format with participation fees that websites who use H.264 are expected to pay.

      I don't think this is true. The encoders need to be licensed, and maybe the decoders do, but simply hosting an h.264 file does not require a license.

  16. Must have script. by Anonymous Coward · · Score: 0

    Use this script: Youtube without Flash Auto
    http://userscripts.org/scripts/show/50771

    Than go to Youtube, hit Preferences under the player, select VLC Player from the drop down menu and Save.

  17. Doesn't work in Safari for iPhone by ciryon · · Score: 1

    I just tried browsing the full site on iPhone and switched to HTML5 mode. Doesn't seem to work, just displays a crossed over play-icon.

    1. Re:Doesn't work in Safari for iPhone by yabos · · Score: 1

      The iPhone supports a subset of what the Mac can play since it uses a hardware decoder chip. The movies it can play are limited by resolution and bit rate.

  18. Cost for Firefox H.264: $5,000,000+ per year by CritterNYC · · Score: 5, Informative

    The problem with H.264 is both its patent status and the licensing cost. The patent means that it can't legally be used in software licensed under the GPL/LGPL 3.0 in countries like the US. So, Mozilla would have to add a closed-source component to Firefox for it to be able to work.

    But the other problem is the licensing fee. Firefox ships so many software units that it will hit the enterprise cap for H.264 licensing every year. In 2006, that cap was $3,500,000. In 2007 it went up to $4,250,000. In 2009 it went up to $5,000,000. In 2011, it is going to go up again. So Mozilla will have to pay out $5,000,000 (and climbing) per year, just to support this one video codec in a product that they give away for free. Their revenue in their last fiscal year was $78.6 million.

    Is it really worth it to spend 6% of your total yearly revenue on the licensing fee for one video codec?

    Apple doesn't care, since they already hit the yearly cap anyway (see: iPod/iTunes) so it's free for them to include it in Safari. I'm not sure if Google does (can't think which apps it would be), but they have the money to do it either way. Opera and Mozilla don't currently have this expense... and they can't afford it. Nor can any other upstart browser since once they hit 200k 'units' per year, they have to start paying $0.20 per download.

    1. Re:Cost for Firefox H.264: $5,000,000+ per year by CowboyBob500 · · Score: 1

      The patent means that it can't legally be used in software licensed under the GPL/LGPL 3.0 in countries like the US.

      And the rest of the world cares because? It's time the rest of the world stuck two fingers up at the US system, grew a backbone, and left the US to their own downward legal spiral. All we need is a non-US company (Canonical perhaps?) to fork Firefox and end this madness.

    2. Re:Cost for Firefox H.264: $5,000,000+ per year by shish · · Score: 2, Insightful

      Mozilla would have to add a closed-source component to Firefox for it to be able to work.

      Or they could hook into each OS's native codec libraries -- IIRC windows 7 supports h264 out of the box, and most linux distros have a gstreamer-x264 or whatever package easily available ("easy" as in "will prompt to be installed the first time it's required", in ubuntu's case at least)

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    3. Re:Cost for Firefox H.264: $5,000,000+ per year by TheRaven64 · · Score: 1

      The other problem is the GPL. The only current open source H.264 implementation is x.264, which is GPL'd. This means that it's incompatible with two of the three licenses used by Mozilla (LGPL and MPL), so even if patents were not an issue, it can't be distributed with FireFox.

      --
      I am TheRaven on Soylent News
    4. Re:Cost for Firefox H.264: $5,000,000+ per year by Firehed · · Score: 1

      In 2009 it went up to $5,000,000. In 2011, it is going to go up again. So Mozilla will have to pay out $5,000,000 (and climbing) per year, just to support this one video codec in a product that they give away for free. Their revenue in their last fiscal year was $78.6 million.

      Is it really worth it to spend 6% of your total yearly revenue on the licensing fee for one video codec?

      More to the point, is it worth spending 6% of your revenue on not having all of your customers switch to competing products?

      Yes. Absolutely, undoubtedly yes.

      You have to remember that Firefox is not IE - it doesn't come preinstalled on 90% of computers shipped. Nearly everyone using that browser is doing so because they chose to switch to it from the system default. Given that both Safari and Chrome offer most of the features that got people to switch in the first place, it wouldn't come as a shock to see people migrate away from Firefox. I switched to Safari for my full-time browsing a few months ago, and I'd been using Firefox since the pre-1.0 naming debacle. Most of the extensions that I cared about had some sort of counterpart, and it's consistently faster, more responsive, and has a lighter footprint.

      Don't take this as an ad for Safari (it's not), but realize that browsers have started to suck a lot less since Firefox came out years and years ago, and that means competition. And in my eyes, the competition is winning. That's my opinion of course, but many of my geek friends that used to use Firefox have also switched to Chrome and/or Safari.

      --
      How are sites slashdotted when nobody reads TFAs?
    5. Re:Cost for Firefox H.264: $5,000,000+ per year by BZ · · Score: 1

      > I'm not sure if Google does (can't think which apps it would be)

      The unit count is for decoders _or_ encoders. So Google is almost certainly already paying the licensing fees per unit for any machine involved in transcoding Youtube videos, say. They may well be hitting the cap with just that.

    6. Re:Cost for Firefox H.264: $5,000,000+ per year by Fluffy+Bunnies · · Score: 1

      x.264 isn't a decoder so it's not related to video playback in any way

    7. Re:Cost for Firefox H.264: $5,000,000+ per year by vitaflo · · Score: 1

      "Is it really worth it to spend 6% of your total yearly revenue on the licensing fee for one video codec?"

      I dunno, is it worth it to potentially lose a vast amount of your user base in the future if you don't?

    8. Re:Cost for Firefox H.264: $5,000,000+ per year by sznupi · · Score: 1

      Plus you add at least some portion of Android phones to that...

      --
      One that hath name thou can not otter
  19. Re:Excellent by Anonymous Coward · · Score: 0

    Ah. The wishful thinking of an anti open source, pro Microsoft zealot is raised again.

    Yawn.

  20. The problem with Directshow (Moz/Opera devs) by Sits · · Score: 2, Insightful

    A Mozilla developer has pointed out several drawbacks of using Directshow for HTML5 video. Among them was that some Directshow codecs are of questionable quality, it can be source of security bugs and would mean a different backend for every supported platform.

    The Opera folks have said Directshow is not well geared to streaming videos so Opera has gone with a minimal gstreamer port for HTML5 video.

    1. Re:The problem with Directshow (Moz/Opera devs) by TheRaven64 · · Score: 3, Informative
      The Opera blog confused me. They say:

      The main problem with this approach is that many DirectShow filters are written in such a way that they can only read from a local file, since the DirectShow framework makes this a lot easier than the "right way" of streaming input from a upstream filter

      Now, admittedly, the last time I wrote any DirectShow code DirectX 8 was all new and shiny, but this sounds like complete nonsense. Writing a DirectShow filter is trivial. You just subclass the standard filter class and receive data on one of the pins. I wrote one that took data off any part of a DirectShow stream and chucked it across the network and a matching one that received it. I had absolutely no problems swapping in other CODECs. They all just took data from one pin and pushed it out on another.

      Writing a DirectShow filter that can only read from a local file is a pain, because you need to implement support for all of the potential container file types. Writing one that fits with the rest of the architecture is trivial.

      Security is a potential issue, but I'm not sure that GStreamer is any more secure. Both contain large amounts of code that can potentially house exploitable bugs. If you care about security then you should run the CODEC in a separate process with a pipe going in to it to provide the data and a shared memory segment for getting the rendered images out.

      --
      I am TheRaven on Soylent News
  21. patenting how to make stuff is ok by circletimessquare · · Score: 2, Insightful

    patenting how to manipulate bits is not ok

    the free exchange of ideas is the only thing underpinning any sense of philosophical integrity in modern liberal democracy. besides, you basically lie when you say its expensive to develop this stuff. a university professional could do this, and by publishing it, for free (in an ideal world) he cements his academic credentials, which is the only reward anyone deserves for the advancement of ideas

    capitalizing on those ideas is a secondary game that does not overlap, and should not overlap (in an ideal world) with the primary game of development of better ideas

    ideas should not be patented

    manipulating bits is simply an idea, not a marketable product

    YOU'RE doing it wrong

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:patenting how to make stuff is ok by TheRaven64 · · Score: 1

      Patenting how to build a CODEC is not okay, but patenting how to build a machine is? A large number of patents for physical machines are orders of magnitude less complex and less difficult to develop than the patents on H.264.

      And if you think university professors are cheap, think again. Someone capable of developing this kind of thing costs, including institutional support and postgrad / postdoc salaries and infrastructure, around half a million dollars per year and would probably take 3-5 years to develop a half-decent CODEC - most just develop a few algorithms that are eventually combined into a CODEC.

      If you think it's really easy, go and develop a patent-free CODEC. The BBC has done this with Dirac, a profile of which is being standardised as VC-2. Take a look at the amount of money and time they've put into it. Their CODEC is built on top of a lot of research published by people at universities (who are funded by taxpayers' money), and even then it took them five years to develop something vaguely competitive.

      --
      I am TheRaven on Soylent News
    2. Re:patenting how to make stuff is ok by circletimessquare · · Score: 1

      patents: like i said before, patenting how to make something PHYSICAL is ok, patenting IDEAS goes against the philosophical basis of liberal democracy. why you think how complicated something is is supposed to matter, i don't know why

      professors: yes, they are expensive. and? if a professor is good, he generates good ideas, and therefore gets a good salary. i don't understand your point. their ideas should be patented to support this? you haven't noticed this fancy radical idea called college tuition?

      a codec is a codec is a codec. how useful or difficult it is to generate is without meaning. its purpose is to manipulate bits, its software. it is therefore incompatible with the idea of patenting, on a philosophical level

      you bring in all these red herrings of costs, as if a patent is the ONLY way to create the infrastructure necessary to create better codecs. as if there aren't a dozen orthogonally related ancillary reasons and motivations and revenue streams more than adequate for people and companies to pour money into codec development

      don't destroy the philosophical foundations of liberal democracy because you can't imagine other ways besides patents to generate money for codec research

      --
      intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    3. Re:patenting how to make stuff is ok by TheRaven64 · · Score: 1

      You seem not to understand what a patent is. A patent is a monopoly on an idea. The idea is how to build something. Whether that something is a piece of software or a machine, the patent is still covering an idea. Your rant, complete with liberal abuse of the English language, does not address this at all. If patenting ideas is against 'the philosophical basis of liberal democracy' then all patents are anti-democratic. That may be what you want to argue - I know quite a few people who oppose the entire patent system - but that's not what you are saying.

      Oh, and I didn't bring up 'the red herring of cost' I was replying directly to what you wrote, claiming that CODEC development was cheap because a university professor could do it.

      --
      I am TheRaven on Soylent News
    4. Re:patenting how to make stuff is ok by circletimessquare · · Score: 1

      i have an idea on how to make a new type of internal combustion engine. the production of engines using that idea is therefore subject to legal restrictions

      i have an idea on how to encode video. the encoding of video using that idea is merely a manipulation of bits. it is therefore subject to no legal restriction (ideally)

      ideas are merely abstract representations. bits are merely abstract representations. it is therefore philosophically unsound to put legal limits on the flow of those bits: they are the same thing as ideas. you are basically putting artificial and productivity limiting controls on the free exchange of ideas. patenting anything which merely governs the flow of bits is directly contradictory to the bedrock concepts in modern liberal democracies of no limitations on the exchange of ideas

      of course a lot of people are confused on this issue. so we must work at convincing the likes of you about why their is lack of logical coherence in your words

      a bit is not an atom. try to understand why channeling the flow of atoms and channeling the flow of bits is philosophically completely different subject matter and subject to completely different implications . your entire premise is that the two arenas are subject to the same rules. only at the point in which a physical object comes into play does the idea of legal limitations make any sense in terms of a clear benefit to society. not to mention enforcement

      this is the bottom line: if you cannot understand why the flow of bits/ ideas is completely unlike the flow of stuff, you fail, hard, at saying anything logically coherent on the subject matter

      you need to work through the logical contradictions in your beliefs

      --
      intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    5. Re:patenting how to make stuff is ok by Anonymous Coward · · Score: 0

      why do you throw insults at each other? its destroying us, can't you see?

      how can we dismantle adobe with our svg extensions when you are just infighting.

    6. Re:patenting how to make stuff is ok by Anonymous Coward · · Score: 0

      H264 is not an idea. It is a implementation/wrapper around many algorithms that allows people to encode and decode media. Thus, H264 is a product, and as such is patentable, so long as the scope of the patent is justifiable (aka, so long as the patent doesn't contain clauses restricting use of the algorithms in completely different applications).

      The people behind H264 took ideas developed in academia and spent resources building a streamlined, usable product. The product is what is patented. The manipulated bits you mention are the videos you are encoding/decoding (which have no inherent value), not the product you are using to do the manipulations (the product has value as you are using it).

      Many people release free software, for good reason. This does not mean that all software can not be a product. So if you disagree that H264 is not a product, don't use it or other software released as a product (once you have expressed your opinion, of course). If it has no value to you (you wouldn't be willing to pay for it), then you would be hypocritical to use it when there are free alternatives.

    7. Re:patenting how to make stuff is ok by stdarg · · Score: 1

      ideas are merely abstract representations. bits are merely abstract representations. it is therefore philosophically unsound to put legal limits on the flow of those bits: they are the same thing as ideas. you are basically putting artificial and productivity limiting controls on the free exchange of ideas.

      Patents, whether on ideas or physical devices, are about the application of ideas, not the exchange of ideas. Patents don't stop anybody from taking apart a physical device and learning how it works, or telling others how it works. Likewise, patents don't stop anybody from figuring out how h264 works.

      In fact, if you look at why patents exist you'll see a big reason is to eliminate the need to keep ideas secret. The whole point of patenting something is that you can tell everybody exactly how it works, or at least not go out of your way to make it hard to figure out, thus benefiting society, but nobody can take that knowledge and compete with you using it directly (for a limited amount of time).

      It's arguable that patenting ideas that go into computer programs is worthwhile if it means a greater and more widespread understanding of the ideas that go into them, which can be applied after the patent expires, using the same logic as with physical items.

      patenting anything which merely governs the flow of bits is directly contradictory to the bedrock concepts in modern liberal democracies of no limitations on the exchange of ideas

      Patents on physical devices, not to mention copyrights, are also contradictory to the principles of liberal democracies. What do you mean I can't take the knowledge in my own brain and simply *express* it as a physical device? What happened to freedom of expression?

      That's not an argument you can use while simultaneously supporting patents on physical devices.

      this is the bottom line: if you cannot understand why the flow of bits/ ideas is completely unlike the flow of stuff, you fail, hard, at saying anything logically coherent on the subject matter

      Completely unlike? A physical object that was created or arranged by a person is by necessity an expression of an idea. When other humans observe that arrangement, they convert it back into an idea. Consider that all sensory input starts as "stuff" and is converted into ideas so that our consciousness can process it, and all communication of ideas depends on converting those ideas into "stuff" which can then be transmitted physically to others. Consider that every idea has at least one representation in physical form, and every physical form has at least one idea. Consider that even if you're talking about literally flowing, a physical expression of an idea that changes over time -- even accidentally -- engenders new flows of ideas in observers as well.

  22. OGV can be as easy as drag and drop by tepples · · Score: 1

    The authoring tools for .ogg are not there either.

    What authoring tools? Just take your finished MP4 file produced with whatever tools, drag and drop it onto the transcoder, and you have OGV. Provided your MP4 is at a high enough bitrate, you shouldn't notice any transcoding artifacts.

  23. Inter Net? by ElusiveJoe · · Score: 2, Interesting

    Not being a US citizen I'd like to see it happen, but it won't.

    I think more people will realize soon, that a thought that software and Internet are independent from governments and borders is an illusion. Currently, the dominant software provider and consumer is US. So the major part of software abides by US law. I still remember, that IE 6 for Russia did not contain 128-bit encryption because of US export laws.

    Add classic US ignorance to it - "we run the world". Hell, even google.ru censors search results with DMCA notice, while DMCA is not valid in Russia. It respects laws of Australia, but laws in China are 'bad' (I personally consider them bad too, but dura lex sed lex). So US laws "must be abided", but laws of other countries "could be abided, if it's not harmful to US".

    1. Re:Inter Net? by lxs · · Score: 1

      True. OTOH both VLC and mplayer have been getting away with it for almost a decade. Then again, Firefox is a pretty big target.

  24. Input, timers, processing, sprites, and audio by tepples · · Score: 1

    Video games need input, timers, processing, sprites, and audio output. That's it. Modern browsers have far faster processing engines than (say) Firefox 1.0-era browsers. The HTML DOM has supported input, timers, and sprites for a long time; games from yet another Soviet Mind Game on up have been possible for years. And the latest draft of HTML5 finally adds decent audio (with pitch, volume, and sync) to the DOM.

  25. kaiser soze by MoFoQ · · Score: 2, Insightful

    hmm...I'm testing out this vimeo html5 player and I'm looking at the source...I see calls using mootools 1.11 to a mootools class named "Kaiser Soze".....gotta love programmers with a sense of humor.

  26. MPEG LA by Anonymous Coward · · Score: 0

    Now if only FireFox will get support.

    Now if only the MPEG LA would give Mozzila a patent license that covers downstream distributors.

  27. The 2 are linked by DrYak · · Score: 4, Insightful

    Because HTML5 + VIDEO tag draws people away *from Flash* and *into an open standard* that can be found everywhere.
    What Microsoft would have liked would be, drawing people away from Flash and *into one of their own proprietary* technology, marketed as much better.

    The core strategy of Microsoft is not just killing random IT companies for the fun of it (although it's not always obvious), but killing other companies in order to get bigger themselves in the process.

    Silverlight is their optimal solution to lock more customer in Microsoft solutions.
    HTML5 is their nightmare.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:The 2 are linked by ObsessiveMathsFreak · · Score: 2, Insightful

      Because HTML5 + VIDEO tag draws people away *from Flash* and *into an open standard* that can be found everywhere.

      H264 is not an open standard. The video tag is just another lock-in, masquerading as an easy to use core feature.

      It's all moot anyway. Without agreement on a codec, the video tag is dead in the water anyway. Lack of a common standard means that the video tag essentially equates to what we already have; the ability to "embed" video which may or may not play in the users browser. Google and Apple killed proper web video because they put their other business interests before giving web users the tag they really wanted. They're not browser companies after all.

      --
      May the Maths Be with you!
    2. Re:The 2 are linked by bonch · · Score: 1

      H.264 is as much of a closed standard as MP3 is, and MP3 is everywhere. Operating systems include H.264 playback by default, just as they do with MP3.

      The video tag isn't any more of a "lock-in" than the img tag, which also doesn't specify a format. Besides that, at some point, you just need to accept that Theora is a technically inferior codec anyway.

    3. Re:The 2 are linked by Stupendoussteve · · Score: 1

      Operating systems include H.264 playback by default, just as they do with MP3.

      I use Red Hat/Fedora you insensitive clod!

    4. Re:The 2 are linked by Anonymous Coward · · Score: 0

      Wow, way to forget history. Many Linux distros (as the sibling points out) still do not include MP3 support due to legal issues. In fact, the patents on the MP3 format were the explicitly stated reason for the development of Ogg Vorbis. Fool me once, ...

    5. Re:The 2 are linked by Khyber · · Score: 1

      "H.264 is as much of a closed standard as MP3 is"

      Yup, As in VERY CLOSED.

      Which is why many MP3 players STILL PAY LICENSE FEES FOR THE FRAUNHOFER MP3 CODEC.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  28. Lots of problems. by DrYak · · Score: 1

    check with the system to see if it provides those codecs, and then either play the content

    The main problem with Firefox is that there no such thing as *THE system*, singular.
    Firefox is a cross-platform tools designed to work on lots of different OSes (and even more now that it is also entering the embed world with project Fennec)
    The solution you currently ask for would require the developers writing in support for lots of different codec framework.

    The second problem, is that you *hope* that the system's codecs will be adequate :
    - They will be able to correctly pause/seek/loop/etc. as the command are issued with the VIDEO tag's API.
    - They will be of adequate security. We're not speaking about an offline player. We're speaking about streaming video from THE (virus-filled) WEB ! The number 1 problem with closed source Flash are the vulnerabilities - you'll be just replacing 1 problem with another.
    And given the popularity of video websites, you know that the slightest bug will be over-exploited. You saw how much abuse was done simply with rick-rolling ? now think of the possibilities if, instead of subjecting the user to some cheesy song, you inflicted a remote exploit to a buggy codec.
    (- Also, the Mozilla developers mentioned there are lots of "install this codec to view our porn" scams on the web to get people will fully install malware)

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Lots of problems. by DrXym · · Score: 2, Interesting
      The main problem with Firefox is that there no such thing as *THE system*, singular.

      Of course there isn't, but that doesn't mean the issue is impossible to solve. In fact if you look at the way Firefox works right now, it has abstractions of various operating services - messaging, drag & drop, windows, graphics, file locations, plugins etc. Each of these abstractions is done precisely so the bulk of the code is platform netural.

      There would be no difference if you were to write an abstract video / audio playback object. The object would appear to the bulk of the code as a common interface or abstract class even though it would be implemented differently on each platform. On Windows, the playback object might work over DirectShow, on OS X it might use Quicktime, on Linux it might use GStreamer or Xine. To the caller however it doesn't make any difference so long as it works as expected.

      The second problem, is that you *hope* that the system's codecs will be adequate :

      Hardly a biggy either. On operating systems that supply one or more codecs implementations, you test and ensure the codecs / filters meet requirements. For operating systems that don't, you revert to a stub implementation that does nothing, and direct users to a help page. e.g. The browser could state that a codec must support high profile @ 4.1.

      In short Firefox can wash their hands of worrying about licencing altogether just by using what the system provides and designing the video apis appropriately such that others can extend / augment the built-in behaviour.

  29. Thats the content provider fees by Anonymous Coward · · Score: 0

    Firefox would be paying $5million/yr. $5m would pay for a lot of codec development, and Firefox wouldn't be the only one paying: anyone else distributing a h264 supporting browser that isn't judgement proof would need to pay, and everyone serving up video. So practically, doing your hosting will no longer be realistic: We'll be stuck with service providers like youtube with their insane habit of taking your files down on a whim.

    Mpegla states that they are already collecting $66 per every man, woman, and child on earth. How much more do you think they're going to make once we hand them over the Internet?

    Goodbye open web. Hello pay to play.

  30. Webvideo with Dancing Kitten ... in 1080p ?!? by DrYak · · Score: 1

    We're speaking about Youtube, Vimeo and Dailymotion.
    Websites with short video snips uploaded by users.
    *NOT* movie rental website providing 1080p HD studio-quality videos (although Youtube has said considering this options in the future...)

    In this context, arguing which codec is better boils down to arguing which codec would be better at preserving all the artefacts, distortion and noise/grain due to previous compression stages and sub-par recording equipment (camera-phone, which compress video as MJPEG with 70% quality).

    Once again,
    the THEORA vs. H264 QUALITY debate is *irrelevant* regarding video clip websites. Even older codecs like DivX/Xvid and similar MPEG-4 part 2 ASP codecs are good enough.

    The only argument in favour of H.246 is that :
    - most of these websites already store a h264 variant of the video. HTML5 + h264 requires absolute zero efforts, whereas HTML5 + Theora would require adding yet another compression variant to the others (H263, Sorenson, etc.) already stored on the site.
    - the most popular pieces of equipment out there (like iPhones and the like) have some form of hardware h264 acceleration built-in. So h264 already works, whereas as Theora would require porting/recompiling a codec for now, and sourcing a chip with hardware Theora support later (Note: There are free/libre Theora cores. Although none in production at some high-volume manufacturer).

    So in short, Laziness is the main reason why some prefer to implement H264 instead of Theora. If it was really a question of quality, people would have moved to some Dirac/Schrödinger derivative (which is both patent-unencumbered *AND* based on a more recent and better technology as H264).
    -

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Webvideo with Dancing Kitten ... in 1080p ?!? by ardor · · Score: 1

      I want to see a comparison Dirac vs. h264 where Dirac wins. As for "better technology", wavelets for video are overly hyped and have many problems which is the reason why block-based DCT codecs are still around. As for patents, Dirac certainly violates patents, as does every software under the sun. However, the situation is particularly bad for video coding, which is filled to the brink with bogus patents. Let Dirac become popular, and somebody WILL sue.

      Also it is not "laziness". Many websites storing h264 content means that transcoding to theora would take them tons of processing power and additional storage space, since Theora is still vastly inferior to h264 at the same perceived quality (not necessarily PSNR). As for hardware acceleration, software decoding is no option. Hardware is the only way to go. It uses less energy, and increases responsiveness, since the CPU does not have to do the decoding.

      --
      This sig does not contain any SCO code.
  31. Quality debate by DrYak · · Score: 1

    In theory Dirac/Schrödinger/VC-2 should be better than H264/MPEG 4 part 10 ASP : it's a newer technology.
    It will be the best thing : patent-unencumbered, opensource, and hardware supported.

    BUT

    In practice I can't really understand why such a fuss about codec quality for websites on which users mainly post short video sets taken with their camera-phone.
    Do we really need a debate to decide which codec is better at faithfully carrying over the compression artefact of the original MJPEG at 70% ?!?

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Quality debate by imroy · · Score: 1

      ...better than H264/MPEG 4 part 10 ASP

      Er, what? MPEG-4 part 10 is AVC a.k.a h.264. MPEG-4 part 2 is SP/ASP.

  32. Reviewable, not inhouse. by DrYak · · Score: 1

    You're indulging in the "Not written here" attitude, where code that is written in any other codeshop is considered inferior.

    The problem is not that the code is not inhouse. The problem is that this code can't be reviewed.
    Nowaday NO opensource project rely on their own codec implementation. They all tend to use ffmpeg.
    FFMPEG is good because it is opensource and its code can be (and is) reviewed for bugs.
    (The only problem : it can't be used in some jurisdictions due to patents on H264)

    Whereas, a hypothetical Direct-Show backend has no way to know if the codec receiving data *straight from the (virus-filled) interweb* is trustworthy.
    Remember how quickly videos of Rickymartin spread everywhere and how easy it was to rick roll unsuspecting users ?
    Now think what will happen if, instead of simply subjecting innocent users to some cheesy music, malevolent people were subjecting buggy codecs to remote exploits ?

    As soon as a flaw is discovered in the system H264 codec on Windows, you bet that you'll see "ricky-exploit-rolling" poping every where on the web. Bonus point if your viral video doesn't ultimately stop the player, but only freeze it during the exploit - something which could be interpreted as a buffering glitch by the user.

    For the record, I have almost 30 years experience writing code, and a good decade of running teams of programmers. I know what they're like.

    For the record, I might only have 20 years experience. But in that (shorter) time frame, I've had on lots of occasion met crappy - but locked and proprietary code - that I had to patch / circumvent with debuggers and hex editors, just have it work. And that was just software wich *I* was forced to use. Meaning that these softwares mainly only got my input fed into them. With HTML5 with VIDEO tag, you're speaking about feeding data directly from the un trustworthy internet straight into codecs whose crappy quality you can't control ! That is irresponsible. That is just a huge disaster waiting to happen.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Reviewable, not inhouse. by yabos · · Score: 1

      How is this any different than it is now? If I want to view Quicktime videos on Windows, I have to install Apple's Quicktime browser plugin. I don't see what the big deal is if they did the same with HTML5 videos.

      Hell, with Flash video being one of the most popular, we have to have the swiss cheese Flash player plugin that is riddled with vulnerabilities. I'm not sure how having Mozilla be responsible for the video decoding is any better except that they can force people to upgrade the decoder when updating the browser. Since they're moving this way with doing the automatic plugin updater, it's not really of much benefit having them do the video decoder IMO.

    2. Re:Reviewable, not inhouse. by BlackHawk-666 · · Score: 1

      The solution is not to use the "crappy" software, and instead choose a project that suits your needs both in terms of functionality and quality. If it fails to meet your needs, don't use it!

      --
      All those moments will be lost in time, like tears in rain.
  33. Come on firefox! Why not get hog tied? by Anonymous Coward · · Score: 0

    Come on firefox, everyone else in the industry is leaping head over foot to get themselves hog tied with ridiculously expensive licenses for h264, so why not add a proprietary anchor to your open source boat? So throw away any notion that open source software can be successful on its own, give up your only real reason to be different, and pick up a technology that a couple of your proprietary competitors are adopting! Sure it kind of undermines the whole idea of open source, but who cares, h264 is the media format of the week!

  34. So send payment to Firefox, then by Anonymous Coward · · Score: 0

    So send payment to Firefox, then. Or is it you want FF to pay for you?

  35. If they go for h264 video is a nonstarter by Anonymous Coward · · Score: 0

    If they go for h264 video is a nonstarter. All that "product" they want to entice me with? Pointless. If they don't support a video codec that can be implemented for free, I won't be watching.

    I don't need to consume: I'm a CUSTOMER.

    If you exclude me, I'll not play either.

  36. according to his point of view by circletimessquare · · Score: 1

    svg extensions cannot be used until they are tied up with the same straightjacket limitations and ip law cruft that makes adobe suck in the first place

    his point of view is the enemy of the free exchange of ideas

    allow me to throw insults at the control freak asshole, because he is destroying the philosophical underpinnings that makes everything since the age of enlightenment subject to corporate ownership. his way of thinking is very much the enemy

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  37. h.264 patent expiration? by OlRickDawson · · Score: 1

    When does the h.264 patent expire? I've been doing google searches, but haven't had any luck in finding the dates. My google search mojo must be weak today.

    --
    Ol' Rick Dawson had a farm EIEIO
    1. Re:h.264 patent expiration? by mkraft · · Score: 1

      When does the h.264 patent expire? I've been doing google searches, but haven't had any luck in finding the dates. My google search mojo must be weak today.

      In the U.S., patents expire 20 years after they were filed. Since H.264 is a fairly new codec (2003), the patent won't expire until at least 2023.

  38. anything that is merely a manipulation of data by circletimessquare · · Score: 1

    is simply an idea, not a product

    that some people do not understand this is the real problem

    a product is something like a iPhone, or a car, or a pressure release valve: a physical thing. anything composed of bits is not, and can never be considered, as a simple matter of logic and reason, to be a product

    your current understanding is simply logically incoherent

    not that there aren't laws that support your incoherence. but these laws, and people like you, stand in the way of the free exchange of ideas, and must be defeated for the sake of progress, if not simply for the sake of philosophical integrity

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:anything that is merely a manipulation of data by sznupi · · Score: 1

      I'm curious why do you draw a line that way. iPhone merely manipulated bits. Itself (as well as car or pressure valve) can be represented by a stream of them. And any algorithm can end up as hardwired piece of equipment.

      --
      One that hath name thou can not otter
    2. Re:anything that is merely a manipulation of data by Anonymous Coward · · Score: 0

      I think I let my fingers type before I really thought out a coherent post, so for this I was intellectually dishonest, and I apologize.

      I will just say that from observation it is obvious that to developers some bits/ideas have intellectual value (such as statistical algorithms), some bits/ideas have (for lack of a better term) monetary value (such as video games), and some simply have practical value (Java?), to name a few types of value.

      There is an inherent difference between these types, even though they are all bits/ideas. (Just as there are inherent differences between diamonds and charcoal, even though they are comprised of atoms.) Simply citing progress for the sake of the free exchange of ideas does not recognize the nature of this difference, nor does it elucidate how we reconcile such differences.

      Going back to your original post. Actually, it can be expensive to create ideas, both in time and money. Which is why university folk are often too busy writing grants or working on specific problems to capitalize on their ideas.

  39. Re:I don't notice a huge difference by snikulin · · Score: 1

    Try to use the Other OS? ;)

  40. Flash by CritterNYC · · Score: 1

    They won't lose anything. Sites that only use the proprietary codec will also support Flash. They *have* to. Chrome + Safari (the only browsers that support it) is less than 10% of online users.

    HTML5 video only really had a chance to supplant it if it was open and free. If H.264 is what sites were all going to use, you're just replacing one proprietary thing (Flash) with another.

  41. Flash by CritterNYC · · Score: 1

    All sites that support H.264 will continue to provide Flash video. They have to. Safari+Chrome (the only HTML5 H.264 supporters) is less than 10% of the online population. So that's not changing.

    I don't know any geeks using Safari. It's decent on Mac OS, but it's a loser on Windows. And it's a good chunk of closed source (geeks still prefer open). And Chrome is a privacy nightmare. Geeks don't like that. Chromium and the variants that don't have the privacy issues won't support H.264.

  42. its a matter of enforcement by circletimessquare · · Score: 1

    it takes time and energy and money to express your ideas in physical form

    but it takes no effort or time or expense to share an idea on the internet

    the creation of a physical object is a choke point that can be controlled: i can send 10,000 copies of a song from my home computer to anyone in the world, just by leaving a program running on my computer. but i can't publish and mail 10,000 copies of a song without considerable expense. therefore, "piracy" is a concept only a few could engage in in the pre-internet world, and ip law worked, because it was essentially a gentleman's agreement in an exclusive club of a few publishing companies. but in the internet world, piracy is simply the status quo, because its better, cheaper, and easier. you can't apply laws from a previous technological era on the behavior of tens of millions of teenagers around the world. so there's no enforcement possible, so the laws are defunct

    in other words, talk all you want about patenting ideas. who cares? certainly not the teenager in slovakia who just violated your patent without knowing or caring anything about all those archaic legal structures that simply don't matter to him. and you have no recourse to make it matter to him. the era, and the laws derived from that era, is simply over, and you have to get used to it. the internet has rendered patents on ideas, and copyrights, as philosphically untenable concepts

    the internet is disruptive technology. it will not be tamed by laws that depend upon the assumption that the production and distribution of media has choke points. instead, the laws will simply be ignored. look: the spanish came to the new world and rendered centuries old civilizations supporting the incan and aztec nobility extinct in a matter of weeks. was it fair to the previous era and the nobility who were invested in that structure to be so rudely toppled? who cares about continuity. who cares about fairness. its technological change: there's no stopping it.

    talk all you want about ip laws: the only question is one of enforceability, and ip laws are unenforceable in the internet world. you merely have to adapt to the new world. a set of laws depending upon pre-internet assumptions going back to the invention of the printing press, about the economics of the distribution of media, are laws that simply don't matter any more

    i'm not advocating for some far-out cybermarxist alternative fringe ideology that might work if everyone just started acting the way i think they should. what i'm doing is simply describing the already extensive reality of how things are already working in the real world, to people like you who seem to live in a pre-internet bubble of denial

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  43. Not HTML5 by Baloo+Uriza · · Score: 2, Interesting

    Too bad HTML5 specifies Ogg Theora, not H.264. This is about as much HTML5 as Silverlight.

    --
    Furries make the internet go.
    1. Re:Not HTML5 by ray_mccrae · · Score: 1

      HTML5 does not specify Ogg Theora. In fact HTML5 does not specify any codec, you know like it doesn't specify what types of images a browser should support. http://news.slashdot.org/story/09/07/02/184251/Browser-Vendors-Force-W3C-To-Scrap-HTML-5-Codecs

    2. Re:Not HTML5 by the_other_chewey · · Score: 1

      Too bad HTML5 specifies Ogg Theora [...]

      No it doesn't.

    3. Re:Not HTML5 by Baloo+Uriza · · Score: 1
      --
      Furries make the internet go.
    4. Re:Not HTML5 by the_other_chewey · · Score: 1

      Too bad HTML5 specifies Ogg Theora [...]

      No it doesn't.

      Yes, yes it does.

      Ah, well, thanks for confirming that it doesn't. Did you even read what you linked to?
      "[...]Formerly, the specification recommended ('should') support for Theora video and Vorbis audio encapsulated in Ogg containers.[...]"

      The final version of the spec doesn't any more, see "HTML5 turns neutral" in your wikipedia article.
      Yes, using theora/vorbis in an ogg container is allowed in HTML5. However, it is not mandatory,
      and clients don't have to implement it to conform to the spec. It is possible to completely adhere to
      the current HTML5 specs with H.264 video.

  44. Firefox "pure" open source? by sznupi · · Score: 1

    Somebody hasn't heard about Debian...

    --
    One that hath name thou can not otter
  45. Where is MNG already? by tepples · · Score: 1

    The only thing GIFs did that PNGs didn't was animation.

    And they still don't. It's been over a decade, and MNG still hasn't been widely implemented. What format (container+lossless codec) should one use for short (20 frame or less), looping line-art animations?

  46. Revenue model for non-US fork? by tepples · · Score: 1

    And the rest of the world cares because?

    How much would it cost Mozilla Corporation to move its headquarters, every developer, and all its other assets out of the United States?

    All we need is a non-US company (Canonical perhaps?) to fork Firefox and end this madness.

    Such a non-US company wouldn't have the Google ads providing the bulk of the revenue.

  47. a physical product by circletimessquare · · Score: 1

    is a concrete real world entity. it takes effort and material to produce it

    a stream of bits takes no effort to produce, and is infinitely reproduceable

    note i am talking about economic effort, not intellectual effort. of course it can take a lot of intellectual effort to produce a stream of bits. at the point where those stream of bits influence the production of a real world object, that is where you put the toll barriers in place

    you do not put the toll barriers on the flow of bits. for many reasons, not least of which this strategy never works

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  48. say you have some amazing new algorithm by circletimessquare · · Score: 1

    for video compression

    at some point, new hardware will built to take advantage of that new algorithm, which is where you can profit from the intellectual effort

    say you write an amazing song

    at some point, enough people will gather to hear a live performance of that song, which is where you can profit from the intellectual effort of creating that song

    but you don't put toll barriers on the flow of bits. for many reasons, not least of which this strategy never works, its always circumvented. its a false conceit to say this can ever work to make money. all you do is cut down on the free exchange of ideas, which impoverishes the whole of society overall. you make more money exchanging ideas freely, and profit from where real world effects emerge from those ideas

    a stream of bits takes no effort to produce, and is infinitely reproduceable. of course it can take a lot of intellectual effort to produce a stream of bits. at the point where those stream of bits influence the production or assembly of real world objects, that is where you put the toll barriers in place

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:say you have some amazing new algorithm by Anonymous Coward · · Score: 0

      We've erroneously equated software with ideas in this talk, but software is a realization of an idea. I would argue that software has a tangible aspect that ideas do not have, even though it is not made of atoms. For example, software is mutable; ideas, or art, don't need bug fixes or re-designs.

      That bits (and in turn software) are easily reproducible given 1) some computing environment and 2) bits are infinite in cost and zero in value brings up a different point. Anyone with a computer has the capacity to write and use software, allowing it to enter the collective conciousness more quickly. So perhaps the barrier before software enters the public domain should be lower than before a Sony Walkman does, and this barrier needs to be better defined.

      However, just because I can make a particular piece of software doesn't mean that I am entitled to in a liberal democracy. Say I have the means to produce an Oldsmobile. This does not grant me the right to do so. This is of course a ridiculous example, because in a liberal democracy (or any other system, practically speaking) most individuals do not have the means. However, collectively the general populous does have the means to make Oldsmobiles. This still does not give it the right. It only has the right if it buys the company or a license to do so.

      Regarding the point you make about toll barriers: officials put up toll booths to maintain the quality of roads. Tolls on software can be attributed to maintaining the quality of the software as time marches forward. Tolls on software, just as road tolls, can be and are abused, but that is beyond the scope of this discussion.

      An aside: cutting down the free exchange of ideas does not necessarily impoverish a society living in a liberal democracy. Cutting down on ideas that benefit the society does. This is why countries that are closest to liberal democracies still have defined and outlawed hate speech so as to prevent the spread of ideas that are detrimental to society (and individuals).

      All of the ideas behind software are not detrimental, and therefore should not be restricted. I believe in this strongly. But software can be manipulated by people, like cars, unlike ideas.

      I guess you could summarize my rambling posts as:
      |Software-cars| |Software-ideas|