GstBin Base container element GstBin is the simplest of the container elements, allowing elements to become children of itself. Pads from the child elements can be ghosted to the bin, making the bin itself look transparently like any other element, allowing for deep nesting of predefined sub-pipelines. A new GstBin is created with gst_bin_new(). Use a #GstPipeline instead if you want to create a toplevel bin because a normal bin doesn't have a scheduler of its own. After the bin has been created you will typically add elements to it with gst_bin_add(). You can remove elements with gst_bin_remove(). An element can be retrieved from a bin with gst_bin_get_by_name(), using the elements name. gst_bin_get_by_name_recurse_up() is mainly used for internal purposes and will query the parent bins when the element is not found in the current bin. The list of elements in a bin can be retrieved with gst_bin_get_list(). After the bin has been set to the PLAYING state (with gst_element_set_state()), gst_bin_iterate() is used to process the elements in the bin. The "object_added" signal is fired whenever a new object is added to the bin. gst_bin_destroy() is used to destroy the bin. Flags for a bin. @GST_BIN_FLAG_MANAGER: @GST_BIN_SELF_SCHEDULABLE: @GST_BIN_FLAG_PREFER_COTHREADS: @GST_BIN_FLAG_LAST: @name: @Returns: Free the memory allocated by this bin @bin: the bin to free @bin: @element: @bin: @element: @bin: @name: @Returns: @bin: @name: @Returns: @bin: @Returns: @bin: @state: @type: @Returns: @bin: @Returns: @bin: @oldstate: @newstate: @child: @bin: @child: is signaled whenever a new GstElement is added to the GstBin @gstbin: the object which received the signal. @arg1: the element that was added