-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FirefoxNightly] H264/MP4 playback not supported #22
Comments
I can confirm that the MP4 playback does not work even with FirefoxDevEdition on Fedora 25, with ffmpeg (and libavcodec.so) installed from RPMFusion (with DNF). |
It took a few hours of muddling, but I added ffmpeg to the .json manifest file, redid the build on my local machine, and got the libraries correctly installed outright. It's all worth it for video playback right? Note some of these dependencies may be unnecessary as far as firefox is concerned, and a couple of them are encumbered by licensing issues, but that's for the lawyers to decide. Also be warned that the firefox git clone performs a ~3gb download, and the initial build takes up to an hour. I added these lines between the Rust section and the Firefox section in
|
Hm, this is rather difficult to decide as long as ffmpeg contains some non-free code, @Sesivany what do you think about it? |
I think the right way to add codecs is via runtime extensions. Firefox uses the GNOME runtime, so you can create an extension which will add ffmpeg to the runtime. The advantage of it is that if the extension is installed any app which uses the GNOME runtime will be able to use it. Another advantage is that you don't have to tweak Firefox to look for ffmpeg in another path which will be very important once Mozilla releases the official Firefox for Flatpak. |
Why not just host it somewhere else outside of the US and on a personal, non RH system? The MPEG-LA can't sue in a country where software patents aren't legally enforceable, and you don't need a whole lot of machine to serve files. If you can extend the GNOME runtime to link against system ffmpeg, then this would only be a temporary stopgap until that change got upstreamed anyways. The lack of H.264 makes these packages essentially useless for most people. |
@tidux If someone forks our work and build it and host it somewhere else... but we as RH employees have tied hands. |
Flathub maybe? They already have VLC and Spotify. |
Flathub would be good. They already have Steam so clearly they're not concerned about redistributing non-libre software. |
It's not about the license. It's about patents. The software itself could be FLOSS, but if it violates existing patents you can't distribute it, at least in some jurisdictions. FFMEG is GPL/LGPL, so the license is not a problem. |
Flathub is already hosting a build of Picard that uses FFMPEG and the hordes of MPEG-LA lawyers haven't descended on them yet. Looks like that issue has been resolved. |
So what's the status of this now? |
Given that there doesn't seem to be any consensus from the greater Flatpak community on defining common non-GStreamer extensions for codecs, why not define the extension for the FirefoxNightly flatpak itself? They're not just available for runtimes, after all. |
Finally we have a solution for this: https://firefox-flatpak.mojefedora.cz/#audio/video-playback |
Running Fedora 31 and ffmpeg 1.6 with Firefox 70 and also 69 and I cannot get the media to play with the solution
Running Fedora 31 and ffmpeg 1.6 with Firefox 70 and also 69 and I cannot get the media to play with this solution. |
Visiting the YouTube html5 test page displays a red mark next to H.264 and H.264/MSE, and trying to play embedded MP4s fails with the browser console error
Reading some past bug reports and forum posts, I believe Firefox looks for libavcodec.so(.57) for H.264 decoding. I have tried dropping those files into the
[...]org.mozilla.FirefoxNightly/current/active/files/lib/
directory but it doesn't appear to help.My distro is Solus, which has its own package manager and may have installed the relevant libraries in a different place than usual. Is there a way to point it to the right codecs? Am I creating more trouble for myself by doing things the wrong way?
Thank you!
The text was updated successfully, but these errors were encountered: