On 12/13/2012 04:56 PM, Brion Vibber wrote:
On Thu, Dec 13, 2012 at 10:38 AM, Brion Vibber bvibber@wikimedia.orgwrote:
On Wed, Dec 12, 2012 at 2:50 PM, Rob Lanphier robla@wikimedia.org wrote:
I was able to play the WebM file of the locomotive on the front page of https://commons.wikimedia.org just now on my Nexus 7 using Chrome, so at least on very new stock Android devices, all is well. My much older Galaxy S didn't fare so well, though, so I would be willing to believe that Android devices with proper WebM support are still relatively rare. That said, the replacement rate for this hardware is frequent enough that it won't be long before my Nexus 7 is "much older".
I can play the current media on the front page of Commons in Chrome on my Nexus 7, but it won't play in position on either desktop < http://en.wikipedia.org/wiki/Serge_Haroche%3E or mobile < http://en.m.wikipedia.org/wiki/Serge_Haroche%3E ...
Sigh. :)
I think this relates to the page not being purged after the transcodes are updated. If you purge the page, will probably give the nexus a more playable flavour. http://en.wikipedia.org/wiki/Serge_Haroche should work on your nexus now ;)
TMH should add page purge to the job queue, but not sure why that page had not been purged yet.
Still some work to be done on compatibility...
I also notice that the <source> elements in the <video> seem to start with the original, and aren't labeled with types or codecs. This means that without the extra Kaltura player JS -- for instance as we see it on the mobile site right now -- the browser may not be able to determine which file is playable or best-playable.
For correctness we should include "type". But I don't know if that will help, the situation you describe. https://gerrit.wikimedia.org/r/#/c/38665/
But certainly will help in the other ways you outline in the bug 43101
AFAIK there are no standard source tag attributes to represent device specific playback targets ( other than type ), so we set a few in data-* tags and read them within the kaltura html5 lib to do flavour selection.
We of course use the Kaltura HTML5 lib on lots of mobile devices, so if you want to explore usage in the mobile app happy to support. For example including the payload into the application itself ( so its not a page view time )
peace, --michael