Skip to content
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

Raspberry Pi compatibility #28

Closed
giubari opened this issue Mar 29, 2017 · 44 comments
Closed

Raspberry Pi compatibility #28

giubari opened this issue Mar 29, 2017 · 44 comments

Comments

@giubari
Copy link

giubari commented Mar 29, 2017

Any way to make it work (with all dependencies) on Raspberry Pi 3?

@asciidisco asciidisco self-assigned this Mar 29, 2017
@asciidisco
Copy link
Owner

At the moment, no. The problem is not the plugin itself, but the way the rendering architecture in either inputstream.adaptive or Kodi Agile is set up. This is above my understanding too, but what I grasped from conversations with others is, that the RPI needs a different implementation of certain things due to its different frame buffer architecture (for someone actually know how this stuff works, this might read like total b******t but, yeah, lets keep it that way).

Long story short, I´ve heard of a working fork for the RPI which will never be public, instead, all efforts are put in merging those changes into Kodi Agile directly in a way that it complies with Kodis rules on how such stuff needs to be implemented. This might take some more weeks, but it´s very likely that we´ll end up with a version working on the RPI which most probably will be able to render 720p video & 5.1 audio. If we´re lucky & all works well, we might even end up with 1080 on the PI.

@cyraid
Copy link

cyraid commented Jun 15, 2017

Any way to track the progress? Or maybe give someone a hand? I'm not afraid to get my hands dirty if it's to support something I use.

@asciidisco
Copy link
Owner

@cyraid The work is basically done. At the moment it´s mostly merging stuff into the "regular" Kodi 18 repo, as well as rewriting parts if the Kodi maintainers do not agree with something in the code to be merged. I believe it´s a matter of weeks now until the needed changes are in Kodi, but I´m not part of the team/people who do actually work on this.

@giubari
Copy link
Author

giubari commented Jun 16, 2017

@asciidisco this is really a great news. Kodi Community is pushing on DRM and official content and plugins and trying to abandon illegal content plugins this would be the perfect way to do it. Today the only way for me to watch my Netflix subscription content is via external addon like TVMC and others.

@renatoriolino
Copy link

renatoriolino commented Jun 22, 2017

@asciidisco Is it possible already for us test it? I'm comfortable to git push development version of LE with kodi 18 and compile. Is this enough or I would need to apply some patches too? Thanks

@leleobhz
Copy link

Hello,

As a effort to test and share results to help development, I've used the following combination:

With this combination, i got the following crashlog: kodi_crashlog_20170625150339.log.zip

It's expected? There is something new I can try?

Thanks!

@marcelveldt
Copy link

First of all, the plugin is currently completely broken due to changes at Netflix. Besides that, a Milhouse build for Libreelec is based on Kodi master and not the Agile branch/fork.

You'll have to compile LibreElec yourself with the Agile code merged in

@leleobhz
Copy link

@marcelveldt - Sorry to ask, but what is the difference from Agile to Master?

@marcelveldt
Copy link

A lot, for example the ability to use the new input stream Adaptive with support for decrypting which is the base to watch the Netflix content

@Uukrull
Copy link
Contributor

Uukrull commented Jun 25, 2017

That's not true anymore. Since this PR, you can use Kodi master and inputstream.adaptive master (tested on Windows with the Amazon addon)

@cyraid
Copy link

cyraid commented Jun 26, 2017

So now it'll build on raspberry pi 3? Or does there still need to be changes made?

@marcelveldt
Copy link

@Uukrull oh wow that's some amazing news. Now only we'll have to wait until the netflix add-on is fixed again.

@Uukrull
Copy link
Contributor

Uukrull commented Jun 26, 2017

@cyraid: you still have to compile the repo from liberty-developer for inputstream.adaptive and wvdecrypter (but I don't know if it will work on pi 3)

@marcelveldt
Copy link

@Uukrull what did you do to get the amazon add-on working for your country ? Mine is giving me errors about the geo lock all the time so there must be some code in the add-on to define which catalog it uses. I'm in the Netherlands btw.

@Uukrull
Copy link
Contributor

Uukrull commented Jun 26, 2017

@marcelveldt AFAIK the Amazon addon only supports UK, DE, JP and USA regions. I live in Spain but I can use Getflix to get those regions working. Check this for more info: Sandmann79/xbmc#22

@asciidisco
Copy link
Owner

Works with Inputstream v2, Kodi 18 Nightly & v0.11.12 of the Netflix Plugin. Therefor closing this.

@lfarkas
Copy link

lfarkas commented Jul 13, 2017

anybody has any experience with this plugin on Raspberry Pi 2? I've tried it and it's working, but very slow and choopy so it seems the hardware is not enough to play back the netflix streams.

@asciidisco
Copy link
Owner

@lfarkas I´ve heard that it should be enough for SD quality (480p), which seems likely as the PI 3 can do 720p but not 1080p. We need to use software encoding on everything other than Android, so we´ll probably have no chance to do something about this.

@leleobhz
Copy link

Maybe with VC-1 hardware decoder with key?

@lfarkas
Copy link

lfarkas commented Jul 13, 2017

@asciidisco is there any change to do the same hardware encoding as on android? with this restriction it'd be useful to add as a FAQ point.

@asciidisco
Copy link
Owner

@lfarkas The Widevine Library extracted from the browser needs to be used (that´s the thing that does the decoding & the DRM stuff). It only can do software decoding.
Regarding the FAQ, sure send a PR with a link to what I´ve posted above.

@lfarkas
Copy link

lfarkas commented Jul 17, 2017

I've tested it with Pi 2 and Pi 3. none of them are able to play a netflix video 720p h264 stream. the strange thing it has no cpu load during the playback (10-20%) but it's still choopy lagging and totally unusable.

@irgendwie
Copy link

@lfarkas I can confirm this for 1080p streams, 720p is working as expected for me (RPi3).
I'm using the libreelec builds of Milhouse (https://forum.kodi.tv/showthread.php?tid=298461) with current master version of this plugin.

@lfarkas
Copy link

lfarkas commented Jul 17, 2017

ok i've tested it with build #712 it's not working. now i've tested it with build #716 it's working. although the usb ports are not working on Pi3 while working on Pi2 but it's a bug of libreelc not this plugin.

@MilhouseVH
Copy link

@lfarkas USB ports are working fine on RPi3, there's been no other reported issues on the forum (from about 250 testers). I've a keyboard, IR dongle and 32GB storage connected to my RPi3. If you've got an issue with USB post your details in the Kodi forum thread.

@tzwn
Copy link

tzwn commented Jul 18, 2017

@lfarkas @MilhouseVH USB is working fine on my Pi2 and Pi3 with #716.

@DaVinci0072
Copy link

DaVinci0072 commented Aug 1, 2017

Works on build #713, RPi3

Max smooth video stream : h264, 720x480, 2314240 bps

@cyraid
Copy link

cyraid commented Aug 1, 2017

I had some good smooth video with 720p on rpi3.. but the temperature icon comes up.. looks like I'll have to get a fan+heatsink..

@jet86
Copy link

jet86 commented Aug 1, 2017

Yes I've been getting the temperature icon and it begins stuttering when watching at 720p for any period of time. I think a heatsink and/or fan might be the way to go (I don't have them yet either).

@tzwn
Copy link

tzwn commented Aug 1, 2017

A good alternative would be a case, which absorbs and dissipates the waste heat from the SoC - passive cooling.

I highly recommend the Flirc case - best in the new version adapted for the Raspberry Pi 3.

@jet86
Copy link

jet86 commented Aug 2, 2017

Most cases actually tend to contain the heat, not dissipate it, which actually exacerbates the issue. My Pi runs cooler out of its case than in it. The Flirc Case does look pretty good since it effectively is the heatsink as well as the case, but just wanted to point out that most cases aren't designed to dissipate heat.

