Package Details: chromium-widevine 1:4.10.2830.0-1

Git Clone URL: https://aur.archlinux.org/chromium-widevine.git (read-only, click to copy)
Package Base: chromium-widevine
Description: A browser plugin designed for the viewing of premium video content
Upstream URL: https://www.widevine.com/
Keywords: amazon chrome netflix prime webengine
Licenses: custom
Submitter: Scimmia
Maintainer: envolution
Last Packager: envolution
Votes: 419
Popularity: 0.076349
First Submitted: 2015-04-17 05:05 (UTC)
Last Updated: 2024-12-02 19:14 (UTC)

Latest Comments

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 36 Next › Last »

Ruddeck commented on 2017-08-16 18:40 (UTC)

Thanks. You help-me a lot.

Scimmia commented on 2017-08-14 17:25 (UTC)

I don't think the optdep on vivaldi-ffmpeg-codecs would be necessary. vivaldi already optionally depends on it, a second optional dep won't do much. Go ahead and test whatever you need. If it works, I can add the provides/replaces and we should be in good shape.

pheerai commented on 2017-08-14 16:23 (UTC)

Scimmia: Me, too, already played with that thought, also it would create a lot of optional dependencies in the background (you'd need an optdepends on `vivaldi-ffmpeg-codecs from my side, for example). Plus, I need some more testing on the browsers behaviour with the `.so` not lying in `/opt/google/chrome` with some special pages - my usual amazon access provider is on vacation. I'll drop you a mail once this is done, to discuss the future procedure with you outside of package comments, if that is ok?

Scimmia commented on 2017-08-14 14:30 (UTC)

pheeral, sounds like I should just remove the chromium dep in chromium-widevine and packages could be combined.

pheerai commented on 2017-08-14 08:33 (UTC) (edited on 2018-03-09 18:56 (UTC) by pheerai)

Please note that you won't need this package if you have google-chrome installed, vivaldi will find the plugin from that package as well.

You can check if you need this package here: https://bitmovin.com/mpeg-dash-hls-drm-test-player/ If the video plays, you're already set regarding widevine, even though you might still need the vivaldi-ffmpeg-codecs.

pheerai commented on 2017-08-14 08:26 (UTC)

Ok, now I've got it. The conflicting package was chromium-widevine, not google-chrome, and that one somehow got lost during transition. Sorry. (I'm switching from directly modifying Scimmias chromium-widevine PKGBUILD to automatically generating one when needed) As the vivaldi-package itself creates a link to `/opt/google/chrome`, I will move the plugin back there, and re-add all the needed conflicts. Note that vivaldi now detects the widevine-plugin from the `chromium-widevine`- and `google-chrome`-package as well, so if you've got one of those installed you won't need this package. Thanks for your help, aoz and atnanasi. A new version will follow soon.

aoz commented on 2017-08-14 07:47 (UTC)

Upgrading to newest version causes conflict, though doing --force works (though it's kind of a bad idea to do so): https://s.ave.zone/7f6f.png

Scimmia commented on 2017-08-13 21:24 (UTC)

Any command line switch. For flash, it's --ppapi-flash-path. If they end up doing something similar for Widevine, we could put this in a more generic path and just let everything use it. I'm asking if they're moving that direction, since I don't follow Chromium development that much and the separate download seems to indicate they might be.

sl1pkn07 commented on 2017-08-13 19:55 (UTC) (edited on 2017-08-13 20:03 (UTC) by sl1pkn07)

what command line switch? i only put the libwidevinecdm.so library into /usr/lib/chromium-dev i'm not sure if upstream maked something about the widevine as pepperflash does

pheerai commented on 2017-08-13 18:47 (UTC) (edited on 2017-08-13 19:24 (UTC) by pheerai)

@atnanasi: That's what I call fast feedback. I will add it (I don't have google chrome installed), resp. try to check if chromium-widevine works now as well. I'll get back to you soon. EDIT: The most current version (1:1.4.8.1008-1) does not conflict with google-chrome, I can install both of them simultaneously. Please be shure that you have the correct version installed And yes, I must admit that the previous version did in fact conflict, due to the fact that I was not aware of the naming change from chrome to google-chrome.

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 36 Next › Last »