-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[script.module.inputstreamhelper] 0.1.0 #598
[script.module.inputstreamhelper] 0.1.0 #598
Conversation
I see no reason why you can't use: Raspberry Pi is a huge device for KODI and needs to work. And, add some credit to @glennguy. Writing code is the easy part of programming |
@matthuisman Because, and I have told you this multiple times now, we cannot rely on third party hosts who are violating the Widevine license by hosting the binary like that. I understand that ARM-based devices are popular, but violating the license in order to support it is not how things should be done. I'm pretty sure Team Kodi agrees with me on that. The seemingly only legitimate way to obtain the binary is by extracting it from a Chrome OS image and I am looking at whether this would be possible to do in a I didn't look at @glennguy's code until now. There are definitely some similarities, but that's kind of inevitable when writing Kodi Python code. There are only so many ways you can do things. :-) I'll happily add him as an author if that's what he wants. My hope is for this module to be a collaborate effort seeing as there is a lot of developers who can benefit from it. One last thing: it would have been nice if you had left your original post before editing it. I originally started responding to that one before realizing that you had done a 180 and completely changed it. |
You had commented about his code in the forum - so obviously you had looked at it. Has a team member explicitly advised you that you can't use that third-party download? Have you even googled that url? Oh, and how is 'https://hg.mozilla.org' not third-party? In the forum, they said - they can allow this add-on as long as it's made by a third-party (non team member) and no closed source binary is in the code. (but OK to download it). If this doesn't work for most devices - then it's going to cause more issues than it solves. GlennGuy and I have many users who use our existing widevine add-ons and that is how we have found all the edge cases - that you some how found in 24 hours yourself by testing every device I assume? |
" This idea spawned from the discussion" No sh*t. That's why it already exists! You haven't had an idea! |
@matthuisman I can see that you're having an extremely hard time differentiating between 'third party hosts who are violating the Widevine license' and licensed third party hosts (Mozilla). It doesn't make it any more legitimate just because it's 'widely' used. Never did I claim that I came up with the idea myself -- that's why I linked to the forum thread in the initial pull request. I liked your idea so I implemented it. I am not going to bother answering to the 'copied some existing code into a class' because that's quite clearly not the case. Could we let this be reviewed now without polluting this pull request with more nonsense that doesn't belong here? I'd be interested in what Team Kodi has to say about the ARM binary situation. I'll happily continue our discussion in the forum thread you created. |
Have you seen Mozilla's license? Have you attempted to look for another source that you are happy with? But if your happy providing all the support for users with ARM devices on the forum - then go for it. |
Did you try using the module in an addon with an existing config.py file in it's lib directory (pretty common). |
@matthuisman @emilsvennesson That discussion seems a bit heated up & I guess we´re all interested in getting this plugin in the main repo. But I´d actually chimed in to provide some more detailed information about the license stuff & answer some questions. 1.) Mozilla is a licensed partner, that was announced by the Widevine License Team itself. 2.) You get a license file from every official widevine download (actually, there´s only one official way to download it, which is from Google directly, even the Mozilla URLs just redirect to)
Interesting part for the Addon developer(s) here: Interesting part for the users: 3.) There are no ARM builds for Widevine provided by Google as a standalone download. The only way to get ARM builds (also 32-bit only, a 64-bit version for ARM is yet to be seen) is as part of an ChromeOS Recovery build. It must be ChromeOS (not Chromium) as ChromiumOS doesn't provide Widevine for ARM. TL:DR; In order to to comply with the license, there are only 2 valid sources to obtain the Widevine lib, for non ARM systems, it´s the Google CDN (which the URLs included in the Mozilla source file link to) and ChromeOS builds for ARM systems. |
@asciidisco Thanks a lot for this information. I have started working on implementing the extraction from the Chrome OS image file after our discussion in emilsvennesson/script.module.inputstreamhelper#1. I will close this PR until a solution for the ARM situation that me and @asciidisco are comfortable with is implemented. |
Description
A simple Kodi module that makes life easier for add-on developers relying on InputStream based add-ons and DRM playback. This idea spawned from the discussion in https://forum.kodi.tv/showthread.php?tid=321165.
Checklist:
Additional information :