Shaka Player DASH live buffering issue after CAF update (4.3.4 to 4.9.2) #8060
Comments
|
Looks like an issue in trick mode stream creation. We've prepared fix for this, I think it needs to be backported to shaka v4.9 #7229 |
|
That change is already in all v4.11+ releases (so all currently-maintained branches), and also appeared in v4.9.25. @jakubjereczek, can you try setting If those don't work, can you please try |
joeyparrish
added
type: question
avelad
added
the
status: waiting on response
|
4.9.25: Possible encoding problem detected! Unexpected buffered range for reference
shaka.media.SegmentReference { startTime: 1740649485.531277, endTime: 1740649487.531277, trueEndTime: 1740649487.531277, startByte: 0 } from URIs ... should be { start: 1740649485.531277 end: 11740649487.531277} but got { start: 1740649485.651277, end: 1740649487.611277}
4.9.36: 4.13.15: It not available for Cast Receiver yet. [ 4.008s] [castx.common.scriptLoader] library(//ajax.googleapis.com/ajax/libs/shaka-player/4.13.15/shaka-player.compiled.js) failed to load but I used a plain Shaka player: Possible encoding problem detected! Unexpected buffered range for reference
{
"startTime": 1740651791.531277,
"endTime": 1740651793.531277,
"trueEndTime": 1740651793.531277,
"startByte": 0,
"endByte": null,
"initSegmentReference": {
"startByte": 0,
"endByte": null,
"mediaQuality": {
"bandwidth": 3040870,
"audioSamplingRate": null,
"codecs": "avc1.64001f",
"contentType": "video",
"frameRate": 25,
"height": 720,
"mimeType": "video/mp4",
"channelsCount": null,
"pixelAspectRatio": "1:1",
"width": 1280,
"label": null,
"roles": [],
"language": null
},
"timescale": null,
"segmentData": null,
"aesKey": null,
"codecs": "avc1.64001f",
"mimeType": "video/mp4"
},
"timestampOffset": 0,
"appendWindowStart": 0,
"appendWindowEnd": null,
"partialReferences": [],
"tilesLayout": "",
"tileDuration": null,
"syncTime": null,
"status": 0,
"preload": false,
"independent": true,
"byterangeOptimization": false,
"aesKey": null,
"thumbnailSprite": null,
"discontinuitySequence": -1,
"allPartialSegments": false,
"partial": false,
"lastPartial": false,
"codecs": "avc1.64001f",
"mimeType": "video/mp4",
"bandwidth": 3040870,
"segmentData": null
}from URIs ... should be {
"start": 1740651791.531277,
"end": 1740651793.531277
}but got {
"start": 1740651791.611277,
"end": 1740651793.651277
} |
shaka-bot
removed
the
status: waiting on response
|
the latest version is 4.13.6 not 4.13.15, can you check with 4.13.6? Thanks! |
|
Sorry, I accidentally wrote it wrong - the last one check was on 4.13.6. I used this one build: https://github.com/shaka-project/shaka-player/releases/tag/v4.13.6. |
Have you read the FAQ and checked for duplicate open issues?
Sure
If the problem is related to FairPlay, have you read the tutorial?
No related
What version of Shaka Player are you using?
4.9.2
https://developers.google.com/cast/docs/release-notes?hl=pl
Can you reproduce the issue with our latest release version?
I reproduced using ShakaPlayer 4.12.6
https://cdnjs.cloudflare.com/ajax/libs/shaka-player/4.12.6/shaka-player.compiled.js
Are you using the demo app or your own custom app?
For the test I used a completely clean application
What browser and OS are you using?
Chrome / Firefox
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Chromecast 4 with GoogleTV, but also reproducible on other devices
What are the manifest and license server URIs?
What configuration are you using? What is the output of
player.getNonDefaultConfiguration()?We use the default CAF configuration, we do not modify it by extending the shakaConfig.
What did you do?
What did you expect to happen?
What actually happened?
In the latest CAF update, the Shaka Player was upgraded from version 4.3.4 to 4.9.2. This new version causes problems with some DASH livestreams that worked before.
After starting the program, the stream keeps buffering, even though the player is still fetching new segments in the background. This issue only affects one client using external streams and might be related to the manifest setup. The problem only happens with Shaka Player, as other players like ExoPlayer and RxPlayer don't have this issue.
An example of what I mentioned earlier, new segments are constantly being fetched in the background:
In the DEBUG version, ShakaPlayer reports the following issues:
Full logs:
Manifest
What do you think about it, do you need any additional data from me?
Maybe it's because of this manifest? Is intentionally not supported? generally we can use the previous version - but unfortunately without updates.
Are you planning to send a PR to fix it?
The text was updated successfully, but these errors were encountered: