Opera 58 and libffmpeg.so
-
-
john-53 last edited by
Fresh install of Opera 58 on Linux Mint 19 there are no issues to report.
Upgrade to Opera 58 from 57 on Linux Mint 17.3 still has some issues. The browser wouldn't load when using the Chromium 71 libffmpeg.so file. Going back to the Chromium 70 file corrected the problem.
-
A Former User last edited by
Correct me if I am wrong, but isn't 17.3 based on ubuntu 14.04?
Chromium and its set of packages has stopped on v67 for ubuntu 14.04, so where did you get chromium ffmpeg codecs 70 and 71 from? -
A Former User last edited by
With Linux leap 15 perform an update: Open console as admin and enter zypper up - ENTER
With Linux Tumbleweed same procedure, only there
Enter zypper dup.The file libffmpeg.so will be renewed automatically if necessary.
And you should update to Opera 58
http://ftp.opera.com/pub/opera/desktop/58.0.3135.47/linux/ -
john-53 last edited by
@jimunderscorep said in Opera 58 and libffmpeg.so:
Correct me if I am wrong, but isn't 17.3 based on ubuntu 14.04?
Chromium and its set of packages has stopped on v67 for ubuntu 14.04, so where did you get chromium ffmpeg codecs 70 and 71 from?I'm testing Mint 19 and it has Chromium 71 in the software manager for d/l.
Slimjet 21 has the Chromium 70 libffmpeg.so file.
Mint 17.3 actually stopped at Chromium 65 for some reason, so I stopped using Chromium on that distro.
-
A Former User last edited by
@zypper said in Opera 58 and libffmpeg.so:
john-53 - if you do this with copy&paste, changing a system-file like this, from one Browser to another, you always have a problem.
A system-file is a part of program, or the system as such; if you do any changes their, you have to be careful.Did you check this site, for you possible working file?
http://fr2.rpmfind.net/linux/rpm2html/search.php?query=libffmpeg.so -
john-53 last edited by
@ said in Opera 58 and libffmpeg.so:
@zypper said in Opera 58 and libffmpeg.so:
john-53 - if you do this with copy&paste, changing a system-file like this, from one Browser to another, you always have a problem.
A system-file is a part of program, or the system as such; if you do any changes their, you have to be careful.Did you check this site, for you possible working file?
http://fr2.rpmfind.net/linux/rpm2html/search.php?query=libffmpeg.soI'm not having any issues currently.
Mint 19 I had not installed Opera, so I d/l Opera 58 a few days ago and it worked on Youtube videos that use html5.
Mint 17.3 the work around that was needed on Opera 57 was to replace the libffmpeg.so file that was from Chromium 70 or Slimjet 21 (the 2 files are identical).
When I upgraded from Opera 57 to 58 on Mint 17.3 the same problem persisted for some reason. So I simply used the Slimjet 21 libffmpeg.so file like I had done before and it works. I'm guessing there is some difference between a fresh install of Opera 58 and upgrading from Opera 57.
-
A Former User last edited by
The chromium version of libffmpeg.so 70 is also valid for opera 58, checked. But if you want you can get it out of here version 71
http://security.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/
Anyway I have a tutorial in Spanish
https://forums.opera.com/topic/30044/h-264-activar-para-ver-vídeos-gif-linux
-
A Former User last edited by
@john-53 said in Opera 58 and libffmpeg.so:
Mint 17.3 actually stopped at Chromium 65 for some reason
My bad then. I wrote 67 in a hurry. Ubuntu 14.04 did stop on chromium 65.
-
A Former User last edited by
@leocg This keeps happening after updates of Opera. Suddenly it can't play films an one has to put in a link to libffmpeg.so in Chromium.
It is quite easily done as soon as one has figured out what is wrong, but it ought not to be necessary by now to my opinion.
So why can't Opera, once and for all, include a working version of the subroutine?
-
leocg Moderator Volunteer last edited by
@goradevik Because, as said many times before, Opera doesn't have the licenses to play proprietary codecs and depends on the OS to do it. So Opera can't include support for those codecs but it can use the OS libraries (or whatever its called) to be able to play those codecs.
With Windows and Mac there are, usually, no problems because the files needed are in the OS but with Linux things can be more complicated.
-
A Former User last edited by
@leocg said in Opera 58 and libffmpeg.so:
but it can use the OS libraries (or whatever its called) to be able to play those codecs
About this part, and leaving chrome aside, because google does have the licence for h264.
How about making opera use the system's ffmpeg libraries (the 3 libav* ones), like almost every distro (excluding ubuntu) does for its chromium (and firefox) browser, by building it differentlt? I do not remember the exact names of the 2 switches that are used fot this, but I will look them up later on. I have definitely mentioned them in the past here on the forums.
Just put a minimum requirement there, e.g. ffmpeg 4.0 or newer, and you are done.Else, you can do what vivaldi does, although I think it is sneaky. It has a tiny script that downloads ubuntu's chromium ffmpeg codecs, extracts the deb and places it somewhere in vivaldi's folder, inside ~/.local/lib/vivaldi, keeping the system clean.
If anyone wants to have a look, I have pastebinned it here
https://paste.debian.net/1130802/And the same applies for the widevine lib. The way opera is today, looking in these locations for libwidevine
$ cat /usr/lib/x86_64-linux-gnu/opera/resources/widevine_config.json [ { "preload" : "/opt/google/chrome/libwidevinecdm.so" }, { "preload" : "/opt/google/chrome-beta/libwidevinecdm.so" }, { "preload" : "/opt/google/chrome-unstable/libwidevinecdm.so" } ]simply "demands" chrome (stable, beta, or unstable verions) to be already installed on the system and opera will use its libwidevine. We are talking about a 200+MB browser and opera only needs a 9MB lib from it!
How about doing using the... vivaldi approach? It downloads libwidevine from google, unzips it and places it inside ~/.local/lib/vivaldi/WidevineCdm, which keeps the system clean of junk. The browser just detects it and uses it.
Simple as that. No need for other browsers to be installed and no need for file editing etc when something fails.
If anyone wants to check it too, I pastebinned it here
https://paste.debian.net/1130805/ -
burnout426 Volunteer last edited by
@jimunderscorep said in Opera 58 and libffmpeg.so:
And the same applies for the widevine lib
So, if you download
https://dl.google.com/widevine-cdm/4.10.1582.2-linux-x64.zipfor example and extract it, where should "libwidevinecdm.so" and "manifest.json" go so that they are only detected by Opera and Opera detects them before any of the others listed in "usr/lib/x86_64-linux-gnu/opera/resources/widevine_config.json"?Is "~/.local/lib/opera/WidevineCDM" where they should go or can they go in "/usr/lib/x86_64-linux-gnu/opera/lib_extra" with libffmpeg.so and be detected?
(Can't check at the moment.)
-
A Former User last edited by
I do not know about the paths you mention... and I am not willing to test.
To be honest, since I first found out opera's issues on h264 playback and on widevine later on, I have lost any interest to make them work. I just use another browser when a video or stream can not play and that's it. I care a bit less for widevine because I do not use netflix or any other service that needs drm. Sorry
Keep in mind that you will also need a "proper" libffmpeg, besides the "right" libwidevinecdm, because the streams you are trying to play are in h264 or h265 (at least on netflix).
-
-
burnout426 Volunteer last edited by
@jimunderscorep said in Opera 58 and libffmpeg.so:
Sorry
No problem. I'll test when I get a chance.
Keep in mind that you will also need a "proper" libffmpeg, besides the "right" libwidevinecdm
Yes. Understood.
