MediaPipe Resource Center

MediaPipe is a flexible framework to manipulate media on MacOS X. It allows you to build decoding, filtering, encoding and even streaming pipelines that correspond exactly to your needs. Additionally, if a format is not supported, or a transformation missing, it features an SDK that allows you to quickly implement the pipe you want.

The MediaPipe team is small and consists of Gaspard Petit (mobodo) and Antoine Missout (Makira). Because we are still in a development period, a lot of the MediaPipe features are still just stubs to hold everything together. A lot of details are going to change over the next two months until version 1.0 is released. Thus, we will not spend much time keeping the web site up to date, and you will not find here technical details about MediaPipe. If you wish to obtain these informations, you can either contact us directly or post your questions on the MediaPipe forums.

MediaPipe is divided in three components: The Front-End (UI) The Framework The MPipes The three components communicate with each others through two interfaces: The MediaPipe API The MediaPipe SDK Although, communication between the components normally goes in one direction (the Application talks to the Framework which talks to the MPipes), as of 0.8.0, the communication has become bi-directional - that is, you can implement a "built-in" MPipe within the Application (the Inspector is an example of that) and the MPipe can query and control the flow of a pipeline.

Recent News

• November 21

  A new pipe: YuvDenoiser, based on the mjpeg tool of the same name. Powerful all-in-one temporal/spatial denoiser, sharpness and constrast plugin.

• November 10

  A small update of the QuickTime Decoder Pipe, which fixes mpeg files compatibility.

• October 10

  A small update of XViD2pvApp, which fixes intra frame showing.

  A new tool which might interest MediaPipe users: AviTool . It takes an avi file and a mp3 file on input and multiplex them in a new avi on output. The result is a pc like avi (can be played in vlc, or in QuickTime once doctored). Uses ffmpeg. The source is avalaible . (Updated 28 october, small fix)

• September 28

  MediaPipe 0.8.9 has been released! We made no changes in the core, as this update mainly fixes and adds a few pipes to our collection. Things of interest:

  • An important fix has been applied to the MPEGDemuxer.
  • New MPipes have appeared, based on xvid:
    • XViDEncoder
    • XViDDecoder
  • The MPEGDecoder is now based on libmpeg2 instead of ffmpeg.
  • The MPEGDecoder, Scaler, Crop, ColorConverter, XVIDEncoder pipes now support YV12.
  • A new utility: XViD2pvApp, for precise control of bitrate of 2 pass vbr XViD encoding.
  • A 'Launch CLI' button has been added to the GUI app.

Mailing List

MediaPipe is meant to be an open. The SDK provides convenient interfaces which can let you build MPipes in less than 200 lines of code. If you would like to write your own pipes, we encourage you to join the mailing list as we cannot keep the documentation up to date (and it's actually not worth it at the moment since there's only Makira and myself reading it...)

About MediaPipe...

So What is the MediaPipe Framework?

The MediaPipe Framework is a programming library which manages and schedules MPipes. The idea is to make it easier for developers to contribute to the media transformation. MediaPipe deals with threading, user interface and interaction between pipes allowing programmers of MPipes to concentrate the actual code that deals with the media.

The MediaPipe Framework does not support any format in particular. The media can be audio, video, even text or raw data - as long as it can be broken into frames, samples or packets.

So What is MediaPipe?

MediaPipe is a simple application which provides a front-end to the MediaPipe Framework

So What is an MPipe?

An MPipe is a media filter. It can be summarized by three key features: it supports some media input format, processes frames and supports some media output formats.

MPipes also have the ability to use multiple input and multiple output at once (MIMO). For example, consider a multiplexer/demultiplexer, or a filter that would make a transition between two video or audio tracks.

Versions 0.x and 1.x of MediaPipe will handle only single input single output (SISO) pipelines. That means that if you demux some media, you will only be able to use 1 of the output streams in your pipeline. It limits the functionality quite a lot, but gives me a chance to make sure the framework is solid before we increase the complexity.