No unified media pipeline on stable Android Chrome 52?
Reported by
to...@interlude.fm,
Aug 10 2016
|
|
Issue descriptionExample URL: https://s3.amazonaws.com/storage2.interlude.fm/dev_temp/tomer/chrome_ump_playbackrate/index.html Steps to reproduce the problem: 1. Navigate to provided URL on stable Android Chrome 52. 2. Play video 3. Click buttons to change playbackRate What is the expected behavior? Video should respond to playbackRate changes. What went wrong? Video keeps playing at original rate, ignoring the playbackRate property. This leads me to believe that video is not actually played via unified media pipeline (since this was the behavior on previous Android Chrome versions). Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? N/A Chrome version: 52.0.2743.98 Channel: stable OS Version: 6.0.1 Flash Version: Tested on a Nexus 5X and HTC One M9. Toggling the UMP flag under chrome://flags does not make a difference. In both cases, playbackRate is ignored. This works well on Android Chrome Beta 53.0.2785.49, and I'm 90% sure this also worked on Chrome 52 when it was in beta...
,
Aug 10 2016
(hopefully 100%)
,
Aug 10 2016
Sorry, not sure what you mean. Is UMP being rolled out gradually? Is there no way to enable it on current stable 52.0.2743.98 build? Should we expect UMP to only arrive on 53?
,
Aug 10 2016
It's being rolled out gradually since it also brought support for the data saver proxy and we needed to monitor server loading. I'll be pushing it to 100% shortly so no need to wait for 53 (except on WebView).
,
Aug 11 2016
100% pushed today; so you shouldn't see this by tomorrow.
,
Aug 11 2016
Awesome, it works now, thanks! Just out of curiosity - how does this roll out work? I mean how are you able to disable a client feature remotely? Does the client make a request to your servers to get flag overrides? Does this happen on startup or are changes pushed?
,
Aug 11 2016
https://cs.chromium.org/chromium/src/media/base/media.cc?l=90 https://cs.chromium.org/chromium/src/base/metrics/field_trial.h https://cs.chromium.org/chromium/src/components/variations/ The above detail how it works. For UMP, by default users are enabled, but we have the ability to push a disabled field trial group. Field trials are pulled by the browser startup if possible, and if the user has opted into metrics collection, we'll get data about how the experiment is going (crash counts, histograms, etc).
,
Aug 11 2016
Thanks! Appreciate the detailed reply :) |
|
►
Sign in to add a comment |
|
Comment 1 by dalecur...@chromium.org
, Aug 10 2016