1221329 - Google Shaka Player loads mpd in Firefox, but fails to autoplay and then reports "multiple buffered ranges detected"

Status: RESOLVED INVALID

(Core :: Audio/Video: Playback, defect)

Description

[Chris Peterson [:cpeterson]]

STR:
1. Load Shaka demo player: http://shaka-player-demo.appspot.com/
2. Set "Custom manifest URL" to http://www.bok.net/dash/tears_of_steel/cleartext/stream.mpd
3. Press the "Load Stream" button

RESULT:

Nightly 45 loads the video from the mpd, but it does not play automatically like it does in Chrome, Safari, and MS Edge. IE fails to load the mpd, for some reason. We log the following error to the web console:

Player error error { target: null, isTrusted: false, detail: TypeError, eventPhase: 0, bubbles: true, cancelable: false, defaultPrevented: false, timeStamp: 1446585931411407, NONE: 0, CAPTURING_PHASE: 1, AT_TARGET: 2 } app.js:962:3
app.onPlayerError_() app.js:962
shaka.util.FakeEventTarget.prototype.recursiveDispatch_() fake_event_target.js:143
shaka.util.FakeEventTarget.prototype.dispatchEvent() fake_event_target.js:121
shaka.player.Player.prototype.load/<() player.js:352
(Async: promise callback) shaka.player.Player.prototype.load() player.js:321
app.load_() app.js:758
app.loadDashStream()

If I press the play button, the video will start, but hiccups after a couple seconds and logs the following console error:

SBM video/mp4: multiple buffered ranges detected: Either the content has gaps in it, the content's segments are not aligned across bitrates, or the browser has evicted the middle of the buffer.
source_buffer_manager.js:455:1
shaka.media.SourceBufferManager.prototype.detectMultipleBufferedRanges() source_buffer_manager.js:455
shaka.media.Stream.prototype.onUpdate_() stream.js:515

Nick Desaulniers originally reported this issue in the Shaka Player's GitHub repo for FF 41:

https://github.com/google/shaka-player/issues/101

Comment 1

[Jean-Yves Avenard [:jya]]

likely the same as bug 1194624
(for the auto starting problem)

Comment 2

[Jean-Yves Avenard [:jya]]

I can't reproduce the "hiccup".

Does the video plays for you or not ?

I also see no error in the web console (Command Option K)

Comment 3

[Chris Peterson [:cpeterson]]

(In reply to Jean-Yves Avenard [:jya] from comment #2)
> I can't reproduce the "hiccup".
> 
> Does the video plays for you or not ?

I only see the hiccup intermittently (the Pac-Man buffering icon appears momentarily about four seconds into the video). After waiting a second, the video then continues to play for me. I think the hiccup is more likely to happen if I click the play button quickly after first loading the video.

Comment 4

[Jean-Yves Avenard [:jya]]

pacman appears when you change resolution or start the video if you have less than 10-15s of data buffered.
After that playback resume.

Comment 5

[Chris Peterson [:cpeterson]]

In Firefox (42 on OS X), the player jumps either tries to jump 500 kbps to 2000 kpbs around time 0:04 or jump from 500 kbps to 800 kbps around time 0:15. Chrome only seems to jump from 500 kbps to 2000 kbps around time 0:20, after more data has been buffered. Does the player think we have buffered more data than we have? Why the apparent difference in behavior?

Comment 6

[Jean-Yves Avenard [:jya]]

I can't explain the difference. Chrome appears to cache content downloaded via XHR/https ; we do not.

In any case, things work as they should be IMHO (other than playback not starting automatically)

You could try with one of the build from https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=849e4c4784ca and see if that helps.

Comment 7

[Jean-Yves Avenard [:jya]]

BTW, shaka player has issues due to bug 1188887. This is only fix in 44 and later. We could always ask to uplift that change.

Comment 8

[Chris Peterson [:cpeterson]]

OK. I will close this bug as invalid.

I don't think we need to uplift bug 1188887 to Beta 43 unless we know of broken websites other than the Shaka Player's demo page. :)