Curiously this player causes <i>more</i> CPU load than a flash video here on chrome/OSX. Must be something specific to this implementation, though. The html5 player on youtube causes less load than flash.
It's not terribly relevant to HTML5, but I wracked my brain over trying to figure out what song plays in the video and how I know it.<p>After listening to a bunch of tracks and going through my music collection, I found it. It's a re-orchestration of Bond's "Oceanic" (Bond, the string quartet). I'm not sure if their version is original, or if that's a remake of something else (they do like to do updated dancy versions of classics like the 1812 Overture).<p>If anyone's interested anyway, it was bugging me like crazy.
Who controls the buffering logic in this case? Is it entirely up to the browser or it's configurable somehow by client's JS?<p>I'm on a less-than-perfect connection here and all I'm seeing is hiccups and it doesn't try to slow down and fill the buffer
While this is nicely presented, I'm not really seeing what it adds, especially for something that's not open source and they intend to charge for.<p>Surely the point of HTML5 video is to have these controls built into the browser so they work with accessibility, and your custom key combos, and your touch control webpad etc. And the non-control bits are just CSS.<p>Okay it looks better than the default Chrome player, but really that's not very hard. Seems a step back for Safari though.
How does this work? As far as I knew, it was the src attribute you set on source tags.<p><source title='<a href="http://d31j8lt3uybmqs.cloudfront.net/sublimevideo/dartmoor.mp4" rel="nofollow">http://d31j8lt3uybmqs.cloudfront.net/sublimevideo/dartmoor.m...</a> type='video/mp4' />
I think it's quite unfair to promote a piece of software with such a surreal video and comforting soundtrack. All of my attention was drawn to the video instead of looking for more info. There doesn't seem to be any relevant information for developers in links on the site or a faq.
Question: How exactly does this work? Is the player code (video decompressing etc.) part of the browser code or does it utilize players on my desktop (divx or even vlc)? It seems that html5-video is codec-independent. But the codecs have to be somewhere, right?
No Firefox support? That seems pretty arbitrary; why not show my browser the page and let it decide if it can render it?<p>Oh yeah, it's by a web designer...