-
Notifications
You must be signed in to change notification settings - Fork 130
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
INCOMPATIBLE_KEYSYSTEMS error using DASH/Widevine on Panasonic 2019 #1219
Comments
In addition to above I've set
|
Hi, The Are you sure that widevine is available on this device? Perhaps the key system string is slightly different? It could also be the In the end, we could be looking at what the shaka is asking for by monkey-patching the |
According to the documentation from Panasonic, Widevine is supported:
Furthermore, when monkey-patching the referenced API, I noticed that I also saw that |
Ok thanks! Interesting, so despite announcing L1 support, it seems that they don't accept any of the widevine robustness levels...
Every second attempt on the same given content or just any second call to We've seen an issue at the end of last year on LG TVs where playing an already-played encrypted content on the same RxPlayer instance could lead there to infinite rebuffering. We found a work-around for them, we could also try that same work-around here. I can try creating a branch with both work-arounds. If I do, do you know how to test it on your side? |
Just any second call, it doesn't matter whether it's the same content or not. BTW, after setting After some digging I ended up disabling the However, I'm not sure whether this is a good option to use as the documentation mentions:
That should be fine, yes. |
OK I just pushed on the This branch isn't built so you will probably want to build it before performing your tests. |
I've build the project using So, the robustness setting should be working. However, now I get these kind of warnings/errors: |
Weird this seems like the code that breaks is here:
Which would mean that you are in an environment where |
We do polyfill Promises (using https://github.com/stefanpenner/es6-promise), but this appears to have an issue when Promise is (partially) implemented. I've also tested the solution on a webOS 3.9, which has a native Promise implementation, but it lacks support for We didn't have any issues with this yet, so was this added recently? |
Yes that code was just added in the for now unreleased v3.30.0. I thought that I may have to replace all occurences of it, I'm looking at if it can be done elegantly without needing to repeat the same boilerplate everywhere. |
BTW, your initial changes seem to work! I've hacked the polyfill a bit in order to support |
Ah that's nice! I updated the branch so it does not use Also, to merge that fix, can you give me the user-agent of panasonic TVs (or a way to detect all of them)? For now the work-around is done generally for tests so cannot be merged as is. |
From their documentation:
|
Nice, thanks! I compared with some user-agents seen on the web and I've been more broad, catching [Pp]anasonic on the user agent (LG's WebOS made me skeptical of vendor's documentations, plain wrong in their case!) when the device is not detected as another platform. I updated the branch to try to make it "mergable", can you test its new form and tell me if everything still works? |
I've just completed another test round, and it's still working nicely 😄 |
Now that the v3.30.0 is officially released, you should have panasonic 2019 DRM support, through a stable version. I'm closing this issue, do not hesitate to re-open it if you still have a problem |
When testing RxPlayer (version
3.29.0
) on a Panasonic 2019 model, I encountered the following error while trying to play a DASH/Widevine stream:Sample code:
When checking the same stream with
Shaka Player
, playback can be started without issues. So, at first glance it appears that the TV should support the supplied source & thatRxPlayer
incorrectly throws this error message.The text was updated successfully, but these errors were encountered: