A different video card, codec chain, and on and on, can yield a very experience. Being an early adopter of many Harry Potter-esque moving pictures can yield nic

A different video card, codec chain, and on and on, can yield a very experience. Being an early adopter of many Harry Potter-esque moving pictures can yield nice content, but it will invariably cause client issues. As I mentioned in another post, it works fine in Chrome 34 on the same hardware that it struggles dramatically with in Chrome 32. Both of them have hardware decoding enabled, and so on. The Chrome 32 instance has no problems at all playing video anywhere else. Indeed, on that same line, the videos don't load at all on Chrome on the Nexus 5. The N5 of course supports h264, and has no problem on any other site that I've ever discovered. Maybe their server is now overloaded (EDIT: Okay they're using S3....going to be an ugly bandwidth bill from that...and it's fully responsive), but it also doesn't load on the iPad 3rd generation running iOS 7. Again just black boxes. EDIT: I wonder if it's because they're (s3) setting the content type to octet-stream, rather than video/mp4. Some clients seem to be going on alternate decode paths or are refusing to display it because of that. e.g. Content-Length:6915107 Content-Range:bytes 0-6915106/6915107 Content-Type:application/octet-stream There's a lesson in here somewhere.