Chromium: a new media Backend based on GStreamer

Display subtitles automatically

None
In the preferred language only when the video is using another
Always in the preferred language
Always in the original language of the video

Preferred language:

Qualities

UbiCast player x

Keyboard shortcuts

Key

Action

K or space

Play / Pause

Mute / Unmute

Select next subtitles

Select next audio track

Show slide in full page or toggle automatic source change

left arrow

Seek 5s backward

right arrow

Seek 5s forward

shift + left arrow or J

Seek 10s backward

shift + right arrow or L

Seek 10s forward

control + left arrow

Seek 60s backward

control + right arrow

Seek 60s forward

shift + down arrow

Decrease volume

shift + up arrow

Increase volume

shift + comma

Decrease playback rate

shift + dot or shift + semicolon

Increase playback rate

end

Seek to end

beginning

Seek to beginning

Loading Click here to add:

Information on this media

Number of views:

783 (this month: 4)

Creation date:

Oct. 29, 2015

Speakers:

Julien Isorce

License:

CC BY-SA 3.0

Description

The GStreamer backend has to follow chromium's multiprocess and sandboxing architecture. Unlike in webkit based browsers, GStreamer pipelines cannot live in the tab-specific processes (Render processes). Chromium design and rules require a different approach than WebKit-based browsers. We will explain why it cannot live in any of the existing processes (Browser process, Renderer Process, GPU Process).

For the sake of the project this new backend must be as efficient as existing media backends in chromium (ffmpeg, chunk demuxers, HW decoder wrappers). One of the purpose of using GStreamer is also to re-use HW decoder elements it provides (gst-v4l2, gstreamer-vaapi, gst-omx, ...).

We will detail how the Media Process interacts with other processes using chromium IPC api and how GstPlayer is integrated. We will describe the sandbox policies we defined for the Media Process and how it blocks or filters system calls. We will explain how the GStreamer pipelines get data from the web through Browser Process to respect sandbox restrictions. Due to sandbox restrictions we will describe how GstGL can access the chromium GPU process to produces OpenGL textures.