Getting Chromium onto the GStreamer lovetrain

Bastien Nocera is known for a lot of things. Most people in Gnome probably knows him as the maintainer of the Totem media player. In the Fedora community he is known as one who deals with a lot of the challenges around multimedia. Here in the UK he is also known as the only frenchman to ever get fully naturalized.

Anyway his latest effort is to try to try and kickstart some work in Google Chromium to get it to use everyone favorite media framework GStreamer. Bastiens explains a lot of his rationale in the Chromium bug report, but I am hoping to get others in the community to chime in too, and even if you don’t have anything new to add, just let Google know you care by starring up this bug report.

10 thoughts on “Getting Chromium onto the GStreamer lovetrain”

  1. Now if only they could use proper GTK+ widgets, system webkit, and support a –new-window argument or something for opening pages in a new window instead of a tab, I might be able to switch…

  2. I’m pretty sure they are using system WebKit in trunk. I got a demo of their build system at the hackfest and it included checking out WebKit from upstream.
    Gives you 1 out of 3 already. And the other thing it gives them is easy access to the GStreamer media stuff.

  3. Chrome needs codecs, not a mm framework. FFmpeg provides that.

    It would be neat to get hardware acceleration, but I haven’t seen GStreamer, or anybody providing that, at least on the platforms I care about.

  4. Just to clarify, FFmpeg does support a variety of Hardware acceleration schemes including vdpau and dxva2.

Comments are closed.