@Xandaros
Copy link

Xandaros commented Nov 5, 2017

This issue is linked in the FAQ section of the readme, but I'm a bit confused. Does it work on an RPi now or not?

@pinoelefante
Copy link
Contributor

it works

@laclaro
Copy link

laclaro commented Dec 24, 2017

Some time ago, I used an rpi3 to test the Netflix addon (https://laclaro.wordpress.com/2017/10/14/rpi-streaming-station-with-amazon-instant-video-and-netflix/). It runs smoothly for 720p videos. However, I claimed that you will need the license keys for this.

If I got it right DRM decoding and GPU acceleration are two different things and with inputstream the GPU cannot be used and purchasing codec licenses will not change that. Is this correct and will it maybe be possible in the future?

Best

@Tr4il
Copy link

Tr4il commented Dec 25, 2017

@asciidisco You might want to remove the link to this issue from the faq

@ndm13
Copy link

ndm13 commented Mar 26, 2018

Do we still need to download nightly builds to get this to work? If so, is there a way to track progress until these updates get officially released? Are all the steps on the wiki still required, or have some of them been slipstreamed or superceded?

@ddlandim
Copy link

In my Raspberry Pi 0w, when i will play a video, the widevine installation starts, but i got a error saying that my architeture is not compatible.

@asciidisco
Copy link
Owner

@ddlandim Which is correct, there is no widevine library that is compatible with RPI0 & RPI1, only RPI2 & RPI3 do work. Aside from that, the Pi Zero wouldn't have enough computing power to do software decoding/decrypting anyways.

@ddlandim
Copy link

I got it, thanks. I thought that note below, which you wrote in the plugin readme, was for this case.

"The link to download the Widevine Libary for none ARM Systems can be found in the Firefox Sources & needs to be placed in the cdm folder in special://home."

@padok
Copy link

padok commented Oct 21, 2018

If you turn the question around, how much computing power would you need to have to play 1080p (or 4k in the future) fluently?

There are also alternative fruity computers.

Board CPU Cores CPU Freq HDMI Tested
Rasberry Pi 3 B 4 1.2GHz 1200P60 720p playback
Orange Pi Plus 2 4 1.5GHz 4KP30 ?
Banana PI M3 8 1.8GHz 1200P60 ?
Odroid C2 4 1.5GHz 4KP60 ?

or even something like a intel NUC?
https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc6cayh.html

@pierregermain
Copy link

pierregermain commented Jun 9, 2019

Installing Input Stream Adaptive and then saying yes to all the disclaimers and accepting installing other 3rd party libraries (Widevine and Chrome OS recovery image and others) this plugin works right now on RPI 2 with LibreELEC 9. Thanks for your hard work! My son is happy now.

@G-Spawn
Copy link

G-Spawn commented Dec 14, 2019

^^^^^^^^^^^^^^ Second this working on December 13th. I just had to setup the input streams adaptive addon (sudo apt-get install kodi-inputstream-adaptive) and its working on the kodi I built atop raspbian via sudo apt-get install kodi or sudo apt-get install kodi-standalone on raspbian buster pi 4b 2gb mem!

@gergolippai
Copy link

one more success story, i also got it working, using the alternative repo here: https://github.com/CastagnaIT/plugin.video.netflix
InputStream-Adaptive seems to be default in OSMC at least (2019.11-1, Kodi 18.5), but I had to go through some add'l hoops to install pycryptodomex using this little tutorial: #665 (comment)

my kids can now watch that horrible Netflix show with the mermaids in it! :)

@Wolfsrabe
Copy link

I experience short audio dropouts using netflix addon with Kodi 18.5 (via the latest LibreELEC) on a RPI 4. I thought, it would help to set the resolution down to 720p but the audio dropouts keep. I dont now what i can do here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests