... in which case the problem is that inline/thumbnail usages of videos by default use a 'popup transform' that -- until currently desktop-only JavaScript is loaded -- is just a thumbnail image plus a link to the original file. (The code for the proper player is hidden away where it can be loaded into a popup window by the JS.)

This is pretty awful on mobile at present, as the thumbnail does nothing when you click on it, while there's a 'play media' link that sends you to the highest-resolution file you could possibly download. This means you're trying to play a full HD 1920x1080 video from the original VP9 source, which while a great format can be somewhat CPU-intensive.

I have some planned refactoring that should improve this by including a stripped-down player inline for the mobile/non-JS cases, but beware it wouldn't get deployed until sometime mid to late next week even if we hurry it. (We do not deploy on Fridays or weekends!)

-- brion

On Thu, Oct 29, 2015 at 7:39 PM, Brion Vibber <bvibber@wikimedia.org> wrote:
We don't yet have fully "on purpose" multimedia support on mobile -- eg if it works at all, that's awesome. :) But it's probably sub-ideal in a number of ways. (On iOS in particular we have *no* playback except in the desktop mode due to Safari's lack of native WebM or Ogg support; the ogv.js JavaScript playback has only been integrated on the desktop mode so far, as we need to clean up TimedMediaHandler's JS-side code to run cleanly on mobile... and not suck on desktop.)

* Are you viewing the File: page in a browser directly, or some page that includes the file on it? (If the latter, which page?)
* Are you pressing the 'play' button on an image thumbnail, or clicking the "download original file" link, or something else?
* What device are you using?
* What Android version are you running on?

General issues:
* There's no manual resolution selection override in the user interface, so you might be getting a high resolution file that's too slow to decode.
* In Firefox in particular you may not be getting the benefit of hardware acceleration for WebM video decoding.
* The 'Android default browser' may or may not exist on any given device (many newer devices just have Chrome, so I can't test it locally on my Nexus 5 or 5x).

There may or may not be any 'fixes' we can make in a short term. Note there are *no* WMF resources assigned to video at present, so things get fixed only as someone interested in the topic gets to them.

-- brion

On Thu, Oct 29, 2015 at 7:16 PM, Pine W <wiki.pine@gmail.com> wrote:

I just tried playing the video on Android. Good news, bad news:

The video plays as expected in the Wikipedia app.

The video has major problems playing in Firefox for Android and the default Android browser for mobile web.

Can someone else please test those latter two configurations? If problems are confirmed, how long will a fix take, keeping in mind how close we are (4,998,070 articles) to the 5M milestone?


Multimedia mailing list