Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Location as baseURL for segments [Fixes #1887] #1941

Merged
merged 1 commit into from
Jun 2, 2017
Merged

Using Location as baseURL for segments [Fixes #1887] #1941

merged 1 commit into from
Jun 2, 2017

Conversation

TobbeEdgeware
Copy link

This implements the use of Location@MPD not only for manifest updates, but also as BaseURL for fetching of segments as discussed in #1887.

As the manifestUpdate, only the first Location element is used.

A test vector is available at http://vm2.dashif.org/dash/vod/Location.mpd

@dsparacio dsparacio merged commit 79d3dac into Dash-Industry-Forum:development Jun 2, 2017
// In the following, we only use the first Location entry even if many are available
// Compare with ManifestUpdater/DashManifestModel
if (manifest.hasOwnProperty('Location')) {
baseUri = urlUtils.parseBaseUrl(manifest.manifest.Location_asArray[0]);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TobbeEdgeware, is there too much manifest ? I have an issue when I try to play the stream :

http://wowzaec2demo.streamlock.net/live/bigbuckbunny-enc-wv.stream/manifest_mvtime.mpd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants