good audio, but the jerky video is borderline unwatchable. Chrome/Linux. I noticed that top showed about 46% cut utilization so I'm guessing it's not able to use more than one core.
So, how exactly does this work? I'm trying to figure out where the media data is coming from; it looks like it's stored as a giant base64 string in a js file. Sort of a "maybe actually production useable" version of JSONVid (http://ajaxian.com/archives/jsonvid-pure-javascript-video-pl...)?
Anyway, there's no video element and no Flash, so none of those compatibility issues to worry about. If it can implement the full HTML5 media element API, I might actually use this one.
4 comments
[ 5.4 ms ] story [ 18.7 ms ] threadAnyway, there's no video element and no Flash, so none of those compatibility issues to worry about. If it can implement the full HTML5 media element API, I might actually use this one.