Nick Cave’s stream is not the problem

I don’t think the stream, per se, was the problem with the Nick Cave concert last night. It’s was a Vimeo embed, they know how to stream and devices optimise for video. It’s the page around it that @dicefm needs to fix.

Trying to reload the video’s page on my iPad Pro last night, the browser had crashed. This suggests to me that it was the tracking and social overlays on the page embedding the video that was causing the problems.

Either too much JavaScript was running, even for recent devices, or the social overlay was making too many connections back the the Dice FM server or other users signed in to the system.

Once I switched to my laptop, a typical web developer’s high powered machine, the streaming was perfect. Of course, by then I’d missed the first third of the concert.

Within 30 minutes of watching the show on my laptop, the battery had dropped back to 40%. This again suggests that JavaScript and tracking is the cause of the problem, these scripts are black holes when it comes to power usage.

As long as the tracking and social overlays remain on the page, it’s likely the show will only be viewable on powerful computers. With fewer viewers on the page at any one time it’s possible a less powerful device might work but really, that’s a roll of the dice.

The real irony of all the social crap on the page is that it’s invisible the moment a user sends the video full screen.

Categorized as General

By Peter Wilson

Peter has worked on the web for twenty years on everything from table based layouts in the 90s to enterprise grade CMS development. Peter’s a big fan of musical theatre and often encourages his industry colleagues to join him for a show or two in New York or in the West End.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.