-
Notifications
You must be signed in to change notification settings - Fork 70
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
Fairplay and Video.js not work with Safari 15 for iPad and iPhone #140
Comments
I think it's broken on Apple's side. |
Yeah, I tested a video with pure DRM without videojs and it worked. |
Major fail at our website now (all our stuff is encrypted). |
Any idea on how to fix this? |
Workaround perhaps? |
Is Apple even aware? This seems critical, we have a ton of clients complaining. |
What is the expected Safari 15 / Apple error happening here? I'm intermittently seeing either:
Updated comment to remove separate non-related issue. |
"The error didn't come from video.js EME extension. To reproduce you can try implement FairPlay using pure JavaScript or using FPS_in_Safari_Example.html that come with FairPlay Streaming Server SDK. You will get the same error on iOS15. — nonth 7 hours ago" https://developer.apple.com/forums/thread/690429 |
By default, we still use the legacy standard for EME on Safari. Supposedly, the issue doesn't occur with the latest standards based EME API. I've been playing around locally and, unfortunately, haven't been able to get it working. |
FYI - Disable GPU rendering (GPU process: Media) in the Safari Experimental Settings, and restart Safari, all the players start showing video - comment from: https://developer.apple.com/forums/thread/690429 . This worked for non-videojs player |
So, we just released videojs-contrib-eme 3.10.0. This switches Safari to use the standards based API rather than the legacy API by default. In conjunction with using CMAF based segments, fairplay should potentially start working again. |
Thanks for the work gents |
So, after some more testing, we realized that there's a breaking change as part of #142. This is because the format of initData changes when switching from the legacy to the standards API. So, upgrading to 3.10.0 will potentially break your player without some changes on your side. To that end, we've decided to revert that change and release 3.10.1 without it. Then we'll do a major version to account for this. |
We did make some changes in back and it 3.10 works for us. Works better than 3.9, but iOS15 still has some issues with ~30% of videos (which was 100%) |
@BakurL yeah, we see some issues on our end as well. I think ultimately, we'll need to wait for apple for the remaining issue. Also, sorry that you'll need to make some more changes once 4.0 comes out. Hopefully, it'll allow you to simplify things on your end. See #147, which still needs some reviews by my teammates, but it's working for me. |
No worries, patch worked much better for us than previous version. Thanks for the info |
iOS 15.1 is out today. I just downloaded and confirmed that with cmaf segments things play correctly with the old version of videojs-contrib-eme. Going to test out ts segments now. |
Confirmed that ts segments work as well for me. |
Tested on ipad and iphones and works too, thanks |
demo videojs work on safari |
Hi there,
This week I tried videojs-eme on the new Safari 15 using iPhone or iPad and it didn't work.
The feedback says the content is not supported, but version 14 works.
The text was updated successfully, but these errors were encountered: