-
Notifications
You must be signed in to change notification settings - Fork 13
dashQualities does not enable quality selection #18
Comments
I'll look again into whether I can find a different criterion which identifies the adaptation set as video at that point. On a more general level, and regarding your stream being stuck on the lowest level: I experience the same with WEBM-DASH and dash.js - please check your stream in the dash.js sample player: http://dashif.org/reference/players/javascript/v2.4.1/samples/dash-if-reference-player/ See also: https://github.com/flowplayer/flowplayer-mpegdash#stream-compatibility |
@zerefel - quality selection should now work with your stream. Please confirm. |
@blacktrash Yes, it does work now, thanks! About feature requests, such as startLevel and smoothSwitching, can I request them and should I open new issues here on GitHub, or do you have them planned for the future? |
@zerefel - you can request them here, no prob. Note however, that the client library works very differently compared to hls.js:
|
Similar to hls.js' startLevel, but with default -1 (ABR). refs: #18 (comment)
@zerefel - you can now set (documentation to follow) |
@blacktrash - setting |
Hey there, when I enable the
dashQualities: true
flag, the quality selector is not displayed in the player menu. It seems like the plugin is unable to push the available bandwidths in the array, because the Adaptation Set does not have amaxFrameRate
attribute https://github.com/flowplayer/flowplayer-mpegdash/blob/master/flowplayer.dashjs.js#L78-L94If I comment out the if check, then it pushes the values.
Here is the full mpd file that I use. It was generated by Zencoder:
The MPEG-DASH stream plays fine, however it is stuck at the lowest quality setting, and I don't have the option to change the level or to at least set a starting level, like it's possible with the hlsjs plugin.
Let me know if you need me to provide additional info. Thanks!
The text was updated successfully, but these errors were encountered: