Stream start time increased by parsing in-band pssh when pssh present in manifest on Xbox One #5197
Labels
platform: Xbox
Issues affecting Xbox
priority: P2
Smaller impact or easy workaround
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
4.3.4
Can you reproduce the issue with our latest release version?
did not test
Can you reproduce the issue with the latest code from
main
?yes
Are you using the demo app or your own custom app?
custom app
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using?
Xbox One
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?
What configuration are you using? What is the output of
player.getConfiguration()
?The important setting here is drm.parseInBandPssh = true
What did you do?
Play streams with pssh in the manifest with shaka 3.1.2 and 4.3.4 and measure start times for a large number of streams on Xbobx one.
When we upgraded from shaka 3.1.2 to 4.3.4 we noticed a 600 ms increase in stream start time on Xbox one for streams with pssh present in the manifest. We determined that the start time increase was caused by unnecessarily parsing the in-band pssh for these stream.
What did you expect to happen?
We expected stream start time to be the same with version 3.1.2 and 4.23.4
What actually happened?
There was a 600 ms increase in average tune time with shaka 4.3.4 on xbox one for streams with pssh in the manifest
We determined that the start time increase was caused by unnecessarily parsing the in-band pssh for these stream.
The problem does not occur when the setting drm.parseInbandPssh is false.
The text was updated successfully, but these errors were encountered: