1. It can be built from source. https://aur.archlinux.org/packages/vivaldi-ffmpeg-codecs/ describes how to built it from source. 2. A binary executable can be extracted from distribution packages. However, if the binary executable is linked against a different version of glibc, it won't work.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vivaldi-ffmpeg-codecs contains build instructions.
ffmpeg[chromium] is broken. https://bugs.gentoo.org/653448
Can you try and make it into ebuild format? It's a lot of work, and there's little interest towards writing it :) It's a shame one needs to download +600 MB of sources and use +30 minutes to compile only to provide a 1 MB file. But yes, this would be nice feature to get into vivaldi, and building it from source to your system is indeed the Gentoo way (although easier to just copypaste the pre-compiled Arch lib).
If it takes more than 30 minutes to compile something, then I think fixing https://bugs.gentoo.org/653448 would be a better solution.
Created attachment 552502 [details] vivaldi-ffmpeg-codecs-69.0.3497.100.ebuild I kinda half-jokingly put up an ebuild fast to see how hard it would actually be to write one, and to my surprise, it worked! It's not ready to be put in Gentoo's tree as-is, but I think it's a nice start for anyone willing to take time and maintain it. Also, if people just wanna _compile_ their own libffmpeg.so, this should work. It's missing every build-dep needed from its DEPEND line for now, but I only had to install gn manually. Some of those configure switch should be controlled with a USE flag, too. And installation gave me some QA error, but as said, vivaldi plays all media files with this now. Building this still requires 3GB of RAM and 5GB of disk base, as does chromium itself. Above are some pointers for people wishing to use it. I _might_ update it to meet Gentoo standards later, but I most likely won't maintain this ever (since chromium's code and ebuilds change all the time).
Sorry, I think this should be closed though I'll leave that for jer to decide. I went through a long and somewhat painful journey in bug #580990 to find out that this isn't necessary. Chromium uses a fork of ffmpeg but the stock ffmpeg actually does work if you build it in the right way. It's a lot simpler with a *much* smaller download and you benefit from using system libraries for the various dependencies. We did have this working a while back through the ffmpeg[chromium] USE flag but it broke when Chromium started using ffmpeg 4 and we took a while to unmask it. It also took me until last night to work out that it segfaults with --enable-opencl. That's not a problem as we build a separate copy of the library for Chromium. I'll get it pushed later today.
I've pushed my changes now. This doesn't include the browser side of the equation so for now, you'll need to manually set LD_PRELOAD to the libffmpeg.so path or symlink it from /opt/vivaldi/lib/libffmpeg.so. I've noticed this bug isn't assigned so I guess I'll just close it.
