Slashdot Mirror

← Back to Stories (view on slashdot.org)

Vimeo Also Introduces HTML5 Video Player

Posted by timothy on from the how-about-set-top-boxes dept.

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."

4 of 369 comments (clear)

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

    I shed not a tear for you.

    --
    Better known as 318230.
  2. 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.
  3. 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.
  4. 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.