The last we heard from Sam, he was experimenting with getting Widevine L1 working, but things were still at quite an early stage, and it was quite possible those experiments would ultimately not be successful. Widevine L1 support has certainly not been announced. It might happen; if it does, we don’t know when.
Even with Widevine L1 (as I understand it) the main difference you’ll see is the enabling of hardware acceleration on Widevine videos, meaning you’ll be able to play 1080p videos comfortably on Netflix. Access to 4K or HDR streams on Netflix requires not only Widevine L1 but a device that has been certified by Netflix. It is possible (but certainly not guaranteed) that a future OSMC device might acquire such certification; but the Vero 4K(+) definitely cannot.
I’m not sure what the situation would be with other add-ons.
With newer hardware, we plan to burn in Widevine L1 and HDCP1.4, HDCP2.2 keys.
This can only be provisioned at factory and can’t be done over the air. So we could do this with newer Vero 4K+ devices but not ones out in the wild.
This does have other implications though - secure boot is probably needed. And just supporting Widevine L1 doesn’t mean we get access to everything. There are additional certification requirements.
I had the same problems on my RPi2, after a Widevine update.
.kodi/userdata/advancedsettings.xml didn’t exist. I went ahead and created it just to test the proposed solution, deactvating http2. Rebooted, didn’t work.
Downgrading the Widevine from the GUI (Addon-browser–> Netflix–> manage dependencies → Widevine reinstallation), then rebooting worked for me (for now ;-))
Same here with the TV Vlaanderen App.
Buffering all the time.
I got the 4.10.222252 .so on my harddisc but I have no clue where to copy it.
Anyone got the right ssh copy command so I can upload it to my Vero4k+ box?
I’m unsure if you can transfer it to location by network transfer easily, since kodi folder is a “hidden” folder, so unless you transfer protokol allows or have settngs to allow hidden folders you are stuck to copy it to osmc home folder, use ssh to access device shell, and run:
I agree, not a optimal solution, but it’s the only one available. There is always updates to the software based decoder, made by google. And then there are the content providers that decide which level of widevine and which functions it is supposed to support.
Most hardware manufactures elect to lock down the OS to provide the “safe space” google needs to approve your device for hw-decodeing, this rimes hard with “OpenSourceMediaCenter”. But apparently there are talks about coming OSMC devices being qualified for HW-libwidevine. Don’t know enough to say more but. For now Software decoding is limiting, in not just CPU on you hardware, but to a lot of constant functions increments, which leaves the ContentProviders a bit in limbo, which version to set as minimum.
