Super Bowl Webcast Poor Quality, Player Broken, Bad Experience

Screen Shot 2013-02-03 at 7.19.53 PMLast year, NBC Sports failed in their execution of the first Super Bowl webcast and this time around, isn’t doing any better. Tonight’s webcast has really bad video quality, lots of pixelation and a stream that looks to be encoded at less than 1Mbps. The webcast player won’t load the Twitter feed, which is giving me an error of “Failed to contact the origin” and the video has lots of buffering. When I join the webcast, I’m first given an ad, then the game comes on for a few seconds and then another ad gets delivered. Clearly the ad delivery function isn’t work right either.

Screen Shot 2013-02-03 at 8.09.07 PMIt’s also interesting to note that Akamai’s website that always shows how many live and on demand streams are running on their network at any given time is showing a total active stream count of zero. It’s as if asked Akamai to shut down that section of their “Visualizing Akamai” dashboard for the Super Bowl webcast so that no one will know the kind of traffic is getting. It could just be a coincidence, but I doubt it as the Akamai page was working before the Super Bowl started.

One might suggest that the reason is encoding the video at such a low bitrate is to reach viewers in areas where they don’t have great connectivity, but as the webcast player support page states, the Super Bowl webcast is “limited to the United States” viewing only. The average broadband speed in the U.S. is at least 5Mbps, maybe even 7Mbps depending on which data you look at. So delivering what appears to be an 800Kbps stream with lots of pixelation makes for a bad experience, no matter what kind of Internet connection you have. Of course tomorrow, I’m sure we’ll see a release from calling the webcast a “success”.

For all the people who talk of streaming media technology supposedly replacing broadcast TV distribution, this is just another example of many where one webcast can’t even be delivered to a small audience with HD video, or a reliable user experience. And for those industry folks who want to try and argue that soon we’ll all be streaming in 4K, 3D or using H.265 at 15Mbps – please come back to the real world.

From the viewing experience, one would think this is some kind of “new” technology being used, when in fact it’s been around for 15 years now. Another Super Bowl, another poorly executed webcast.

  • Worked great for me, and blown up on a 55inch it looked like Netflix, and just fine on the iPad. They had an FAQ about it being ABR too, I think I found 5 rates. Different options were cool, smooth player, and I didn’t have to pay for a cable subscription!

  • Don Kichline

    I have to concur with Blair. I watched the broadcast on my iPad. I had no difficulties and the picture looked terrific. Granted the screen is small comparatively to a television, but as far as I was concerned, it was a success.

  • Joey

    The video quality stunk even on my Macbook. Choppy, fuzzy and not sharp at all. I have no idea what it was encoded at, but it wasn’t very good. And I have a 20 MB connection with Uverse. It should have looked a lot better than it did.

  • lynnwashere

    oh man….my experience was aweful! 4.5 hours of buffering every 30sec.
    kill me!
    I thought it was my connection so I checked out Hulu. It streamed beautifully, so I know it wasn’t my connection.
    Boo on

    • Don Kichline

      When did you have the problem? Early in the game, or later? I watched the first half on TV and then the last quarter on my iPad. My only real complaint is that everytime I switched to another app it forced me to watch the opening commercial again. The buffering was only about 10 seconds and then it streamed in great, no pauses or rebuffering.

  • Thierry

    Dan, hevc hd will bring half the bitrate, do not get fixed on 4k!