Comment by shinratdr

12 years ago

I don't know why someone would use a liveblog when they offered a very capable livestream. Also quite the rookie mistake considering the AMD logo they showed had "FireGL" written right on it.

7 comments

shinratdr

Reply
spangborn  12 years ago

It wasn't available on Windows, which many of us work on. Also, some work networks are more restrictive and block it.

  • shinratdr  12 years ago

    It was, just not via any typical Windows browser because of their lack of support for HLS. Simply copying the URL into VLC would have worked.

capnjngl  12 years ago

Livestream from Apple was OSX-only.

  • eyko  12 years ago

    More like Safari-only. I couldn't watch it on Chrome on OSX (unless I changed my user agent to Safari)

    • shinratdr  12 years ago

      Whether or not HLS is supported by Chrome is quite confusing. I'm not surprised they blocked it at a User Agent level (which Google does all the time for their services, Reverse Image Search & Maps being good examples).

      While Chrome has supported HLS for a WebM backend for some time now, documentation on their support for HLS with an MP4 backend is unclear. It seems to work now as of Chrome 26, but that wasn't always the case. It also works fine on Android devices past 3.2 because of Google TV.

    • dhruvmittal  12 years ago

      Seriously, that was a little absurd. Why exactly does Apple want to limit its audience by only allowing people using Safari on OSX to watch it? I doubt all the markets are so saturated that every potential iPhone, Macbook, and Mac Pro customer is already on OS X.

      If I didn't happen to have a Macbook as a work PC for the summer, I'd have missed the Macbook Air announcement. But god, do I want one.

      1 reply →