Package Details: vivaldi-ffmpeg-codecs 77.0.3865.93-1

Git Clone URL: https://aur.archlinux.org/vivaldi-ffmpeg-codecs.git (read-only)
Package Base: vivaldi-ffmpeg-codecs
Description: additional support for proprietary codecs for vivaldi
Upstream URL: https://ffmpeg.org/
Licenses: LGPL2.1
Submitter: BlackIkeEagle
Maintainer: BlackIkeEagle
Last Packager: BlackIkeEagle
Votes: 95
Popularity: 0.054501
First Submitted: 2015-10-14 21:40
Last Updated: 2019-09-23 12:16

Pinned Comments

BlackIkeEagle commented on 2016-05-25 20:54

For the people not willing to download 500MB of chromium source to build this package:

You can install it from my repo: https://repo.herecura.eu

Note: When the version here in AUR updates you should keep in mind it can take up to 30 minutes until its available in my repo.

If you are using an AUR helper you must make sure you have enough space where the helper wants to build. If your helper uses /tmp or something you are very likely to run out of "diskspace" while building this package.

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Cavsfan commented on 2017-07-18 15:34

Although without installing this package I see no difference in Vivaldi.

Cavsfan commented on 2017-07-18 15:33

All I've gotten is errors trying to install this package. I've got a fast connection so I do not care about the 500MB but, it will not install.
It gets hundreds of "write failed" errors and wants to start over, which I cancel.
Here are the last few in terminal:
chromium-59.0.3071.104/chromeos/printing/OWNERS: Write failed
chromium-59.0.3071.104/chromeos/BUILD.gn: Write failed
chromium-59.0.3071.104/chromeos/chromeos_test_utils.cc: Write failed
chromium-59.0.3071.104/chromeos/chromeos_switches.cc: Write failed
chromium-59.0.3071.104/chromeos/OWNERS: Write failed
chromium-59.0.3071.104/chromeos/CHROMEOS_LKGM: Write failed
chromium-59.0.3071.104/chromeos/chromeos_paths.h: Write failed
chromium-59.0.3071.104/chromeos/login_event_recorder.cc: Write failed
chromium-59.0.3071.104/chromeos/third_party/android_bionic_libc/NOTICE: Write failed
chromium-59.0.3071.104/chromeos/third_party/android_bionic_libc/kernel/uapi/linux/binder.h: Write failed
chromium-59.0.3071.104/chromeos/third_party/android_bionic_libc/README.chromium: Write failed
bsdtar: Error exit delayed from previous errors.

ception commented on 2017-06-23 15:07

I'd also like to add a comment regarding this:

==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build vivaldi-ffmpeg-codecs.

because I found the comments so far not very helpful. I also tried to build it with yaourt and apparently the storage needed in /tmp during installation exceeds the tmpfs size, at least in my case. So the command you need to resolve this issue is the last one in this section of the tmpfs article:
https://wiki.archlinux.org/index.php/Tmpfs#Examples.
Temporarily resizing it to 8GB worked fine for me.

BlackIkeEagle commented on 2017-06-19 07:38

@dado1981 on the other hand nothing is stopping you from building the ffmpeg codecs ofcourse, the repo is just there for convenience

BlackIkeEagle commented on 2017-06-19 07:36

@dado1981, the packages in my personal repo are signed with the same key as the packages I put into community ;)

And the first one is not outdated because it matches the then current vivaldi-snapshot chrome version

dado1981 commented on 2017-06-18 18:31

@BlacklkeEagle
By outdated I mean "vivaldi-snapshot-ffmpeg-codecs" is 59.0.3071.83-1, and "vivaldi-ffmpeg-codecs" is 59.0.3071.91-1. The first one is slightly outdated, don't you think.
And by untrusted I mean that that repo isn't signed, so who knows what I'm downloading and from where and from whom. I downloaded thousands packages from aur.archlinux.org, they are moderated so to speak (each package is tries by several users), so I'm pretty sure that I get a real deal from here.

ben2ben commented on 2017-06-17 05:47

Same problems as @locuaz

I don't understand @Purgator do not use yaourt? I tried using pacman -S and uh. No package. Which is what I suspected. I have tried building this several times, rebooting.. etc.

Here is the console output.

Command '['/tmp/tmpUaB4k3/gn', 'gen', '/tmp/yaourt-tmp-XXXX/aur-vivaldi-ffmpeg-codecs/src/chromium-59.0.3071.91/out/Release', '--args=ffmpeg_branding="ChromeOS" proprietary_codecs=true enable_hevc_demuxing=true use_gconf=false use_gio=false use_gnome_keyring=false use_kerberos=false use_cups=false use_sysroot=false use_gold=false linux_use_bundled_binutils=false fatal_linker_warnings=false treat_warnings_as_errors=false is_clang=false is_component_build=true is_debug=false symbol_level=0 is_debug=false']' returned non-zero exit status -6
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build vivaldi-ffmpeg-codecs.
==> Restart building vivaldi-ffmpeg-codecs ? [y/N]


Little help?

#edit

I found a solution, as to help others I will post it here.

from mintjberry May 5

Sorted it. Hadn't removed the # on the line "BUILDDIR=/xxxx" - in the file "makepkg.conf ", which is in the etc folder.
Had to reboot after this.

Then I had to set permissions on the folder I had created (to use instead of tmp).
This was done through the command: "sudo chown -R user /xxxx" (where xxxx is the folder location).

The codecs did take an age to install after they downloaded, but now all videos are working great across twitter, facebook etc etc.

##

On my core i5 with 8GB of ram it took about 20 minutes to compile with no applications running.

BlackIkeEagle commented on 2017-06-15 13:26

@dado1981, and what is out of date in vivaldi-snapshot-ffmpeg-codecs? the codecs are built to match the version of chromium vivaldi* is based on as much as possible

BlackIkeEagle commented on 2017-06-15 13:23

@dado1981 what do you mean with Herecura is untrusted? You trust the stuff I upload in AUR but not the binaries I provide for you :p

dado1981 commented on 2017-06-15 12:36

Oh, and by the way, Herecura isn't trusted... I'm at work, and it would be unproffesional to use unsigned repos.