Open mediaminister opened 9 months ago
I've also noticed that the goplay website uses the X-Keyos-Authorization
header to pass the base64 drmXml instead of the customdata
header as it was before, but none of those work here.
I only tested this on Linux and it still works. I'll try on Windows.
Okay, I see. A verified media path (VMP) error. Nothing to do about it, so this won't work on Windows: https://github.com/xbmc/inputstream.adaptive/issues/919#issuecomment-1077469189
@mediaminister I tried this on Raspberry PI4 with libreelec kodi 20 and I have the same error as Michael:
2023-10-07 08:27:54.440 T:1069 info
2023-10-07 08:27:56.404 T:1765 error
2023-10-07 08:27:57.046 T:1765 error
This is also Linux...
I also found this: https://github.com/xbmc/inputstream.adaptive/issues/593 But this is from 2021 and @michaelarnauts was involved with it but since GoPlay and VTM Go are working now (except for this live stream) it must have been fixed so I wonder if the problem is more that not all needed data is provided...
No, it's not fixed. There are several levels of DRM. Some content, like livestreams or Hollywood series in 1080p quality have a more strict level of DRM: https://github.com/add-ons/plugin.video.viervijfzes/issues/69
It can't be fixed using InputStream Adaptive that uses a Widevine DRM binary with Verified Media Path enabled. Only the Widevine DRM binary on Linux x86/x64 works because Verified Media Path isn't enabled.
On Windows and RPi maybe Verified Media Path isn't enabled when you choose a lower video resolution (non-HD, like 540p)
Unfortunately it also doesn't work with a lower quality. I changed the setting in inputstream.adaptive to ask quality and even 640x360, 25ffs, 157 Kbps, the lowest quality does not work.
Hi, What is current status of this Merge Request? Is it rejected because of the windows issue? Or is the windows issue being solved with next kodi release? Or just waiting for something else?
It's impossible to solve the Verified Media Path DRM-issue as long as Kodi uses the Widevine Content Decryption Module that Google ships with web browsers. So, livestreams will not work on Windows, Apple and ARM-devices like Raspberry Pi.
I guess Kodi with InputStream Adaptive cannot provide a solution for this DRM-issue: https://github.com/xbmc/inputstream.adaptive/wiki/Verified-Media-Path-%28VMP%29
This add-on is also not actively maintained anymore.
This PR can work on Linux x64 and Android but I guess a new maintainer needs to test, merge and release this.
OK. That is clear. Real pity.
The only thing i personally don't understand (technically), what is the deal with the digital code signing? Why is this not possible? Is it a thing on resources? Licence thing? Or on the open source characteristics that requires a private key to be deployed in the public? And if I personally have the resources myself can I get my own device certified for official widivine DRM?
I know it a completely different discussion. it's just not clear to me.
For Verified Media Path (VMP) to work you need to sign your software binary (Kodi) with a keypair from Google Widevine. So you need to have a license agreement with Google Widevine.
There is a similar issue with TV Vlaanderen add-on: https://github.com/add-ons/plugin.video.tvvlaanderen/issues/63
For Verified Media Path (VMP) to work you need to sign your software binary (Kodi) with a keypair from Google Widevine. So you need to have a license agreement with Google Widevine.
There is a similar issue with TV Vlaanderen add-on: add-ons/plugin.video.tvvlaanderen#63
There is another way that could work, but it's also getting in a grayer area legal-wise.
I have tested the first two steps and this seems to work. It doesn't complain about VMP here (I think since that's something specific for browsers, and using an Android CDM doesn't have that restriuction). I'm able to pass the decryption key to ffmpeg, remux and play it in VLC.
However... I'm not interested in developing this... As said, It's a gray area, and I'm not using Kodi and my addons anymore.
That sound more like a black area. If you take up ADB for getting a key (Didn't do that google search thing though) you should be knowing that you do stuff you are not allowed that. Even tough it's your device and the kodi box is your device as well the key is the device's one. For myself I'm actually looking into the whitest area possible (hence the question on getting my kodi box certified) so it's far from an option to me.
I really appreciate the answer. And it's a pity you quit kodi altough recent developments make me think to do the same. Maybe you can still release this PR as a new version and give all users a notice that you quit your addons and encourage them to create a fork? I think you can label the live channels with beta or alpha so people actually know they use something that may or may not work?
Hi,
Just want to mention here that I forked the addon for the improvements I can add myself (don't know python myself, honestly). I started from this PR and will add stuff going forward.
I have to mention this pure self service. The livestream is working for me and I will probably not look into issues that I don't run into myself. I also added the playcrime channel already.
@JeroenED On which OS are you running kodi and the addon?
I use libreelec. I can confirm my fork is working on Linux Mint Vanessa via latest flatpak and LE11 and LE12. (LM is tested during development) However LE12 or Kodi 21 (as LM suffers the same issue) seems to have issues with inputstream.adaptive that forces SD output. Didn't look into it yet as I believe it's an issue to be solved in inputstream.adaptive but I will look into it if it's not solved by updating LE to LE12.0.1 (Or kodi 21.1)
I just tried it with libreelec on raspbery pi 5 kodi 21.0 and play is not working except play crime. But this was predicted by mediaminister.
@mediaminister i've tried this on windows, but it seems that the license server doesn't give a correct decryption key.
Is this still working for you, and on what OS?
Specific part with curl logging: