Videos in HTML5 will not work
-
A Former User last edited by
Here is the profile of how well the browser runs HTML5, I have tried the one other suggestion on this forum that suggests downloading Chromium [which I did] and it has done nothing towards this browser running videos like it should.
Why can't just Opera come with the codecs out of the box? -
-
A Former User last edited by
@mayune said in Videos in HTML5 will not work:
I have tried the one other suggestion on this forum that suggests downloading Chromium [which I did]
What you must download, provided that you are on ubuntu or an ubuntu based distro, is the chromium ffmpeg codecs, not chromium itself.
For more details, check the post on my signature. -
A Former User last edited by
@jimunderscorep That has done absolutely nothing. I am saying that I have followed every instruction out there and all of them are outdated and don't work at all.
-
-
-
neoh4x0r last edited by
@mayune
You will have to download the version of chromium-codecs-ffmpeg-extra that matches the version of chrome that opera uses -- this can be seen in your user-agent or on the 'Help->About Opera' pageI'm running Opera 62.0.3331.99 and on the help page the version of chrome is: Chrome/75.0.3770.100
The only matching version at the following url is: 75.0.3770.90 (make sure to match the arch: amd64, arm64, armhf, i3866)
https://launchpad.net/ubuntu/disco/+package/chromium-codecs-ffmpeg-extra
Once you click on the appropdate version and arch -- you will be taken to a page where you can download the .deb file: listed under Downloadable files -- note that you do not need the chromium-browser file, only the one for chromium-codecs-ffmpeg-extra.
After you have downloaded the .deb file you will need to open it in an archive manager that supports deb files -- the goal is to extract libffmpeg.so.
You would then copy that file into your opera installation's path (this where the opera binary is located).
To get the binary path for opera run this command in a terminal
readlink -f $(which opera)
/usr/lib/x86_64-linux-gnu/opera/operacopy libffmpeg.so into /usr/lib/x86_64-linux-gnu/opera/
** depending on your arch and system that path could be different
-
A Former User last edited by
If you are on ubuntu (or derivative distro, (e.g. mint, kde neon, k/u/lubuntu etc), why don't you just install chromium ffmpeg codecs extra?
-
neoh4x0r last edited by
@jimunderscorep said in Videos in HTML5 will not work:
If you are on ubuntu (or derivative distro, (e.g. mint, kde neon, k/u/lubuntu etc), why don't you just install chromium ffmpeg codecs extra?
@jimunderscorep said in opera beta 51.0.2830.23 linux debian x64 problem with display films into faceboobk tweeter etc (adobe flash player):
Expert's advice on the above
From time to time, someone will post a "solution" to the libffmpeg problem. This will either be "install this ubuntu's chromium ffmpeg codecs package by hand to get the... precious html5 support" or "get that tar,gz from herecura's repo, untar it and move libffmpeg to the right place to make it work".
Both are wrong because they refer to packages built for a different distro (ubuntu in the first case, arch in the second), and definitely built with a different set of libraries and compilers. Do not do that unless you want to break your system or browser.I looked at the post in your signature....
If someone is on debian and they extract libffmpeg.so from the ubuntu package: chromium-codecs-ffmpeg-extra
They won't break their browser (assuming that they grab a compatible version) and they won't break their system.
Ubuntu uses the same libraries and compilers that Debian does (since it based on debian).
Furthermore, the way that the source for libffmpeg is written (with standard inferfaces: libav, etc) means that code compiled for one system will work on other systems that are also use the same libraries, etc.
(In other words, something compiled on a derivative system can be used on the parent system, provided that the compiled code only relies on code from the parent system).
A second, but more complicated option, is to directly build libffmpeg from the chromium-browser source -- which is exactly what every packager of chromium-codecs-ffmpeg-extra does.
(the latter is what I do -- compile from source; only because I was having issues finding the extract version of chromium-codecs-ffmpeg-extra (depending on the version I might find it or not).
-
neoh4x0r last edited by
@neoh4x0r said in Videos in HTML5 will not work:
A second, but more complicated option, is to directly build libffmpeg from the chromium-browser source -- which is exactly what every packager of chromium-codecs-ffmpeg-extra does.
(the latter is what I do -- compile from source; only because I was having issues finding the extract version of chromium-codecs-ffmpeg-extra (depending on the version I might find it or not).
Like I was saying compiling libffmpeg is not easily done as it requires checking out the entire code-based for chromium browser and then checking out the specific revision -- tied to the tagged version that is needed.
Also even before checkout, there is a complicated dance needed to be done to run the depot_tools gclient (which is a custom client used to stage and build the source).
Yes, telling people just to use a different browser is an option, but for people who are largely tied to the browser that they use....that isn't really an actual option for them.
And, so since opera does not ship a proper libffmpeg.so (it is built based on chromium, the target can be changed to a chrome build). The chromium target lacks support for certain codec, but chaning the target to chrome exposes all of the extra codecs (changing the target is as simple as editing a single file and replacing a string).
in third_party/ffmpeg/ffmpeg_options.gni :
change ffmpeg_branding = _default_ffmpeg_branding
to ffmpeg_branding = "Chrome"It means that every user who is not running Ubuntu will have to resort to some out-of-band/out-of-channel process or procedure to get proper libffmpeg support in opera (meaning taking pre-build packages and extacting the plugin, or building from source, etc -- it just the way things are.
The might even be Google trying to force people to use chrome -- since the only official build that supports the codec is a "chrome" branded build.
