I don't see any value in creating five issues for Christian to respond in when we currently have all pending action items for him in one place, and most can be resolved immediately upon his response. Well we can split out remaining issues once Christian gets back to us to answer our pending questions. Indeed, it seems that there are 3/4 issues being discussed in this ticket, which is making it quite difficult to follow.

The more we rely on the dynamic behaviour, the more important any bugs in those code paths become, which just means more stress for us. eg., shipping a repository as enabled=1 is more robust than having some code that can under certain conditions enable it and unconditionally (barring privacy concerns) pulling in the two RPMs after installation is more robust than relying on GStreamer and GNOME Software to work it out when a certain codec is necessary. I say this based on the assumption that anything (configuration or code) that's statically baked into the installation image is more robust than anything that happens dynamically on the user's system based on some conditions. Now that the legal barriers have been eased, we seem to have artificially put up some obstacles of our own making. I filed this issue because it seemed to me that we are shooting ourselves in the foot by making it really convoluted to get codecs that were for so many years unavailable to us for legal reasons. We need to get in touch with them somehow.Ĭrashes and and other bugs seem a bit unrelated to this issue. Meanwhile, Epiphany can use it, but OpenH264 is crashingĪnd Cisco won't respond to our bug report. You have to install RPMFusion to makeįirefox acceptably useful. It doesn't use OpenH264 except for WebRTC. Firefox is currently unable to play most HTML5 video because We still need confirmation from that this received legal we really need you to comment here and confirm, or this won't move forward.įinally, functionality.

In our last meeting, the full WG was not satisfied that we're allowed to do this.

Do I need to wait a day or two before the new version becomes available?

It installed gstreamer1-plugin-openh264-1.15.1-1.fc31, which is the old version that doesn't support MP4 playback.

Two more important issues before we close out this issue: What's important is that gnome-software was able to successfully install the right package. Then the description of the package, referring to non-encumbered codecs, is clearly incorrect:Īnyway, these are both minor issues. It's a bit weird that GStreamer Multimedia Codecs - Extra is showing up here, because it does not contain H.264 support. The codec launcher took me to this screen:

I manually installed your gnome-software-3.34.0-2.fc31 update and tried playing an MP4 video.

Openh264 video codec