You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The baseline.html sample calls player.autoPlay = true; when autoPlay is not a property of MediaPlayer. The correct call is player.setAutoPlay(true);
If you use mediaPlayer.setAutoPlay(false), then playback does not autoplay, however it also does not start if the play button is pressed on the video controls.
In MediaPlayer.js, the attachView function hard codes the element autoplay to true. This means that if player.attachView is called after player.setAutoPlay, then the previous autoplay setting is overridden. The order in which the following calls are made against a MediaPlayer instance should not matter
This is fixed in my latest pull request, with one caveat... You cannot call both attachSource and attachView BEFORE calling setAutoPlay(false). Because autoPlay defaults to true, if both the view and the source are set the video will autoPlay, as per the correct default setting. I believe this is the correct, expected behavior.
…SwitchStream, done in composeStreams. The problem is, at this specific time, no StreamProcessor has been built. The return value of this function is always false."
This reverts commit 29c0eff.
To ensure VOD is always played until end (Dash-Industry-Forum#22).
See: Dash-Industry-Forum#1901
There are a number of problems here
player.attachView
player.setAutoPlay
player.attachSource
The text was updated successfully, but these errors were encountered: