-
-
Notifications
You must be signed in to change notification settings - Fork 12
Unable to play DRM protected content on ARM devices #69
Comments
Has been reported at xbmc/inputstream.adaptive#593, but I'm not sure it's an actual issue in Inputstream Adaptive. |
It is also working on a RHEL7 x64 using Chrome v88 and an ARM-based Chrombook using Chrome v88. |
Just some more information. You can play a protected stream with the demo page on https://www.buydrm.com/multikey-demo Example: Open the network tab in the developper tools, and go to the above url. You'll see a call to Next, look for the Manifest. For this url, it's Now, on https://www.buydrm.com/multikey-demo, fill in the Authentication XML and the Source URL, and hit Play Stream. The video should start playing fine in your browser. This indicates that we only need these two values, and that we don't need to pass some cookies around. |
It would be nice to document this as part of the Add-ons best practices. We already have some tools listed for analyzing streams. |
It seems that another add-on also noticed this exact same issue, but they use a different backend, so that's odd. |
I still believe it's related to this 'nice' VMP validation feature. |
Some recent programs of GoPlay are DRM protected. Examples are all episodes of Masterchef USA newer than 6x12.
These programs can be played from Kodi in Ubuntu (although there is a bug in IA on Leia that allows you to only play one episode per session, so you'll need to restart Kodi), but it can't be played at all from Kodi on LibreElec (RPI4).
It seems they also can't be played on Windows. The same error is shown there.
The error we get is
{"errorcode":371000005,"errormsg":"Widevine license acquisition failed >> Verified media path cannot be verified","errorid":"07a9c5fe-d906-46b4-8c51-1976a646a3ad"}
This would indicate that it requires VMP, and nothing can be done about it, but it's working fine on Kodi on Ubuntu 20.04 x64.
Relevant part of the log:
This is the same issue as Catch-up-TV-and-More/plugin.video.catchuptvandmore#402
The text was updated successfully, but these errors were encountered: