The collective intent of the above plugins is to provide the GStreamer framework with a set of filters as already available in various other multimedia applications, e.g. MPlayer/mencoder, transcode, avidemux, many of them often duplicated over and over again. Once so available in GStreamer framework, they are accessible by a common API, so that the very same code can be used repeatedly (as opposed to duplicated), in line with GStreamer Motivation & Goals.
There a number of ways to make such filters available, each requiring more or less effort, and providing less or more quality (typically in that order). Foremost, of course, is to perform a code-level port, making the filter (operation) natively available in GStreamer. Alternatively, one could resort to dynamic or runtime “binding”
Clearly, when being done properly, this leads to most robust quality results. As it also requires most effort and maintenance, priority focus is given to the “popular” ones, defined here as roughly proportional to occurrence across various existing applications. The following table compares some filter operations, that implement an identical or very similar algorithm.