-
Notifications
You must be signed in to change notification settings - Fork 13
Progressive download on byte-range segmented webm file #19
Comments
@zerefel - as mentioned previously: See also: Dash-Industry-Forum/dash.js#2044 dash-mse-test.appspot.com uses a different library (and has different issues). You would/should also set `dashCodecs: "vp9", but as you noticed it doesn't work properly. |
@blacktrash JWPlayer's implementation seems to be able to switch the underlying provider to Shaka, which enables WebM-DASH to be played back properly. Given that this is a problem in the Dash.js plugin, you can close this ticket if you feel like nothing could be done. I will wait for the plugin to mature before switching my platform to WebM-DASH as the main video format. |
no problem with webm-dash vp9 video codec and opus audio with dash.js 2.5.1 (using videojs) |
@arpu How have you segmented your files? Can you link a sample mpd that you use? |
@arpu - will try that; however for mpegdash and VOD there's currently a showstopper with dash.js 2.5.x: Dash-Industry-Forum/dash.js#1901 |
Hey, it's me again.
I ran into a problem where the entire webm file is downloaded before playback can begin. I am using this DASH playlist for testing purposes: https://s3.eu-central-1.amazonaws.com/overpro.zencoder.eu/B1615JjGZ/dash/B1615JjGZ.mpd
Flowplayer version: Commercial 7.0.2
Flowplayer DASH.js version: latest commit in GitHub
Relevant part of Flowplayer config:
I also tried to remove the
initialVideoQuality: 3
setting but that did not help, it just made the player download (again - progressively) another video quality setting, for instance 480p.I expect the stream to work similarly as in this demo (same manifest used):
http://dash-mse-test.appspot.com/dash-player.html?url=https%3A%2F%2Fs3.eu-central-1.amazonaws.com%2Foverpro.zencoder.eu%2FB1615JjGZ%2Fdash%2FB1615JjGZ.mpd&autoplay=on&adapt=auto&flavor=
The text was updated successfully, but these errors were encountered: