Cannot play HLS/Fairplay content on Safari with V4 #4312
Labels
component: FairPlay
The issue involves the FairPlay DRM
priority: P1
Big impact or workaround impractical; resolve before feature release
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
Comments
avelad
added
the
priority: P1
|
Duplicate #4211 I am having a same issue |
|
It will be resolved with #4309 |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@fredrik-telia please open a new issue with your case. Your case is different from this. |
|
Thanks, will do 👍 |
github-actions
bot
added
the
status: archived
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
Latest, 4.x
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
If custom app, can you reproduce the issue using our demo app?
Cannot test
What browser and OS are you using?
Safari on Mac
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()?What did you do?
Played a linear channel or a VOD in Safari.
What did you expect to happen?
Playback to start
What actually happened?
We are having problems playing HLS/Fairplay content with Shaka V4.
The license request towards the license server seems to work as expected. We originally had issue with that the the defaultInitDataTransform has changed so that skd:// was no longer removed in the data sent in the license request (which V3 does). In addition to successful license requests we also see that manifests and media segments are retrieved from our server but playback never starts. After a long period of time we get an error 3016 saying that media cannot be decoded. We can play the same streams using V3 and we can also play unencrypted versions of the streams using V4.
Comparing the logs between V3 and V4 we see differences when it comes to implementation of MediaKeys. If I understand correctly, V4 is using the EME for handling the media keys where as V3 is using a poly-filled version?
We are out of ideas on how to troubleshoot this further. Do you have any suggestions?
Is it possible to configure the implementation of MediaKeys in V4 to at least test to see if that is the root cause?
The text was updated successfully, but these errors were encountered: