Slashdot Mirror


YouTube Live Streams Now Support HTML5 Playback and 60fps Video

An anonymous reader writes: YouTube today announced that it is rolling out HTML5 playback and has added 60fps live streaming to allow users to broadcast in real time. "When you start a live stream on YouTube at 60fps, we'll transcode your stream into 720p60 and 1080p60, which means silky smooth playback for gaming and other fast-action videos," YouTube said in a statement. "We'll also make your stream available in 30fps on devices where high frame rate viewing is not yet available, while we work to expand support in the coming weeks."

6 of 60 comments (clear)

  1. Re:Silky smooth? Hah by agoodm · · Score: 2

    1080p 60fps works fine on ubuntu with sandy bridge era built in graphics on a lenovo x220 which has such inadequate cooling...... So its not Intels fault...

  2. Bring Back Background Play by SoVi3t · · Score: 2

    Perhaps now they can bring back background play for mobile devices, so I don't have to stay on the youtube app to listen to music/podcasts/etc posted there.

    --
    Defender of Microsoft and Communism!!!
  3. So they didn't work with OBS? by Hohlraum · · Score: 2

    OBS being easily THE most popular streaming software around, which is open source and free. That's awesome Google, way to blow it.

  4. Codec? by manu0601 · · Score: 2

    What in and out codec are? You do not transcode into HTML5, it is just a container format. You transcode H264 in VP8 or Ogg for instance.

    1. Re:Codec? by Z00L00K · · Score: 2

      Much about the video, but what about sound? Still just stereo sound on most YouTube videos.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  5. Re:can't wait to see the game by hairyfeet · · Score: 2

    I can't wait to hear even more people bitching about YouTube being "broken" because HTML V5 is still buggy as fuck and on Chrome/Chromium bas when something goes wrong? You get ZERO useful information that you can use to troubleshoot the issue, just a vague "encountered a problem, please try again later" which makes Windows number code errors look like fountains of information by comparison.

    Is it REALLY so impossible to give the USER the choice of whether they want HTML V5 or Flash? is it really so damned hard for a company the size of Google to give meaningful error messages? All this rollout, along with the previous playback rollout has done is strengthen my belief that HTML V5 is a classic "we have to do SOMETHING" approach where you take the first alternative without bothering to ask "is this really better than what we had before, or just different?" as HTML V5 still supports less than half the features that Flash supports and what features it DOES have? It uses more memory and CPU and often works worse than what it was supposed to be the cure of!

    --
    ACs don't waste your time replying, your posts are never seen by me.