www-client/google-chrome): /opt/google/chrome/WidevineCdm The used in the Vivaldi ebuild binaries come with a symlink to this folder, but it is working only if the Chrome version is stable (i.e. Upstream has described how:īut there is one more problem with the current ebuild - the DRM support provided by Chrome's WidevineCdm. We have it provided by media-video/ffmpeg but it needs to be symlinked in a special way to the /opt/vivaldi folder. In order the x264 videos and others to work, Vivaldi really needs the libffmpeg.so library. I'm less bothered about this aspect though, I'd just like it to work while avoiding nasty breakages.Ĭreated attachment 602618 Using that approach, you can avoid patching altogether and just replace the libffmpeg.so file that gets installed with a symlink. With the dependency in place, users can choose whether they would prefer to upgrade ffmpeg now or keep the videos working. I seriously recommend adding an ffmpeg dependency like "proprietary-codecs? ( media-video/ffmpeg:0/56.58.58 )" or you'll get problems that could include videos not working without warning, browser tabs crashing, and the browser segfaulting on startup. Just commenting it out is dangerous because it'll almost certainly break when the ffmpeg subslot/soname changes. The version check it does will never work because it's checking against the version used by Chromium (based on git commits) rather than the upstream ffmpeg version that our library has. Jer, in terms of making this work in the browser, I think more caution is needed. For now, you'll need to manually set LD_PRELOAD to the libffmpeg.so path or symlink it from /opt/vivaldi/lib/libffmpeg.so. It won't work out of the box yet because jer stopped patching the launcher script a while back. I have just pushed a fix to the ffmpeg ebuilds (v4+ only) to make it work again. Bah, there's so much confusion here, I wish someone had pinged me earlier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |