GStreamer Application Development Manual (0.8.10) | ||
---|---|---|
<<< Previous | Next >>> |
This chapter contains a fairly random selection of things that can be useful to keep in mind when writing GStreamer-based applications. It's up to you how much you're going to use the information provided here. We will shortly discuss how to debug pipeline problems using GStreamer applications. Also, we will touch upon how to acquire knowledge about plugins and elements and how to test simple pipelines before building applications around them.
Always connect to the "error" signal of your topmost pipeline to be notified of errors in your pipeline.
Always check return values of GStreamer functions. Especially, check return values of gst_element_link () and gst_element_set_state ().
Always use your pipeline object to keep track of the current state of your pipeline. Don't keep private variables in your application. Also, don't update your user interface if a user presses the "play" button. Instead, connect to the "state-changed" signal of your topmost pipeline and update the user interface whenever this signal is triggered.
<<< Previous | Home | Next >>> |
Appendices | Up | Debugging |