GStreamer was designed to provide a solution to the current Linux media problems. We descibe what we try to achieve with GStreamer. GStreamer wants to provide a clean interface to: The application programmer who wants to build a media pipeline. The programmer can use an extensive set of powerfull tools to create media pipelines without writing a single line of code. Performing complex media manipulations becomes very easy. The plugin programmer. Plugin programmers are provided a clean and simple API to create self contained plugins. An extensive debugging and tracing mechanism has been integrated. GStreamer also comes with an extensive set of real-life plugins that serve as an example too. Adhere to the GLib 2.0 object model. A programmer familiar with GLib 2.0 or older versions of Gtk+ will be comfortable with GStreamer. GStreamer uses the mechanism of signals and object properties. All objects can be queried at runtime for their various properties and capabilities. All GStreamer Objects can be extended using the GObject inheritance methods. All plugins are loaded dynamically and can be extended and upgraded independently. Plugins are shared libraries that are loaded at runtime. Since all the properties of the plugin can be set using the GObject properties, there is no need (and in fact no way) to have any header files installed for the plugins. Special care has been taking into making the plugin completely self contained. All relevant aspects of plugins can be queried at run-time. High performance is obtained by: Using GLib g_mem_chunk where possible to minimize dynamic memory allocation. Extremely light-weight connections between plugins. Data can travel the pipeline with minimal overhead. Providing a mechanism to directly work on the target memory. A plugin can for example directly write to the X server's shared memory space. Buffers can also point to arbitrary memory, such as a sound card's internal hardware buffer. Refcounting and copy on write minimize usage of memcpy(3). Sub-buffers efficiently split buffers into manageable pieces. The use of cothreads to minimize the threading overhead. Cothreads are a simple and fast user-space method for switching between subtasks. Allowing HW acceleration by the use of specialized plugins. Using a plugin registry with the specifications of the plugins so that the plugin loading can be delayed until the plugin is actually used.