-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[PARAMOUNT GLOBAL] - PS4 - Video Start Failure In New MSE Based WebMAF #4315
Comments
So WebMAF is a browser-like environment? Is there anywhere we could access that for debugging purposes? We don't have a PS4. v4.1.1 fails, but v3.2.1 works? What about later v3.2 releases, such as v3.2.8? Does v3.3 work? Does v4.0? |
Yes it is. Hmm 🤔, I think having an actual PS4 (test-kit or dev-kit) device is the only way unfortunately. Just a regular production PS4 doesn't cut it either. It needs to be one of their test or dev-kits. I randomly tried a few builds between 3.2.1 and 4.1.1. None worked. I know I did 3.3.1 and 3.3.7 for sure. I will run additional tests with other builds and be more thorough, in case if I get lucky and find a 3.x build that works |
We will test the versions to see if something later works. Also, I'll be shipping a PS4 dev kit and pc to @littlespex for debugging. This will take some time. |
One of the things that needs changing is that shaka.util.Platform.isApple() returns true for PS4. Not sure if that was the only cause of MediaCapabilities.decodingInfo() failed error that I was getting for DASH/PlayReady. At some point playback was starting but it was very glitchy. Hopefully I'll have some time to look at it this/next week. |
@bcupac thank you. |
Can you create a PR similar to #3808? Thanks! |
This would force the use of our polyfill for MCap, since we force that on for
That would make it more explicit to force the MCap polyfill, but it sounds like it's already happening by accident. Perhaps we should try fixing |
I would mark this a P1 (since everything is broken in WebMAF), but I'm marking this a P2 (lower priority) since that is not an officially supported platform for the project. And since my team can't do anything about it, I'll assign this issue to the groups of folks who have responded so far (and @littlespex, who is apparently getting a PS4 dev kit). Thanks! |
On this new MSE based WebMAF environment |
PR is there just for clarity, as joeyparrish said it was polyfiling accidentally and it should as PS4 doesn't have navigator.mediaCapabilities |
@bcupac That being said, I have another PS4 issue that involves VTT cue parsing. I haven't submitted a ticket yet, but I will shortly. So stay tuned 😉 |
Have you read the FAQ and checked for duplicate open issues?
Yes, I have. I searched for duplicates and couldn't find any
What version of Shaka Player are you using?
Shaka Player 4.1.1
Can you reproduce the issue with our latest release version?
Yes
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?
N/A
What browser and OS are you using?
Recently released WebMAF 3.0 for Play Station 4
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
WebMAF/v3.0.1-rc-6-g6b785d8b
SDK Version: 9.5
What are the manifest and license server URIs?
http://dash.edgesuite.net/envivio/EnvivioDash3/manifest.mpd
What configuration are you using? What is the output of
player.getConfiguration()
?Default configuration. Using it as is.
What did you do?
What did you expect to happen?
I expected it to start playing
What actually happened?
Playback did not begin. I can see that player loaded the manifest and then state changed to
buffering
. See the logs for details.This page works and plays just fine if I use Shaka Player version 3.2.1 and below in the same environment.
Logs
User Agent
The text was updated successfully, but these errors were encountered: