%image-entities; GStreamer"> GStreamer Application Development Manual"> GStreamer Library Reference"> ]> &TITLEPAGE; &GStreamer; is an exremely powerful and versatile framework for creating streaming media applications. Many of the virtues of the &GStreamer; framework come from its modularity: &GStreamer; can seamlessly incorporate new plugin modules. But because modularity and power often come at a cost of greater complexity (consider, for example, CORBA), writing new plugins is not always easy. This guide is intended to help you understand the &GStreamer; framework (version &GstVersion;) so you can develop new plugins to extend the existing functionality. The guide addresses most issues by following the development of an example plugin - an audio filter plugin - written in C. However, the later parts of the guide also present some issues involved in writing other types of plugins, and the end of the guide describes some of the Python bindings for &GStreamer;. &INTRO_PREFACE; &INTRO_BASICS; You are now ready to learn how to build a plugin. In this part of the guide, you will learn how to apply basic &GStreamer; and GNOME programming concepts to write a simple plugin. The previous parts of the guide have contained no explicit example code, perhaps making things a bit abstract and difficult to understand. In contrast, this section will present both applications and code by following the development of an example audio filter plugin called ExampleFilter. The example filter will begin with a single input pad and a single output pad. The filter will, at first, simply pass media and event data from its sink pad to its source pad without modification. But by the end of this part of the guide, you will learn to add some more interesting functionality, including properties and signal handlers. And after reading the next part of the guide, , you will be able to add even more functionality to your plugins. The example code used in this part of the guide can be found in examples/pwg/examplefilter/ in your &GStreamer; directory. &BUILDING_BOILER; &BUILDING_PADS; &BUILDING_CHAINFN; &BUILDING_STATE; &BUILDING_PROPS; &BUILDING_SIGNALS; &BUILDING_TESTAPP; &BUILDING_FILTERFACT; By now, you should be able to create basic filter elements that can receive and send data. This is the simple model that &GStreamer; stands for. But &GStreamer; can do much more than only this! In this chapter, various advanced topics will be discussed, such as scheduling, special pad types, clocking, events, interfaces, tagging and more. These topics are the sugar that makes &GStreamer; so easy to use for applications. &ADVANCED_SCHEDULING; &ADVANCED_TYPES; &ADVANCED_REQUEST; &ADVANCED_CLOCK; &ADVANCED_DPARAMS; &ADVANCED_MIDI; &ADVANCED_INTERFACES; &ADVANCED_TAGGING; &ADVANCED_EVENTS; By now, we have looked at pretty much any feature that can be embedded into a &GStreamer; element. However, we have limited ourselves to the simple model of a filter element. In this chapter, we will look at the specific difficulties and things to keep in mind when writing specific types of elements. We will discuss output elements (sinks), input elements (sources), 1-to-N elements, N-to-1 elements, N-to-N elements, autopluggers and managers. Some of these represent elements that don't actually exist. Rather, they represent a general concept. &OTHER_SOURCE; &OTHER_SINK; &OTHER_ONETON; &OTHER_NTOONE; &OTHER_NTON; &OTHER_AUTOPLUGGER; &OTHER_MANAGER; This chapter contains things that don't belong anywhere else. &APPENDIX_CHECKLIST; &APPENDIX_PYTHON;