2014-12-16, 05:34
(2014-12-16, 05:14)pcutler Wrote:(2014-12-16, 01:54)corona Wrote:(2014-12-16, 00:12)pcutler Wrote: Hi all,
I'm on XBMC 13.2 with latest (64 bit) Chrome and using Chrome Launcher 1.1.1 and NetfliXMBC 1.3.8 on Mac OS X (Yosemite).
Has anyone seen this error: https://www.dropbox.com/s/uqdd3tnamz3zxp...0.png?dl=0 which takes you here: https://help.netflix.com/en/node/14759
Netflix is complaining that the WidevineCdm component isn't working properly - I've checked in my normal Chrome browser, and it's up to date and working.
Netlfix runs fine in my normal Chrome browser - I'm guessing this is related to Kiosk mode?
Has anyone seen this before? Any hints or help?
Thanks!
Drats, yep I've seen that while I was initially putting the canned user-data-dir together. I thought I had got the WidevineCdm back into it properly, but clearly not.
Until I get a chance to fix it, running this in terminal will hopefully get you up and going:
Code:cp -a ~/Library/Application\ Support/Google/Chrome/WidevineCDM/* ~/Library/Application\ Support/Kodi/userdata/addon_data/plugin.video.netflixbmc/chrome-user-data/WidevineCDM/
However it sounds like you'll need to change Kodi in the destination path to xbmc - I'm running on Kodi rc on my mac.
Thanks for the quick response!
I didn't have a chrome-user-data folder in my plugin.video.netflixbmc directory, so I created it, and then copied the WidevineCDM folder from /Library/Application\ Support/Google/Chrome/WidevineCDM/
Unfortunately, it still doesn't work. Any other hints to try? If necessary, I think I can upgrade to a Kodi RC (I'm using MySQL to sync my backends and am just conservative about RCs in general)
Oh, I've run ahead of you.... I just realised you're on the released version, not the one with my new user-data-dir stuff.... so yeah my suggestion is not right. If you go to the settings for chrome launcher, is it set to use its own profile? If so, try copying the WidevineCDM folder to userdata/addon_data/plugin.program.chrome.launcher/profile/
Or delete the userdata/addon_data/plugin.program.chrome.launcher/profile altogether and give it another try.
If the setting is not on, maybe try turning that setting on and seeing if it works.