-
Notifications
You must be signed in to change notification settings - Fork 1.3k
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can Safari on MacOS play H.265 DRM VOD stream? #7300
Comments
Are you using src= or MSE? |
Hello @avelad we use MSE |
In my case I have always used src= for HEVC (due to my DRM provider). I leave the question open in case someone in the community knows how to answer it. |
@avelad can you please provide the sample code of used src= for HEVC, I believe this can help me. Currently my player always return error 3015. I use player.load() to player HEVC like other codecs. |
With |
ak if so, yes, I am using src= like you. because my useNativeHlsForFairPlay is true |
Since you use src=, only the Apple player is involved except to request the content license. In my case, HEVC works, I use fmp4 and there are also other qualities with AVC. I don't know how to help you much more, I recommend that you open an issue at https://bugs.webkit.org/ so they can help you better. Sorry! |
Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
If the question is related to FairPlay, have you read the tutorial?
Yes, but not find the information I need
What version of Shaka Player are you using?
4.10.6
What browser and OS are you using?
Safari 17.6 on macOS Monterey
Please ask your question
Everytime player load VOD stream DRM H.265, it throws error 3016. Do we need any other configuration or Safari MacOS does not support DRM H.265.
Manifest link:
https://vod06-cdn.fptplay.net/POVOD/encoded/2024/08/29/SolLevante_netflix_h265_drm_v2/hls_drm/master.m3u8
Attached is the manifest content.
h265.txt
Thank you
The text was updated successfully, but these errors were encountered: